Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 01-Text | 1.29 MB |
Contents
Snapshot management in file storage
Quota management in file storage
Volume mapping in block storage
Volume migration in block storage
Volume snapshot in block storage
Async remote replication in block storage
Self-healing framework in block storage
Appendix A Summary of SNMP notifications
Introduction
This document provides information about the SNMP alarm notifications for the storage system. It also provides recommended actions to help you remove the alarm conditions reported through SNMP notifications.
Support for the SNMP alarm notifications might be slightly different depending on the software version.
The following information is provided based on the assumption that you have basic knowledge of the storage and the storage device.
Obtaining alarm notifications
To obtain SNMP alarm notifications:
· Configure SNMP alarm notification settings in the storage management system. For more information about the configuration procedure, see the storage management system online help.
· Configure a third-party platform that acts as the SNMP manager.
Alternatively, you can obtain alarms by accessing the alarm management page of the storage management system.
To obtain alarms from the alarm management page:
1. Log in to the Web interface of the storage management system.
2. From the navigation pane, select Alarms > Alarm Management > All Alarms.
3. View alarms or export alarms as needed.
For more information, see the storage management system online help.
|
|
NOTE: For the ease of use, this document includes alarms that have not supported SNMP notifications yet. |
Severity levels of alarms
The alarms contain a severity level to help you determine whether immediate action is required. Table 1 describes the predefined severity levels. In addition to these severity levels, the storage system also supports self-defined severity levels.
The severity level of an alarm is user configurable.
Table 1 Notification severity levels
|
Services are impacted, for example, a node or resource is unavailable. Immediate action is required. |
|
|
Major |
Service quality is degraded, for example, the performance of a node or resource degrades and requires a restoration. Action is required with high priority. |
|
Minor |
Minor impact or risk exists without impacting service quality. Action is required with medium to low priority. |
|
Warning |
An error might occur to impact services. A review is required to determine whether action is necessary. |
Alarm sources
Table 2 lists the modules that generate alarms.
|
Module |
Description |
|
OS |
System alarms, for example, CPU usage alarms. |
|
NET |
Network alarms on the cluster or a node, for example, an alarm about a network error on a storage node. |
|
DEVICE |
Physical device alarm, for example, CPU error alarms. |
|
CLUSTER |
Cluster alarms, for example, storage pool error alarms. |
|
NAS |
NAS alarms, for example, file system quota alarms. |
Alarm email format
This section is an introduction of alarm email topics and email format.
Topic format
An alarm email topic includes the following fields: client name, cluster name, severity level, email ID, and alarm content.
Figure 1 Fields in an alarm email topic
Table 3 Fields in an alarm email topic
|
Sequence number |
Field |
Description |
Remark |
|
1 |
Client name |
Name of the client that uses the storage cluster service. Client name configuration is supported only when the user deploys a cluster. |
When a client uses multiple clusters, the client can configure the same client name for different clusters. |
|
2 |
Cluster name |
Name of the storage cluster. Cluster name configuration is supported only when the user deploys the cluster. |
When a client uses multiple clusters, the client should configure a unique name for each cluster. |
|
3 |
Severity level |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
For more information about each severity level, see Table 1. |
|
4 |
Email ID |
Email ID. |
· For real-time alarm emails, the ID consists of the following: ¡ Alarm type ID, a string of 10 characters. ¡ Auto-generated ID, a string of 9 characters. · For repeating alarm emails, the ID consists of the following: ¡ Alarm type ID, a string of 10 characters. ¡ Auto-generated ID, a string of 9 characters. ¡ Send times, a string with an uncertain number of characters. |
|
5 |
Alarm content |
Alarm content. |
For more information about an alarm, see "Notifications." |
Text format
The text of an alarm email includes the following: email header, alarm information, cluster information, technical support contact, and email ending.
Figure 2 Text format of an alarm email
Table 4 Text format of an alarm email
|
Sequence number |
Field |
Description |
|
1 |
Email header |
Email header in fixed format. |
|
2 |
Alarm information |
Content of an alarm information, including alarm content, alarm type, severity level, alarm source, alarm status, alarm time, alarm recovery time, alarm cause, and recommended actions. |
|
3 |
Cluster information |
Information about the cluster where the alarm occurs, including contacts, cluster license information, software version, node quantity, OSD quantity, monitor node information, node pool information, and disk pool information. |
|
4 |
Technical support contact |
Contacts used to obtain technical support. |
|
5 |
Email ending |
Email ending in fixed format. |
Technical support
H3C is dedicated to providing user-friendly products with the best quality. To obtain assistance, contact H3C by email or phone or access documents at the H3C website.
· Email:
¡ China: [email protected]
¡ Hongkong, China: [email protected]
¡ Other countries or regions: [email protected]
· Technical support hotline:
To find contacts for your local area, access the H3C global contacts page at https://www.h3c.com/en/Support/Online_Help/Service_Hotlines/
· Website: http://www.h3c.com
Using this document
You can obtain some notification information such as a type ID, through the storage management system or the third-party platform, and then use it to locate the corresponding alarm for more details.
For each notification, this document provides the information described in Table 5.
Table 5 Information provided for each notification
|
Item |
Description |
|
Type ID |
Alarm type ID, which uniquely identifies the notification. |
|
OID |
OID of the notification in the MIB. |
|
Trap name |
SNMP trap name of the alarm. |
|
MIB file |
Name of the MIB file that contains the notification. For an NMS to identify and understand the MIB objects used by the device, you must first load the MIB files to the NMS by using a MIB compiler. |
|
Metric |
Alarm metric name in the storage management system. |
|
Text |
Alarm text. |
|
Source |
Modules that might generate the alarm. |
|
Severity |
Severity of the notification. This information helps you determine whether action is required in response to the notification. |
|
Default status |
Default status of the notification: · ON—The notification is enabled. · OFF—The notification is disabled. |
|
Description |
Explanation of the notification. |
|
Objects |
Information about the objects included in the notification. |
|
Recommended action |
Recommended action to remove an error condition. This section contains a "no action is required" description for recovery and informational notifications. |
|
|
NOTE: For the ease of use, this document contains alarms for which SNMP notifications are yet to be supported. For these alarms, the OID and MIB file fields are empty. These alarms are available from the Web interface of the storage management system. |
Notifications
This document categorizes notifications by functionality. The MIBs and the notifications in each MIB are sorted by type ID.
Cluster management
This section contains the notifications about cluster management.
0x02040303
Basic information
|
Item |
Values |
|
Type ID |
0x02040303 |
|
OID |
1.3.6.1.4.1.25506.2.1.20 |
|
Trap name |
sysAlarmCapabilityUtilizationL1 |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Cluster Storage Capacity Usage Level 1 |
|
Text |
The cluster capacity usage ($2%) has reached or exceeded the level-1 threshold ($3%) $2: sysCapabilityUtilizationRate $3: sysCapabilityThreshold |
|
Source |
CLUSTER |
|
Severity |
Minor |
|
Default status |
ON |
Description
The used cluster capacity has exceeded the level 1 threshold.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.6 (sysCapabilityUtilizationRate) |
OCTET STRING |
$2: Capacity usage of the cluster. |
|
1.3.6.1.4.1.25506.1.1.1.13(sysCapabilityThreshold) |
OCTET STRING |
$3: Level 1 threshold on cluster capacity usage. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Add storage nodes or disks to expand the cluster.
0x02040304
Basic information
|
Item |
Values |
|
Type ID |
0x02040304 |
|
OID |
1.3.6.1.4.1.25506.2.1.21 |
|
Trap name |
sysAlarmCapabilityUtilizationL2 |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Cluster Storage Capacity Usage Level 2 |
|
Text |
The cluster capacity usage ($2%) has reached or exceeded the level-2 threshold ($3%) $2: sysCapabilityUtilizationRate $3: sysCapabilityThreshold |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The used cluster capacity has reached or exceeded the level 2 threshold.
In this situation, the cluster capacity usage is high. Make sure the remaining amount of capacity is sufficient.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.6 (sysCapabilityUtilizationRate) |
OCTET STRING |
$2: Capacity usage of the cluster. |
|
1.3.6.1.4.1.25506.1.1.1.13(sysCapabilityThreshold) |
OCTET STRING |
|
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Add storage nodes or disks to expand the cluster.
0x02040305
Basic information
|
Item |
Values |
|
Type ID |
0x02040305 |
|
OID |
1.3.6.1.4.1.25506.2.1.22 |
|
Trap name |
sysAlarmCapabilityUtilizationL3 |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Cluster Storage Capacity Usage Level 3 |
|
Text |
The cluster capacity usage ($2%) has reached or exceeded the level-3 threshold ($3%) $2: sysCapabilityUtilizationRate $3: sysCapabilityThreshold |
|
Source |
CLUSTER |
|
Severity |
Critical |
|
Default status |
ON |
Description
The used cluster capacity has reached or exceeded the Level 3 threshold.
In this situation, the remaining cluster capacity is not sufficient and only data reads are allowed.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.6 (sysCapabilityUtilizationRate) |
OCTET STRING |
$2: Capacity usage of the cluster. |
|
1.3.6.1.4.1.25506.1.1.1.13(sysCapabilityThreshold) |
OCTET STRING |
$3: Level 3 threshold on cluster capacity usage. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Add storage nodes or disks to expand the cluster.
0x02040402
Basic information
|
Item |
Values |
|
Type ID |
0x02040402 |
|
OID |
1.3.6.1.4.1.25506.2.1.18 |
|
Trap name |
sysAlarmDiskPoolCapabilityUtilization |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Diskpool Capacity Usage |
|
Text |
The capacity usage of disk pool $2 is $3% and the alarm threshold is $4%. The current capacity usage has been reached or exceeded the alarm threshold $1: fsid $2: sysDiskPoolName $3: sysCapabilityUtilizationRate $4: sysCapabilityUtilizationRateThreshold |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The capacity usage of the disk pool has been reached or exceeded the alarm threshold.
In this situation, the storage system cannot write data to the disk pool.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
$1: Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.33 (sysDiskPoolName) |
OCTET STRING |
$2: Disk pool name. |
|
1.3.6.1.4.1.25506.1.1.1.6 (sysCapabilityUtilizationRate) |
OCTET STRING |
$3: Capacity usage of the disk pool. |
|
1.3.6.1.4.1.25506.1.1.1.34(sysCapabilityUtilizationRateThreshold) |
OCTET STRING |
$4: Threshold on disk pool capacity usage. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Add disks to expand the disk pool.
0x02040701
Basic information
|
Item |
Values |
|
Type ID |
0x02040701 |
|
OID |
1.3.6.1.4.1.25506.2.1.27 |
|
Trap name |
sysAlarmClusterVerDiff |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
node_version_inconsistent |
|
Text |
The nodes in the cluster do not use the same software version. |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The nodes in the cluster do not use the same software version.
In this situation, the cluster cannot be used for data storage.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Make sure all nodes in the cluster use the same software version.
0x02040702
Basic information
|
Item |
Values |
|
Type ID |
0x02040702 |
|
OID |
1.3.6.1.4.1.25506.2.1.29 |
|
Trap name |
sysAlarmVerDiffUpgrade |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
component_version_maybe_inconsistent |
|
Text |
Component versions may be inconsistent between nodes during the upgrade process. |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
Some nodes might use different component versions during upgrade.
In this situation, the upgrade might fail. If the upgrade succeeds despite the component version inconsistency, some features of the cluster might be unavailable or go wrong.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
After the upgrade completes, check the component version of each node. Make sure all nodes in the cluster use the same component version.
0x02042101
Basic information
|
Item |
Values |
|
Type ID |
0x02042101 |
|
OID |
1.3.6.1.4.1.25506.2.1.2 |
|
Trap name |
sysAlarmPoolStatus |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Storage Pool Error |
|
Text |
Storage pool anomaly occurred: Pool $2 contains PG in abnormal state $2: sysPoolName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
A storage pool became abnormal. Some PGs in the pool were abnormal.
In this situation, cluster I/O might decrease to zero.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.24 (sysPoolName) |
OCTET STRING |
|
|
1.3.6.1.4.1.25506.1.1.1.29 (sysPoolId) |
Unsigned32 |
Storage pool ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Log in to the storage management system.
2. From the navigation pane, select Cluster Management > Dashboard.
3. Observe the cluster data health degree for changes.
¡ If the cluster data health improves, the cluster is self-healing. Ignore the alarm.
¡ If the cluster data health stays unchanged in 10 minutes, contact Technical Support.
0x02042102
Basic information
|
Item |
Values |
|
Type ID |
0x02042102 |
|
OID |
1.3.6.1.4.1.25506.2.1.3 |
|
Trap name |
sysAlarmPoolDegrade |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Degraded Storage Pool |
|
Text |
Storage pool anomaly occurred: Pool $2 contains degraded PGs $2: sysPoolName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
Some data in the storage pool has fewer replicas or blocks than specified in the redundancy policy.
In this situation, the storage pool is prone to data loss.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.24 (sysPoolName) |
OCTET STRING |
$2: Storage pool name. |
|
1.3.6.1.4.1.25506.1.1.1.29 (sysPoolId) |
Unsigned32 |
Storage pool ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Log in to the cluster management system.
2. From the navigation pane, select Cluster.
3. On the Dashboard page, observe the cluster data health degree for changes.
¡ If the cluster data health is improving, the cluster is self-healing, ignore the alarm.
¡ If the cluster data health does not improve in 10 minutes, contact Technical Support.
0x02042103
Basic information
|
Item |
Values |
|
Type ID |
0x02042103 |
|
OID |
1.3.6.1.4.1.25506.2.1.33 |
|
Trap name |
sysAlarmClusterPoolWritable |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Un-writable storage pool |
|
Text |
The cluster is unusable: Storage pool $1 is read only and is unusable. |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The storage pool is read only.
In this situation, the storage system cannot write data to the storage pool.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.24(sysPoolName) |
OCTET STRING |
$1: Storage pool name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check whether the number of the faulty nodes has exceeded the redundancy limit, and then have an overall troubleshooting.
2. If the alarm notification persists after the troubleshooting, contact Technical Support.
0x02042104
Basic information
|
Item |
Values |
|
Type ID |
0x02042104 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Cluster Pool Capacity Usage |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
N/A
Recommended action
Delete the unwanted data from the storage pool.
0x02040102
Basic information
|
Item |
Values |
|
Type ID |
0x02040102 |
|
OID |
1.3.6.1.4.1.25506.2.1.5 |
|
Trap name |
sysAlarmCpuUtilization |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Cluster CPU Usage |
|
Text |
The CPU usage of the cluster is $2% $2: sysCpuUtilizationRate |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The CPU usage of the cluster has exceeded the threshold.
In this situation, cluster performance will decrease.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.7 (sysCpuUtilizationRate) |
OCTET STRING |
$2: CPU usage of the cluster. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
No immediate action is required. The cluster will automatically remove this alarm notification after the service load decreases.
0x02040202
Basic information
|
Item |
Values |
|
Type ID |
0x02040202 |
|
OID |
1.3.6.1.4.1.25506.2.1.6 |
|
Trap name |
sysAlarmMemoryUtilization |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Cluster Memory Usage |
|
Text |
The memory usage of the cluster is $2% $2: sysMemUtilizationRate |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The memory usage of the cluster has exceeded the threshold.
In this situation, cluster performance will decrease.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.8(sysMemUtilizationRate) |
OCTET STRING |
$2: Memory usage of the cluster. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
No immediate action is required. The cluster will automatically remove this alarm notification after the service load decreases.
0x02042001
Basic information
|
Item |
Values |
|
Type ID |
0x02042001 |
|
OID |
1.3.6.1.4.1.25506.2.1.12 |
|
Trap name |
sysAlarmClusterSystemWarnHealth |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Cluster health warning |
|
Text |
The cluster entered the HEALTH_WARN state. $2 $2: sysWarnHealth |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
Cluster health has deteriorated to the HEALTH_WARN state because some flag bits might be set for the cluster.
In this situation, cluster services might be interrupted.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.27(sysWarnHealth) |
OCTET STRING |
$2: Detailed information about cluster warn health. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Log in to the cluster management system.
2. From the navigation pane, select Hosts.
3. Select Monitor Nodes.
4. Check the status of monitor nodes.
5. If the monitor nodes are operating correctly, check the storage nodes for OSD exceptions.
¡ If exception has occurred on all OSDs on a storage node, check for network and configuration issues.
¡ If all OSDs are operating correctly or exception has occurred only on some OSDs, contact Technical Support.
6. If a monitor node is in an abnormal state, access the monitor node to check for its ceph-mon daemon.
a. Start the daemon if it is not running.
In Ubuntu, execute the start ceph-mon-all command to start the daemon.
In CentOS, execute the systemctl start ceph-mon.target command to start the daemon.
b. Two minutes later, check for the daemon again.
c. If the daemon is not running, contact Technical Support.
0x02042002
Basic information
|
Item |
Values |
|
Type ID |
0x02042002 |
|
OID |
1.3.6.1.4.1.25506.2.1.13 |
|
Trap name |
sysAlarmClusterSystemErrorHealth |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Cluster health error |
|
Text |
The cluster entered the HEALTH_ERROR state. $2 $2: sysErrorHealth |
|
Source |
CLUSTER |
|
Severity |
Critical |
|
Default status |
ON |
Description
Cluster health has deteriorated to the HEALTH_ERROR state, typically because of an unhealthy PG.
In this situation, I/O might decrease to zero. Immediate action is required.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.28(sysErrorHealth) |
OCTET STRING |
$2: Detailed information about cluster error health. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Log in to the cluster management system.
2. From the navigation pane, select Hosts.
3. Select Monitor Nodes
4. Check the status of monitor nodes.
5. If the monitor nodes are operating correctly, check the storage nodes for OSD exceptions.
¡ If exception has occurred on all OSDs on a storage node, check for network and configuration issues.
¡ If all OSDs are operating correctly or exception has occurred only on some OSDs, contact Technical Support.
6. If a monitor node is in an abnormal state, access the monitor node to check for its ceph-mon daemon.
a. Start the daemon if it is not running.
In Ubuntu, execute the start ceph-mon-all command to start the daemon.
In CentOS, execute the systemctl start ceph-mon.target command to start the daemon.
b. Two minutes later, check for the daemon again.
c. If the daemon is not running, contact Technical Support.
0x02042003
Basic information
|
Item |
Values |
|
Type ID |
0x02042003 |
|
OID |
1.3.6.1.4.1.25506.1.7.1.186 |
|
Trap name |
sysAlarmClusterHealthOID |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Cluster unavailable |
|
Text |
Cluster unavailable |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The cluster is unavailable because of a specific reason.
In this situation, the system cannot provide data writing or reading services.
Objects
|
Syntax |
Description |
|
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check whether the number of the faulty nodes has exceeded the redundancy limit, and then have an overall troubleshooting.
2. If the alarm notification persists after the troubleshooting, contact Technical Support.
0x01040130
Basic information
|
Item |
Values |
|
Type ID |
0x01040130 |
|
OID |
1.3.6.1.4.1.25506.2.2.88 |
|
Trap name |
nodeAlarmHostMaintain |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Host_maintain_warn |
|
Text |
The maintenance mode is enabled for node $1. $1: nodeName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The maintenance mode is enabled for the node.
In this situation, the state of the cluster or OSD is marked as noout or noup to avoid CRUSH auto-rebalancing.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Disable the maintenance mode for the node.
0x01040131
Basic information
|
Item |
Values |
|
Type ID |
0x01040131 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Abnormal AI ENGINE Container Deployment |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
When you deploy an AI Engine container, one of the following tasks fails:
· Enable TCP for the AI Engine.
· Upload the AI Engine image.
· Create the AI Engine container.
In this situation, the AI Engine container deployment fails.
Objects
N/A
Recommended action
1. Check the system log to find the cause of this alarm notification.
2. Have a troubleshooting, and then redeploy the AI Engine container under the guidance of the maintenance book.
3. Clear the alarm notification manually.
4. If the alarm notification persists, contact Technical Support.
0x01040601
Basic information
|
Item |
Values |
|
Type ID |
0x01040601 |
|
OID |
1.3.6.1.4.1.25506.2.1.28 |
|
Trap name |
sysAlarmUpgradeStatus |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
upgrade_warn |
|
Text |
Cluster upgrade failed. |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The cluster upgrade failed because of a specific reason.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check the system log to find the cause of this alarm notification.
2. Have a troubleshooting, and then upgrade the cluster again.
3. If the alarm notification persists, contact Technical Support.
0x01040700
Basic information
|
Item |
Values |
|
Type ID |
0x01040700 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
DISK added failed |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
Failed to add some disks during cluster deployment or node pool creation for a specific reason.
Objects
N/A
Recommended action
1. Check the system log to find the cause of this alarm notification.
2. Locate the cause, and then clear the faulty disk partitions under the guidance of the maintenance book.
3. Add disks to the disk pool again, and then clear the alarm notification manually.
4. If the alarm notification persists, contact Technical Support.
0x01042201
Basic information
|
Item |
Values |
|
Type ID |
0x01042201 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Database configuration reconstruction failure |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The database is not accessible because of a cluster or network failure.
In this situation, the database is not accessible. You cannot log in to or search data on the management page of the storage system.
Objects
N/A
Recommended action
1. Log in to the cluster management system.
2. From the navigation pane, select Hosts.
3. Select Monitor Nodes.
4. Check the status of monitor nodes, and then perform one of the following tasks:
¡ If a monitor node is in an abnormal state, log in to each monitor node, and then check whether its network condition is normal.
If the network condition of a monitor node is abnormal, restart the NIC of the monitor node, and then check whether the network condition restores to normal.
¡ If the monitor nodes are operating correctly, use the supervisorctl restart onestor-leader command to restart the leader processes on the primary and backup management nodes. Then, check whether you can search configuration information successfully.
5. If the issue persists, contact Technical Support.
0x01042304
Basic information
|
Item |
Values |
|
Type ID |
0x01042304 |
|
OID |
1.3.6.1.4.1.25506.2.1.14 |
|
Trap name |
clusterSqlSynchronize |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Database synchronization exception |
|
Text |
Database synchronization status is abnormal |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
Database synchronization errors occurred on the primary management node and the backup management node.
In this situation, the system is prone to data loss of alarms and logs.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Access all management nodes to check for network issues.
2. Access all management nodes to check for the existence of database processes. If the database does not exist, contact Technical Support.
3. If the alarm is not cleared in 30 minutes, contact Technical Support.
0x01042305
Basic information
|
Item |
Values |
|
Type ID |
0x01042305 |
|
N/A |
|
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Conflict of HA VIP |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The management HA VIP is used by another network device.
In this situation, you cannot log in to the management page of the storage system.
Objects
N/A
Recommended action
Set a new HA VIP that is not used by any device on the network.
0x01042306
Basic information
|
Item |
Values |
|
Type ID |
0x01042306 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
|
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
OFF |
Description
The Handy service is in an abnormal state.
In this situation, the management page of the storage system is not usable.
Objects
N/A
Recommended action
1. Check all management nodes for network issues.
If a management node has a network issue, have a troubleshooting.
2. If the alarm notification is not cleared within 30 minutes, contact Technical Support.
0x01042301
Basic information
|
Item |
Values |
|
Type ID |
0x01042301 |
|
OID |
1.3.6.1.4.1.25506.2.1.15 |
|
Trap name |
clusterZKNum |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Inappropriate number of zookeeper nodes |
|
Text |
The number of zookeeper nodes is even. |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The number of zookeeper nodes is even.
In this situation, the cluster will be unable to operate correctly because auto primary management node election fails.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Add or delete a monitor node to make sure the number of zookeeper nodes is odd.
If the alarm notification is not cleared within 30 minutes, contact Technical Support.
0x01042302
Basic information
|
Item |
Values |
|
Type ID |
0x01042302 |
|
OID |
1.3.6.1.4.1.25506.2.1.16 |
|
Trap name |
clusterZKHealth |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Cluster management configuration service exception |
|
Text |
Exception occurred to cluster management configuration service. |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
Exception occurs on the cluster management configuration service.
This alarm impacts cluster manageability but it does not impact cluster services.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Access each monitor node to check for management network issues.
2. Restart the NICs to recover from network issues.
3. If the cluster management configuration alarm is not cleared in 10 minutes, contact Technical Support.
0x01042303
Basic information
|
Item |
Values |
|
Type ID |
0x01042303 |
|
OID |
1.3.6.1.4.1.25506.2.1.17 |
|
Trap name |
ifDownWhenOperate |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Network failure during host operations |
|
Text |
Network connectivity was lost while the system was operating host $1. $1: sysNodesIP |
|
Source |
CLUSTER |
|
Severity |
Critical |
|
Default status |
ON |
Description
Network connectivity was lost while the system was operating the host, resulting in a host operation failure. The system might have failed to clear data as required, and the amount of remnant data varies depending on the time when connectivity was lost.
In this situation, you will be unable to add the host to the cluster.
This alarm requires a manual acknowledgement after the issue is removed. The system cannot automatically clear this alarm.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
$1: sysNodesIP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Contact Technical Support for help and manually acknowledge the alarm after the issue is removed.
0x02010099
Basic information
|
Item |
Values |
|
Type ID |
0x02010099 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Abnormal disk status |
|
Text |
N/A |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
Some disks went offline or were pulled out.
In this situation, the cluster cannot run correctly.
Objects
N/A
Recommended action
1. Log in to the cluster management system.
2. From the navigation pane, select Hosts.
3. Click the name of the host to which the faulty disk belongs.
4. Click Replace Disk to replace or repair the faulty disk.
5. If the alarm notification persists, contact Technical Support.
0x02010303
Basic information
|
Item |
Values |
|
Type ID |
0x02010303 |
|
OID |
1.3.6.1.4.1.25506.2.2.35 |
|
Trap name |
nodeAlarmDiskUtilizationL1 |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
|
|
Text |
The usage of disk $3 on node $1 ($2) is $4%, which has reached or exceeded level 1 threshold $5%. $2: nodeIP $3: diskName $4: diskUtilizationRate |
|
Source |
DEVICE |
|
Severity |
Minor |
|
Default status |
ON |
Description
Disk usage on the node has reached or exceeded the level 1 threshold.
Storage services have not been impacted yet.
|
OID (object name) |
Syntax |
Description |
|
OCTET STRING |
$1: Host name. |
|
|
1.3.6.1.4.1.25506.1.2.1.3 (nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.2(diskName) |
OCTET STRING |
$3: Disk name. |
|
1.3.6.1.4.1.25506.1.4.1.13(diskUtilizationRate) |
OCTET STRING |
$4: Disk usage. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Delete useless files or directories from the disks.
0x02010304
Basic information
|
Item |
Values |
|
Type ID |
0x02010304 |
|
OID |
1.3.6.1.4.1.25506.2.2.36 |
|
Trap name |
nodeAlarmDiskUtilizationL2 |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
|
|
Text |
The usage of disk $3 on node $1 ($2) is $4%, which has reached or exceeded level 2 threshold $5%. $1: nodeName $2: nodeIP $3: diskName $4: diskUtilizationRate |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
Disk usage on the node has reached or exceeded the level 2 threshold.
In this situation, the disk load is high, and you must make sure the remaining disk capacity is sufficient.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2 (nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3 (nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.2 (diskName) |
OCTET STRING |
$3: Disk name. |
|
1.3.6.1.4.1.25506.1.4.1.13 ( diskUtilizationRate) |
OCTET STRING |
$4: Disk usage. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Delete useless files or directories from the disks on the node that generates the alarm.
0x02010305
Basic information
|
Item |
Values |
|
Type ID |
0x02010305 |
|
OID |
1.3.6.1.4.1.25506.2.2.37 |
|
Trap name |
nodeAlarmDiskUtilizationL3 |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Node Disk Usage Level 3 |
|
Text |
The usage of disk $3 on node $1 ($2) is $4%, which has reached or exceeded level 3 threshold $5%. $1: nodeName $2: nodeIP $3: diskName $4: diskUtilizationRate |
|
Source |
DEVICE |
|
Severity |
Critical |
|
Default status |
ON |
Description
Disk usage on the node has reached or exceeded the level 3 threshold.
In this situation, the disk capacity is insufficient. Data cannot be written to disk and only data reads are allowed.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3 (nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.2(diskName) |
OCTET STRING |
$3: Disk name. |
|
1.3.6.1.4.1.25506.1.4.1.13(diskUtilizationRate) |
OCTET STRING |
$4: Disk usage. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Delete useless files or directories from the disks on the node that generates the alarm.
0x02010306
Basic information
|
Item |
Values |
|
Type ID |
0x02010306 |
|
OID |
1.3.6.1.4.1.25506.2.2.87 |
|
Trap name |
nodeAlarmLogPartitionUsage |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Log partition usage |
|
Text |
The log partition usage on node $1 ($2) is $3%, and the alarm threshold is $4%. The current usage has reached or exceeded the alarm threshold. $1: nodeName $2: nodeIP $3: nodeLogPartitionUsage $4: diskUtilizationThreshold |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
Log partition usage on the storage node has reached or exceeded the alarm threshold.
In this situation, the system can only ready data in the disk, but cannot write log data to the disk. The running speed and performance of the system might be degraded.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2 (nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3 (nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.38 (nodeLogPartitionUsage) |
OCTET STRING |
$3: Log partition usage. |
|
1.3.6.1.4.1.25506.1.4.1.14 (diskUtilizationThreshold) |
OCTET STRING |
$4: Threshold on disk usage. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Please transfer useless log data to another disk or delete them from the current disk.
0x02010331
Basic information
|
Item |
Values |
|
Type ID |
0x02010331 |
|
OID |
1.3.6.1.4.1.25506.2.2.97 |
|
Trap name |
nodeAlarmDiskInfoInconsistent |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The disk info in cluster is inconsistent with the actual info |
|
Text |
Disk info on node $1 in the cluster is inconsistent with the actual disk info. $1: nodeName |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm notification is generated in either of the following situations:
· Some disks of the node were misplaced or absent.
· You replaced some disks of the node on the node's backstage.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Log in to the cluster management system.
2. From the navigation pane, select Hosts.
¡ If you have not replaced disks manually, click the name of the host to which the faulty disks belong, and then click Replace Disk to replace or repair the faulty disks.
¡ If you have replaced disks manually, click More > Correct Disk Info for a faulty disk to correct its information. Repeat this step for the remaining faulty disks.
3. If the alarm notification persists, contact Technical Support.
0x02010102
Basic information
|
Item |
Values |
|
Type ID |
0x02010102 |
|
OID |
1.3.6.1.4.1.25506.2.2.7 |
|
Trap name |
nodeAlarmCpuUtilization |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Node CPU Usage |
|
Text |
The CPU usage of node $1 ($2) is $3%, which has reached or exceeded the threshold $4%. $1: nodeName $2: nodeIP $3: nodeCpuUtilizationRate $4: nodeCpuUtilizationThreshold |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
CPU usage on the storage node has exceeded the threshold.
The system performance of the node will decrease.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.4(nodeCpuUtilizationRate) |
OCTET STRING |
$3: CPU usage. |
|
1.3.6.1.4.1.25506.1.2.1.12(nodeCpuUtilizationThreshold) |
OCTET STRING |
$4: Threshold on CPU usage. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
No immediate action is required. The cluster will automatically remove this alarm notification after the service load decreases.
0x02010202
Basic information
|
Item |
Values |
|
Type ID |
0x02010102 |
|
OID |
1.3.6.1.4.1.25506.2.2.7 |
|
Trap name |
nodeAlarmMemoryUtilization |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Node memory Usage |
|
Type ID |
The memory usage of node $1 ($2) is $3%, which has reached or exceeded the threshold $4%. $1: nodeName $2: nodeIP $3: nodeMemUtilizationRate $4: nodeMemUtilizationThreshold |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
Memory usage on the storage node has exceeded the threshold.
The system performance of the storage node will decrease.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.7(nodeMemUtilizationRate) |
OCTET STRING |
$3: Memory usage. |
|
1.3.6.1.4.1.25506.1.2.1.13(nodeMemUtilizationThreshold) |
OCTET STRING |
$4: Threshold on Memory usage. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
No immediate action is required. The cluster will automatically remove this alarm notification after the service load decreases.
0x01010601
Basic information
|
Item |
Values |
|
Type ID |
0x01010601 |
|
OID |
1.3.6.1.4.1.25506.2.2.16 |
|
Trap name |
nodeAlarmRaidControler |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A RAID controller become abnormal |
|
Type ID |
RAID controller $3 of node $1 ($2) became abnormal $1: nodeName $2: nodeIP $3: nodeRaidController |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The RAID controller on the node is operating incorrectly and cannot manage disks correctly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.30(nodeRaidController) |
OCTET STRING |
$3: RAID controller. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Replace the faulty RAID controller.
0x01010101
Basic information
|
Item |
Values |
|
Type ID |
0x01010101 |
|
OID |
1.3.6.1.4.1.25506.2.2.24 |
|
Trap name |
nodeAlarmCpuStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A CPU module became abnormal |
|
Text |
CPU module $3 on node $1 ($2) became abnormal. $1: nodeName $2: nodeIP $3: nodeCpuModule |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
A CPU module is operating incorrectly on the node.
As the number of available CPUs decreases, process error might occur and CPU load might increase, resulting in system error.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.24(nodeCpuModule) |
OCTET STRING |
$3: CPU module. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Replace the faulty CPU.
0x01010172
Basic information
|
Item |
Values |
|
Type ID |
0x01010172 |
|
OID |
1.3.6.1.4.1.25506.2.3.31 |
|
Trap name |
blockAlarmIscsiLinkAbnormal |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
iSCSI link disconnected abnormally |
|
Text |
Storage node $1 detected an abnormal iSCSI link disconnection from host $2 to storage $3. After handling this issue, manually acknowledge the alarm notification. $1: appIscsiNode $2: appIscsiHostIp $3: appIscsiIP |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The iSCSI link between two nodes was disconnected abnormally.
In this situation, the two nodes cannot communicate with each other and the cluster will malfunction.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.17(appIscsiNode) |
OCTET STRING |
$1: iSCSI node name. |
|
1.3.6.1.4.1.25506.1.6.1.18(appIscsiHostIp) |
OCTET STRING |
$2: iSCSI host IP. |
|
1.3.6.1.4.1.25506.1.6.1.16(appIscsiIP) |
OCTET STRING |
$3: iSCSI storage IP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check whether the host is operating correctly and whether the network connectivity between the host and the storage node is normal.
2. Handle all detected issues, and then manually acknowledge the alarm notification.
0x01010201
Basic information
|
Item |
Values |
|
Type ID |
0x01010201 |
|
OID |
1.3.6.1.4.1.25506.2.2.25 |
|
Trap name |
nodeAlarmMemStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A Memory module became abnormal |
|
Text |
Memory module $3 on node $1 ($2) became abnormal. $1: nodeName $2: nodeIP $3: nodeMemModule |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
A memory module is operating incorrectly on the node.
As the available memory space decreases, process error or system failure might occur.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.25(nodeMemModule) |
OCTET STRING |
$3: Memory module. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Replace the faulty memory module.
0x01010301
Basic information
|
Item |
Values |
|
Type ID |
0x01010301 |
|
OID |
1.3.6.1.4.1.25506.2.2.26 |
|
Trap name |
nodeAlarmFanStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A Fan module became abnormal |
|
Text |
Fan module $3 of node $1 ($2) became abnormal. $1: nodeName $2: nodeIP $3: nodeFanModule |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
A fan module is operating incorrectly.
The cooling performance will decrease and eventually result in hardware overtemperature and system failure if no action is taken.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.26(nodeFanModule) |
OCTET STRING |
$3: Fan module. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Replace the faulty fan module.
0x01010401
Basic information
|
Item |
Values |
|
Type ID |
0x01010401 |
|
OID |
1.3.6.1.4.1.25506.2.2.27 |
|
Trap name |
nodeAlarmPwrStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A power module became abnormal |
|
Text |
Power module $3 of node $1 ($2) became abnormal. $1: nodeName $2: nodeIP $3: nodePwrModule |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The power supply cannot supply power to the node, which might result in hardware exceptions.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.27(nodePwrModule) |
OCTET STRING |
$3: Power module. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Replace the faulty power supply.
0x01010501
Basic information
|
Item |
Values |
|
Type ID |
0x01010501 |
|
OID |
1.3.6.1.4.1.25506.2.2.28 |
|
Trap name |
nodeAlarmEthStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A NIC became abnormal |
|
Text |
NIC $3 of node $1 ($2) became abnormal. $1: nodeName $2: nodeIP $3: nodeNic |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
NIC error will cause loss of network connectivity.
As the node cannot communicate with other nodes in the cluster, the cluster will malfunction.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.28(nodeNic) |
OCTET STRING |
$3: NIC. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check the NIC condition. If the NIC is failed, replace it.
0x01010502
Basic information
|
Item |
Values |
|
Type ID |
0x01010502 |
|
OID |
1.3.6.1.4.1.25506.2.2.29 |
|
Trap name |
nodeAlarmEthPlug |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A NIC was removed |
|
Text |
NIC $3 of node $1 ($2) was removed. $1: nodeName $2: nodeIP $3: nodeNic |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The node will be unable to communicate with other nodes in the network attached to the NIC. Cluster error will occur.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.28(nodeNic) |
OCTET STRING |
$3: NIC. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Re-install and enable the NIC.
0x01010503
Basic information
|
Item |
Values |
|
Type ID |
0x01010503 |
|
OID |
1.3.6.1.4.1.25506.2.2.30 |
|
Trap name |
nodeAlarmIbStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
An RDMA NIC became abnormal |
|
Text |
RDMA NIC $3 of node $1 ($2) became abnormal. $1: nodeName $2: nodeIP $3: nodeIbNic |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The node will be unable to communicate with other nodes in the network attached to the NIC. Cluster error will occur.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.29(nodeIbNic) |
OCTET STRING |
$3: IB NIC. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Replace the faulty IB NIC.
0x01010504
Basic information
|
Item |
Values |
|
Type ID |
0x01010504 |
|
OID |
1.3.6.1.4.1.25506.2.2.9 |
|
Trap name |
nodeAlarmBandWidthUtilization |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Node NIC Bandwidth Usage |
|
Text |
Bandwidth usage of NIC $3 on node $1 ($2) is $4%, which has reached or exceeded the alarm threshold is $5%. $1: nodeName $2: nodeIP $3: nodeNic $4: nodeBandwidthUsage $5: nodeBandwidthThreshold |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The bandwidth usage of a NIC on a node has reached or exceeded the alarm threshold.
In this situation, the running speed of the cluster will degrade.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3 (nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.28(nodeNic) |
OCTET STRING |
$3: NIC. |
|
1.3.6.1.4.1.25506.1.2.1.34(nodeBandwidthUsage) |
OCTET STRING |
$4: Bandwidth usage. |
|
1.3.6.1.4.1.25506.1.2.1.14(nodeBandwidthThreshold) |
OCTET STRING |
$5: Threshold on bandwidth usage. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check whether the cluster has a high service load. If yes, reduce the number of storage services.
0x01010505
Basic information
|
Item |
Values |
|
Type ID |
0x01010505 |
|
OID |
1.3.6.1.4.1.25506.2.2.106 |
|
Trap name |
nodeAlarmEthLinkSpeed |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Maximum data transmission rate of a NIC not achieved |
|
Text |
The current data transmission rate of NIC $3 on node $1 ($2) is $4 Mbps, which is lower than the maximum data transmission rate ($5 Mbps) supported by the NIC. $1: nodeName $2: nodeIP $3: nodeNic $4: nodeBandwidthUsage $5: nodeNicMaxTransmissionRate |
|
Source |
DEVICE |
|
Severity |
Minor |
|
Default status |
ON |
Description
The current data transmission rate of a NIC is lower than the maximum data transmission rate supported by the NIC.
In this situation, the following issues might occur:
· A network issue arises.
· The node cannot communicate with another node quickly.
· The cluster malfunctions.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3 (nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.28(nodeNic) |
OCTET STRING |
$3: NIC. |
|
1.3.6.1.4.1.25506.1.2.1.42 (nodeBandwidthUsage) |
OCTET STRING |
$4: Data transmission rate. |
|
1.3.6.1.4.1.25506.1.2.1.43 (nodeNicMaxTransmissionRate) |
OCTET STRING |
$5: Maximum data transmission rate. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check whether the data transmission rate of that NIC is affected by other devices.
0x01010701
Basic information
|
Item |
Values |
|
Type ID |
0x01010701 |
|
OID |
1.3.6.1.4.1.25506.2.2.31 |
|
Trap name |
nodeAlarmPdPlug |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A disk was removed |
|
Text |
Disk $4 in slot $3 of node $1 ($2) was removed. $1: nodeName $2: nodeIP $3: diskSlot $4: diskid |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
Removal of the system disk will cause a system failure.
Removal of a data disk will cause a data migration, resulting in an increased use of memory, CPU, and network bandwidth.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3 (nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$3: Slot number. |
|
1.3.6.1.4.1.25506.1.4.1.17(diskid) |
OCTET STRING |
$4: Disk ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Re-install the disk.
0x01010703
Basic information
|
Item |
Values |
|
Type ID |
0x01010703 |
|
OID |
1.3.6.1.4.1.25506.2.2.32 |
|
Trap name |
nodeAlarmPdLine |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A disk went offline |
|
Text |
Disk $4 in slot $3 of node $1 ($2) went offline. $1: nodeName $2: nodeIP $3: diskSlot $4: diskid |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
If the system disk goes offline, the system of the node will fail.
If a data disk goes offline, data migration will occur, resulting in an increased use of memory, CPU, and network bandwidth.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3 (nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$3: Slot number. |
|
1.3.6.1.4.1.25506.1.4.1.17(diskid) |
OCTET STRING |
$4: Disk ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Bring the disk online.
0x01010704
Basic information
|
Item |
Values |
|
Type ID |
0x01010704 |
|
OID |
1.3.6.1.4.1.25506.2.2.75 |
|
Trap name |
nodeAlarmSsdEraseOverThreshold |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Number of SSD rewrite times has reached the threshold |
|
Text |
The number of write/erase cycles in the SSD of slot $3 on node $1 ($2) is $4% (statistical value of the average block erasure times obtained by normalization calculation) and has reached the alarm threshold $5% (statistical threshold of the average block erasure times obtained by normalization calculation). $1: nodeName $2: nodeIP $3: diskSlot $4: diskRewrittenNum $5: diskRewrittenNumThreshold |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The number of write/erase cycles in an SSD has reached the alarm threshold.
In this situation, the SSD might fails and the cluster cannot operate correctly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3 (nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$3: Slot number. |
|
1.3.6.1.4.1.25506.1.4.1.22(diskRewrittenNum) |
OCTET STRING |
$4: Number of write/erase cycles. |
|
1.3.6.1.4.1.25506.1.4.1.23 (diskRewrittenNumThreshold) |
OCTET STRING |
$5: Threshold on the number of write/erase cycles. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Replace the SSD that has violated the threshold on the number of write/erase cycles.
0x01010705
Basic information
|
Item |
Values |
|
Type ID |
0x01010705 |
|
OID |
1.3.6.1.4.1.25506.2.2.33 |
|
Trap name |
nodeAlarmPdTemp |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The temperature of a disk is too high |
|
Text |
The temperature of disk $4 in slot $3 on node $1 ($2) is $5°C and the alarm temperature is $6°C. The current temperature has reached or exceeded the alarm temperature. $1: nodeName $2: nodeIP $3: diskSlot $4: diskid $5: diskTemperature $6: diskTemperatureThreshold |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
High disk temperature might cause disk failure and in the worst case, data corruption.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3 (nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$3: Slot number. |
|
1.3.6.1.4.1.25506.1.4.1.17(diskid) |
OCTET STRING |
$4: Disk ID. |
|
1.3.6.1.4.1.25506.1.4.1.15(diskTemperature) |
OCTET STRING |
$5: Disk temperature. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Decrease the room temperature.
0x01010706
Basic information
|
Item |
Values |
|
Type ID |
0x01010706 |
|
OID |
1.3.6.1.4.1.25506.2.2.76 |
|
Trap name |
nodeAlarmDownStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Node Management Network Abnormal |
|
Text |
Node $1 ($2) has a management network issue. $1: nodeName $2: nodeIP |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The node has a management network issue. In this situation, the node cannot communicate with other nodes in the cluster correctly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3 (nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check whether the host is down. If yes, power on and start the host.
2. Check the management network for faults, and then have a troubleshooting.
3. If the alarm notification persists, contact Technical Support.
0x01010707
Basic information
|
Item |
Values |
|
Type ID |
0x01010707 |
|
OID |
1.3.6.1.4.1.25506.2.2.77 |
|
Trap name |
nodeAlarmPdRemappErrCnt |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Number of disk remapping times has reached the threshold |
|
Text |
The number of disk remappings in slot $3 on node $1 ($2) has reached the threshold. $1: nodeName $2: nodeIP $3: diskSlot |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The number of disk remappings has reached the threshold.
In this situation, the disk will fail and the data in the disk might be destroyed.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$3: Slot number. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Replace the faulty disk, and then manually acknowledge the alarm notification.
0x01010708
Basic information
|
Item |
Values |
|
Type ID |
0x01010708 |
|
OID |
1.3.6.1.4.1.25506.2.2.78 |
|
Trap name |
nodeAlarmPdBadBlockCnt |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Number of bad blocks on a disk has reached the threshold |
|
Text |
The number of bad blocks on the disk in slot $3 on node $1 ($2) has reached the threshold. $1: nodeName $2: nodeIP $3: diskSlot |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The number of faulty blocks in a disk has reached the threshold.
In this situation, the disk will fail and data writing and reading will go wrong. The data in the disk might be destroyed.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$3: Slot number. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Replace the faulty disk.
0x01010709
Basic information
|
Item |
Values |
|
Type ID |
0x01010709 |
|
OID |
1.3.6.1.4.1.25506.2.2.79 |
|
Trap name |
nodeAlarmPdReadErrCnt |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Number of disk read errors has reached the threshold |
|
Text |
The number of read errors occurred on the disk in slot $3 on node $1 ($2) has reached the threshold. $1: nodeName $2: nodeIP $3: diskSlot |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The number of disk read errors has reached the threshold.
In this situation, the disk might fail with a high data read error rate and the data in the disk might be destroyed. The cluster might have I/O errors.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$3: Slot number. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Replace the faulty disk, and then manually acknowledge the alarm notification.
0x0101070a
Basic information
|
Item |
Values |
|
Type ID |
0x0101070a |
|
OID |
1.3.6.1.4.1.25506.2.2.80 |
|
Trap name |
nodeAlarmPdSelfTestSenseCheckErr |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
SMART failure predicted |
|
Text |
SMART failure predicted on the disk in slot $3 on node $1 ($2). $1: nodeName $2: nodeIP $3: diskSlot |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The disk had a SMART failure and cannot be used.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$3: Slot number. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Replace the faulty disk, and then manually acknowledge the alarm notification.
0x0101070b
Basic information
|
Item |
Values |
|
Type ID |
0x0101070b |
|
OID |
1.3.6.1.4.1.25506.2.2.81 |
|
Trap name |
nodeAlarmDiskIoSlow |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Slow disk I/O |
|
Text |
Disk $4 in slot $3 on node $1 ($2) became slow. $1: nodeName $2: nodeIP $3: diskSlot $4: diskid |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The disk has a low I/O speed.
In this situation, the node to which the disk belongs will run slowly and the performance of the storage system will degrade.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$3: Slot number. |
|
1.3.6.1.4.1.25506.1.4.1.17(diskid) |
OCTET STRING |
$4: Disk ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Use a SMART tool to check the state of the disk, and then manually acknowledge the alarm notification.
0x0101070c
Basic information
|
Item |
Values |
|
Type ID |
0x0101070c |
|
OID |
1.3.6.1.4.1.25506.2.2.89 |
|
Trap name |
nodeAlarmCpuTemp |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The temperature of a CPU is too high |
|
Text |
The temperature of the CPU in slot $3 on node $1 ($2) is $4°C and the alarm temperature is $5°C. The current temperature has reached or exceeded the alarm temperature. $1: nodeName $2: nodeIP $3: nodeCpuModule $4: nodeTemp $5: nodeTempThreshold |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The temperature of a CPU is too high.
In this situation, the node might operate incorrectly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.18(nodeCpuModule) |
OCTET STRING |
$3: Slot number. |
|
1.3.6.1.4.1.25506.1.4.1.17(nodeTemp) |
OCTET STRING |
$4: Temperature. |
|
1.3.6.1.4.1.25506.1.2.1.37(nodeTempThreshold) |
OCTET STRING |
$5: Temperature threshold. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Decrease the room temperature.
0x0101070d
Basic information
|
Item |
Values |
|
Type ID |
0x0101070d |
|
OID |
1.3.6.1.4.1.25506.2.2.90 |
|
Trap name |
nodeAlarmEnvTemp |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The temperature of server environment is too high |
|
Text |
The environment temperature of node $1 ($2) is $3°C and the alarm temperature is $4°C. The current temperature has reached or exceeded the alarm temperature. $1: nodeName $2: nodeIP $3: nodeTemp $4: nodeTempThreshold |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The server module has a high temperature because the environment temperature is too high.
In this situation, the node might operate incorrectly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.17(nodeTemp) |
OCTET STRING |
$3: Temperature. |
|
1.3.6.1.4.1.25506.1.2.1.37(nodeTempThreshold) |
OCTET STRING |
$4: Temperature threshold. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Decrease the room temperature.
0x0101070e
Basic information
|
Item |
Values |
|
Type ID |
0x0101070e |
|
OID |
1.3.6.1.4.1.25506.2.2.86 |
|
Trap name |
nodeAlarmDiskAbnormal |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Abnormal disk state |
|
Text |
The state of the disks in $2 $4 on node $1 became abnormal, please check. $1: nodeName $2: diskSlot $3: diskRaidInfoCh $4: diskRaidInfoEn |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The state of the disks in a RAID became abnormal.
In this situation, the cluster might run incorrectly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$2: Slot number. |
|
1.3.6.1.4.1.25506.1.4.1.20(diskRaidInfoCh) |
OCTET STRING |
$3: RAID information (CH). |
|
1.3.6.1.4.1.25506.1.4.1.21 (diskRaidInfoEn) |
OCTET STRING |
$4: RAID information (EN). |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Keep observing the storage system. The system will repair the faulty disks within two hours.
2. If the system fails to repair the faulty disks, replace those disks.
3. If the alarm notification persists, contact Technical Support.
0x0101070f
Basic information
|
Item |
Values |
|
Type ID |
0x0101070f |
|
OID |
1.3.6.1.4.1.25506.2.2.92 |
|
Trap name |
nodeAlarmEvtIothWarnCannotRecover |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Unrecoverable disk errors |
|
Text |
Unrecoverable errors occurred on disk in slot $3 of node $1 ($2). $1: nodeName $2: nodeIP $3: diskSlot |
|
Source |
DEVICE |
|
Severity |
Critical |
|
Default status |
ON |
Description
A disk had unrecoverable disk errors.
In this situation, the cluster might operate incorrectly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$3: Slot number. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Replace the faulty disk.
0x01010710
Basic information
|
Item |
Values |
|
Type ID |
0x01010710 |
|
OID |
1.3.6.1.4.1.25506.2.2.107 |
|
Trap name |
nodeAlarmPdPreFailure |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The disk might fail |
|
Text |
Disk failure might occur on slot($3) of node $1 ($2). $1: nodeName $2: nodeIP $3: diskSlot |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The AI Engine has detected an upcoming disk failure in a slot.
In this situation, the disk is going to fail and the data in the disk might be destroyed. The cluster will malfunction.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$3: Slot number. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Replace the faulty disk, and then check whether the alarm notification is cleared.
2. If the alarm notification persists, contact Technical Support.
0x01010711
Basic information
|
Item |
Values |
|
Type ID |
0x01010711 |
|
OID |
1.3.6.1.4.1.25506.2.2.108 (Primary) |
|
Trap name |
nodeAlarmDiskIoSlowDetect |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Disk IO Timeout |
|
Text |
A disk IO timeout was detected in slot $3 on node $1 ($2). $1: nodeName $2: nodeIP $3: diskSlot |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
I/O timeouts occurred frequently on a disk.
In this situation, the disk might fail and the cluster will operate incorrectly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$3: Slot number. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Keep observing the storage system. The system will repair the faulty disk within two hours.
2. If the system fails to repair the faulty disk, replace the disk.
3. If the alarm notification persists, contact Technical Support.
0x01010801
Basic information
|
Item |
Values |
|
Type ID |
0x01010801 |
|
OID |
1.3.6.1.4.1.25506.2.2.82 |
|
Trap name |
nodeAlarmPowerOff |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A node was powered off |
|
Text |
Node $1 ($2) was powered off. $1: nodeName $2: nodeIP |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
A host was powered off.
In this situation, the storage services in which the host participates are interrupted temporarily. The cluster will operate incorrectly if more than half of the hosts in the cluster are powered off.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Power on the host.
0x01010802
Basic information
|
Item |
Values |
|
Type ID |
0x01010802 |
|
OID |
1.3.6.1.4.1.25506.2.2.98 |
|
Trap name |
nodeAlarmNodeFailure |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Node failure |
|
Text |
Node $1 ($2) failed. $1: nodeName $2: nodeIP |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
A host failed.
In this situation, the storage services in which the host participates are interrupted temporarily. The cluster will operate incorrectly if more than half of the hosts in the cluster are powered off.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check whether the faulty host has a network issue.
2. Check whether the faulty host is powered off and then restarted.
3. Manually acknowledge the alarm.
4. If the alarm notification persists, contact Technical Support.
0x02042011
Basic information
|
Item |
Values |
|
Type ID |
0x02042011 |
|
OID |
1.3.6.1.4.1.25506.2.2.84 |
|
Trap name |
nodeAlarmOsdOneHalfDown |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
More than half OSD of host failures |
|
Text |
Over 50% of the OSDs on host $1 ($2) are down. Host maybe down. $1: nodeName $2: nodeIP |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
More than 50% of the OSDs on a host are down.
In this situation, the host might be unable to provide services.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Repair the faulty OSDs.
0x01013232
Basic information
|
Item |
Values |
|
Type ID |
0x01013232 |
|
OID |
1.3.6.1.4.1.25506.2.2.34 |
|
Trap name |
nodeAlarmDiskState |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Host failure |
|
Text |
OSD.$1 detected a disk medium error. Please remove the error as instructed in the maintenance guide. $1: nodeOsdId |
|
Source |
DEVICE |
|
Severity |
Critical |
|
Default status |
ON |
Description
A disk medium error occurred and the disk cannot be used.
In this situation, the OSD that generates the alarm cannot be used and the data will be migrated to other OSDs.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.23(nodeOsdId) |
OCTET STRING |
$1: OSD ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Repair the faulty OSDs as instructed in the maintenance guide.
2. If the alarm persists, contact Technical Support.
0x01010803
Basic information
|
Item |
Values |
|
Type ID |
0x01010803 |
|
OID |
1.3.6.1.4.1.25506.2.2.49 |
|
Trap name |
nodeAlarmNetHighDelay |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Node NIC or Direct connected switch failure |
|
Text |
A high delay occurred on the network with IP address $2 of host $1. $1: nodeName $2: nodeIP |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The NIC or directly connected switch is faulty.
NIC error or switch error will cause high delay in the network.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check the NIC or the directly connected switch.
0x01010804
Basic information
|
Item |
Values |
|
Type ID |
0x01010804 |
|
OID |
1.3.6.1.4.1.25506.2.2.50 |
|
Trap name |
nodeAlarmNetHigherDelay |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Node NIC or Direct connected switch failure |
|
Text |
A rather high delay occurred on the network with IP address $2 of host $1. $1: nodeName $2: nodeIP |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The NIC or directly connected switch is faulty.
NIC error or switch error will cause relatively high delay in the network.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check the NIC or the directly connected switch.
0x01010805
Basic information
|
Item |
Values |
|
Type ID |
0x01010805 |
|
OID |
1.3.6.1.4.1.25506.2.2.51 |
|
Trap name |
nodeAlarmNetHighestDelay |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Node NIC or Direct connected switch failure |
|
Text |
A high delay occurred on the network with IP address $2 of host $1. $1: nodeName $2: nodeIP |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The NIC or directly connected switch is faulty.
NIC error or switch error will cause extremely high delay in the network.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check the NIC or the directly connected switch.
0x02042012
Basic information
|
Item |
Values |
|
Type ID |
0x02042012 |
|
OID |
1.3.6.1.4.1.25506.2.2.85 |
|
Trap name |
nodeAlarmOsdAllDown |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
All OSD of host failures |
|
Text |
All OSDs on host $1 ($2) are down. The host is unreachable. $1: nodeName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
Exception has occurred on all OSDs on the host.
In this situation, the host is unable to provide services.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Repair the faulty OSDs.
0x01013233
Basic information
|
Item |
Values |
|
Type ID |
0x01013233 |
|
OID |
1.3.6.1.4.1.25506.2.2.55 |
|
Trap name |
nodeAlarmBadDisk |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
OSD not available as the disk is broken |
|
Text |
Host:$1 IP:$2 OSD:$3 is not available as disk:$4 is broken. Disk slot:$5, disk ID:$6, please replace the faulty disk as instructed in the maintenance guide. $1: nodeName $2: nodeIP $3: nodeOsdId $4: diskName $5: diskSlot $6: diskid |
|
Source |
DEVICE |
|
Severity |
Critical |
|
Default status |
ON |
Description
An unrecoverable error occurred on the disk, and the disk requires replacement.
In this situation, the OSD that generates the alarm will be isolated from the cluster, which causes data migration. The services might be unstable.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2 (nodeName) |
OCTET STRING |
$1: Host name. |
|
1, 3, 6, 1, 4, 1, 25506, 1, 2, 1, 3 (nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.23 (nodeOsdId) |
OCTET STRING |
$3: OSD ID. |
|
1.3.6.1.4.1.25506.1.4.1.2 (diskName) |
OCTET STRING |
$4: Disk name. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$5: Slot number. |
|
1.3.6.1.4.1.25506.1.4.1.17(diskid) |
OCTET STRING |
$6: Disk ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
|
|
CAUTION: Do not delete the disk without authorization. |
1. Replace the disk as instructed in the maintenance guide for the product.
2. If the alarm persists, contact Technical Support.
0x01013234
Basic information
|
Item |
Values |
|
Type ID |
0x01013234 |
|
OID |
1.3.6.1.4.1.25506.2.2.56 |
|
Trap name |
nodeAlarmMediumErrTrigBadDisk |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
OSD not available as the Medium Error |
|
Text |
Host:$1 IP:$2 OSD:$3 is not available as disk:$4 is broken. Disk slot:$5, disk ID:$6, please remove the faulty disk, and then add it back to the cluster as instructed in the maintenance guide. If the alarm persists, replace the disk. $1: nodeName $2: nodeIP $3: nodeOsdId $4: diskName $5: diskSlot $6: diskid |
|
Source |
DEVICE |
|
Severity |
Critical |
|
Default status |
ON |
Description
A disk medium error occurred and the disk cannot be repaired.
In this situation, the OSD that generates the alarm will be isolated from the cluster, which causes data migration. The services might be unstable.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2 (nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIP) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.23 (nodeOsdId) |
OCTET STRING |
$3: OSD ID. |
|
1.3.6.1.4.1.25506.1.4.1.2 (diskName) |
OCTET STRING |
$4: Disk name. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$5: Slot number. |
|
1.3.6.1.4.1.25506.1.4.1.17(diskid) |
OCTET STRING |
$6: Disk ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
|
|
CAUTION: Do not delete the disk without authorization. |
1. Remove the faulty disk, and then add it back to the cluster as instructed in the maintenance guide for the product.
2. If the alarm persists, contact Technical Support.
0x02020601
Basic information
|
Item |
Values |
|
Type ID |
0x02020601 |
|
OID |
1.3.6.1.4.1.25506.2.2.57 |
|
Trap name |
nodeAlarmCpuSpecifications |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Node does not meet the CPU requirements |
|
Text |
Node $1 ($2) does not meet the CPU requirements. $1: nodeName $2: nodeIP |
|
Source |
OS |
|
Severity |
Minor |
|
Default status |
ON |
Description
The number of CPUs on the node is less than 2 or the core number of a CPU is less than 8.
In this situation, cluster performance is impacted.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check the number of CPUs and the core number of each CPU on the node.
Make sure the number of CPUs on the node is not less than 2 and the core number of each CPU is not less than 8.
0x02020701
Basic information
|
Item |
Values |
|
Type ID |
0x02020701 |
|
OID |
1.3.6.1.4.1.25506.2.2.58 |
|
Trap name |
nodeAlarmMemorySpecifications |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Node does not meet the memory requirements |
|
Text |
Node $1 ($2) does not meet the memory requirements. $1: nodeName $2: nodeIP |
|
Source |
OS |
|
Severity |
Major |
|
Default status |
ON |
Description
The total memory capacity is less than 64 GB.
In this situation, cluster performance degrades.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check the total memory capacity of the node.
Make sure the memory capacity of the node is not less than 64 GB.
0x01020001
Basic information
|
Item |
Values |
|
Type ID |
0x01020001 |
|
OID |
1.3.6.1.4.1.25506.2.2.99 |
|
Trap name |
nodeAlarmCpuIsolation |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Node CPU Isolation |
|
Text |
Node $1 ($2) is isolated, because its CPU usage has reached $3%. $1: nodeName $2: nodeIP $3: nodeCpuUtilizationRate |
|
Source |
OS |
|
Severity |
Critical |
|
Default status |
ON |
Description
The node has a much higher CPU usage than other nodes.
In this situation, the cluster will operate slower because of high CPU usage and service load.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.4(nodeCpuUtilizationRate) |
OCTET STRING |
$3: CPU usage. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Contact Technical Support.
After a troubleshooting, manually acknowledge the alarm notification.
0x01020002
Basic information
|
Item |
Values |
|
Type ID |
0x01020002 |
|
OID |
1.3.6.1.4.1.25506.2.2.100 |
|
Trap name |
nodeAlarmMemIsolation |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Node Memory Isolation |
|
Text |
Node $1 ($2) is isolated, because its memory usage has reached $3%. $1: nodeName $2: nodeIP $3: nodeCpuUtilizationRate |
|
Source |
OS |
|
Severity |
Critical |
|
Default status |
ON |
Description
The node has a much higher memory usage than other nodes.
In this situation, the cluster will operate slower because of high memory usage and service load.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.7(nodeMemUtilizationRate) |
OCTET STRING |
$3: Memory usage. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Contact Technical Support.
After a troubleshooting, manually acknowledge the alarm notification.
0x01020303
Basic information
|
Item |
Values |
|
Type ID |
0x01020303 |
|
OID |
1.3.6.1.4.1.25506.2.1.24 |
|
Trap name |
sysAlarmNtpExtAutoDisabled |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Cluster changed to inner NTP synchronizing node mode automatically |
|
Text |
The time gap between the external NTP server and nodes in the cluster is larger than 2 seconds, and the system changed the NTP source to the internal NTP server. |
|
Source |
OS |
|
Severity |
Major |
|
Default status |
ON |
Description
The time gap between the external NTP servers and the cluster is larger than two seconds.
In this situation, the cluster cannot synchronize time with the external NTP servers.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Verify that neither the time of external NTP servers outside the cluster nor the cluster time has been modified.
· If the time of external NTP servers outside the cluster or the cluster time has been modified, synchronize the time of external NTP servers outside the cluster and the cluster time.
· If neither the time of external NTP servers outside the cluster nor the cluster time has been modified, contact Technical Support.
0x02020301
Basic information
|
Item |
Values |
|
Type ID |
0x02020301 |
|
OID |
1.3.6.1.4.1.25506.2.2.59 |
|
Trap name |
nodeAlarmNtpClientStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
NTP client status |
|
Type ID |
Node $1 failed to synchronize time from the NTP server. $1: nodeName |
|
Source |
OS |
|
Severity |
Warning |
|
Default status |
ON |
Description
The NTP client is unable to synchronize time.
In this situation, the NTP client cannot synchronize time with the NTP servers.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2 (nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Verify that the NTP servers are operating correctly.
2. Verify that the network connectivity is normal for NTP clients and NTP servers.
3. If no exception exists, contact Technical Support.
0x02020304
Basic information
|
Item |
Description |
|
Type ID |
0x02020304 |
|
OID |
1.3.6.1.4.1.25506.2.2.60 |
|
Trap name |
nodeAlarmNtpOffset |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Offset with NTP server |
|
Text |
The time gap between node $1 and NTP server $2 is $3 milliseconds. $1: nodeName $2: nodeNtpServerIp $3: nodeNtpServerOffset |
|
Source |
OS |
|
Severity |
Major |
|
Default status |
ON |
Description
The time gap between the external NTP server and the nodes has exceeded the threshold.
In this situation, exception occurs on time synchronization.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.31(nodeNtpServerIp) |
OCTET STRING |
$2: nodeNtpServerIp. |
|
1.3.6.1.4.1.25506.1.2.1.32(nodeNtpServerOffset) |
OCTET STRING |
$3: nodeNtpServerOffset. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Verify that the NTP servers are operating correctly.
2. Verify that the network connectivity is normal for NTP clients and NTP servers.
3. If no exception exists, contact Technical Support.
0x02020302
Basic information
|
Item |
Description |
|
Type ID |
0x02020302 |
|
OID |
1.3.6.1.4.1.25506.2.2.61 |
|
Trap name |
nodeAlarmNtpChange |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
NTP external server status |
|
Text |
Node $1 synchronized time from the internal NTP server instead of the external NTP server. $1: nodeName |
|
Source |
OS |
|
Severity |
Major |
|
Default status |
ON |
Description
The time gap between the external NTP servers outside the cluster and the nodes has exceeded the threshold.
In this situation, exception occurs on time synchronization.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
Unsigned32 |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Verify that the NTP servers outside the cluster are operating correctly.
2. Verify that the network connectivity is normal for NTP clients and NTP servers.
3. If no exception exists, contact Technical Support.
0x02030401
Basic information
|
Item |
Description |
|
Type ID |
0x02030401 |
|
OID |
1.3.6.1.4.1.25506.2.1.23 |
|
Trap name |
sysAlarmLicsServerErr |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
License server sync fail |
|
Text |
Failed to synchronize data from the license server. |
|
Source |
NET |
|
Severity |
Critical |
|
Default status |
ON |
Description
License server synchronization failed.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
Unsigned32 |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Verify that the license server is operating correctly.
2. Verify that the network connectivity is normal between the management node and the license server.
3. If the alarm persists, contact Technical Support.
0x02020401
Basic information
|
Item |
Description |
|
Type ID |
0x02020401 |
|
OID |
1.3.6.1.4.1.25506.2.2.74 |
|
Trap name |
nodeAlarmProcessMemoryUsage |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Memory used by the process has exceeded the threshold |
|
Text |
The memory usage of process $3 on node $1 ($2) is $4, which has exceeded the threshold $5. $1: nodeName $2: nodeIp $3: nodeProcess $4: nodeMemUtilizationRate $5: nodeMemUtilizationThreshold |
|
Source |
OS |
|
Severity |
Major |
|
Default status |
ON |
Description
The memory usage of a process on a node has exceeded the threshold.
In this situation, a memory leak might occur, which causes system exception.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.33(nodeProcess) |
OCTET STRING |
$3: Process. |
|
1.3.6.1.4.1.25506.1.2.1.7(nodeMemUtilizationRate) |
OCTET STRING |
$3: Memory usage of the process. |
|
1.3.6.1.4.1.25506.1.2.1.13(nodeMemUtilizationThreshold) |
OCTET STRING |
$4: Memory usage threshold. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
Unsigned32 |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Verify that no memory leak occurs.
0x02040129
Basic information
|
Item |
Description |
|
Type ID |
0x02040129 |
|
OID |
1.3.6.1.4.1.25506.2.1.26 |
|
Trap name |
sysAlarmPatchStatus |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Patch_warn |
|
Text |
Cluster has patch status warning, please check patches on host $1 $1: nodeName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The patch state is abnormal.
In this situation, one of the following situations might exist:
· A patch on a node in the cluster does not finish installation.
· The version of the operating patch on a node is not consistent with the baseline version of the cluster.
· The patch configuration file is corrupted.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
Unsigned32 |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Verify that the network of the nodes is normal.
2. Verify that the version of the operating patches is consistent with the baseline version of the cluster.
3. Verify that the patches of all node roles are installed.
4. Verify that the configuration files on the nodes are not modified.
5. If the alarm occurs during patch installation or uninstallation, no action is required. The alarm is removed automatically after installation or uninstallation.
6. If the alarm persists, contact Technical Support.
0x02040130
Basic information
|
Item |
Description |
|
Type ID |
0x02040130 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB.mib |
|
Metric |
AI Engine container state alarm |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The node has a docker service issue or AI Engine container issue.
Objects
N/A
Recommended action
1. Contact Technical Support.
2. Perform one of the following tasks:
¡ Check the docker service state of the node. If the docker service is in an abnormal state, restore its state to active.
¡ Check the AI Engine container state of the node. If the AI Engine container is in an abnormal state, restore its state to UP.
0x02040801
Basic information
|
Item |
Description |
|
Type ID |
0x02040801 |
|
OID |
1.3.6.1.4.1.25506.2.3.32 |
|
Trap name |
blockAlarmTrashUsage |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Exceeding the upper limit of trash lun |
|
Text |
The number of storage volumes in the recycle bin almost reaches the upper limit. |
|
Source |
CLUSTER |
|
Severity |
Warning |
|
Default status |
ON |
Description
The number of storage volumes in the recycle bin has reached the alarm threshold.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Recover or destroy the volumes in the recycle bin.
0x02010706
Basic information
|
Item |
Description |
|
Type ID |
0x02010706 |
|
OID |
1.3.6.1.4.1.25506.2.2.66 |
|
Trap name |
nodeAlarmSlowDiskSoftEnv |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Slow disk appears |
|
Text |
Host:$1 IP:$2 OSD:$3 disk $4 is slow. $1: nodeName $2: nodeIp $3: nodeOsdId $4: diskName |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The disk is operating incorrectly and has I/O timeouts.
In this situation, storage performance degrades.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.23(nodeOsdId) |
OCTET STRING |
$3: OSD ID. |
|
1.3.6.1.4.1.25506.1.4.1.2(diskName) |
OCTET STRING |
$4: Disk name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Repair the faulty disk or replace it with a new disk.
0x02010707
Basic information
|
Item |
Description |
|
Type ID |
0x02010707 |
|
OID |
1.3.6.1.4.1.25506.2.2.62 |
|
Trap name |
nodeAlarmSlowDisk |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Slow disk appears(AIO) |
|
Text |
Host:$1 IP:$2 OSD:$3 disk $4 is slow. Slot: $5. $1: nodeName $2: nodeIp $3: nodeOsdId $4: diskName $5: diskSlot |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The disk is operating incorrectly and has I/O timeouts.
In this situation, storage performance degrades.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.23(nodeOsdId) |
OCTET STRING |
$3: OSD ID. |
|
1.3.6.1.4.1.25506.1.4.1.2(diskName) |
OCTET STRING |
$4: Disk name. |
|
1.3.6.1.4.1.25506.1.4.1.18(diskSlot) |
OCTET STRING |
$5: Slot number. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Repair the faulty disk or replace it with a new disk.
0x02010708
Basic information
|
Item |
Description |
|
Type ID |
0x02010708 |
|
OID |
1.3.6.1.4.1.25506.2.2.63 |
|
Trap name |
nodeAlarmDiskIOTimeout |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
IO timeout |
|
Text |
Host:$1 IP:$2 OSD:$3 has an I/O timeout issue. $1: nodeName $2: nodeIp $3: nodeOsdId |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The cause of this issue is uncertain. You need to find out the cause according to the actual condition.
In this situation, storage performance degrades seriously.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.23(nodeOsdId) |
OCTET STRING |
$3: OSD ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
No immediate action is required. The cluster will solve this issue automatically.
If this issue persists for more than 12 hours, contact Technical Support.
0x02010709
Basic information
|
Item |
Description |
|
Type ID |
0x02010709 |
|
OID |
1.3.6.1.4.1.25506.2.2.64 |
|
Trap name |
nodeAlarmExternIOTimeout |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
IO timeout(external check) |
|
Text |
Host:$1 IP:$2 OSD:$3 has an external I/O timeout issue. $1: nodeName $2: nodeIp $3: nodeOsdId |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The cause of this issue is uncertain. You need to find out the cause according to the actual condition.
In this situation, storage performance degrades seriously.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.23(nodeOsdId) |
OCTET STRING |
$3: OSD ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
No immediate action is required. The cluster will solve this issue automatically.
If this issue persists for more than 12 hours, contact Technical Support.
0x02010710
Basic information
|
Item |
Description |
|
Type ID |
0x02010710 |
|
OID |
1.3.6.1.4.1.25506.2.2.65 |
|
Trap name |
nodeAlarmOsdAssert |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
OSD assert appears |
|
Text |
Host:$1 IP:$2 OSD:$3 had an assertion. $1: nodeName $2: nodeIp $3: nodeOsdId |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The OSD had an assertion. In this situation, the OSD will go down and quit the process. The cluster might then operate incorrectly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.23(nodeOsdId) |
OCTET STRING |
$3: OSD ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
No immediate action is required. The cluster will solve this issue automatically.
If this issue persists for more than 12 hours, contact Technical Support.
0x02010711
Basic information
|
Item |
Description |
|
Type ID |
0x02010711 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
BAD CRC |
|
Text |
N/A |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The OSD had a data verification error.
In this situation, the OSD has a data error. The cluster might then operate incorrectly.
Objects
N/A
Recommended action
No immediate action is required. The cluster will solve this issue automatically.
If this issue persists for more than 12 hours, contact Technical Support.
0x02010712
Basic information
|
Item |
Description |
|
Type ID |
0x02010712 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
OSD IO timeout(internal check) |
|
Text |
N/A |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The OSD had an I/O timeout during internal check.
In this situation, the cluster might operate incorrectly.
Objects
N/A
Recommended action
No immediate action is required. The cluster will solve this issue automatically.
If this issue persists for more than 12 hours, contact Technical Support.
0x02043001
Basic information
|
Item |
Description |
|
Type ID |
0x02043001 |
|
OID |
1.3.6.1.4.1.25506.2.2.71 |
|
Trap name |
nodeAlarmOsdDown |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
OSD service error |
|
Text |
Host:$1 ($2) OSD:$3 became abnormal. $1: nodeName $2: nodeIp $3: nodeOsdId |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The OSD runs incorrectly.
In this situation, the OSD has a data error. The cluster might operate incorrectly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.23(nodeOsdId) |
OCTET STRING |
$3: OSD ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check whether the node where the faulty OSD resides has a network connectivity issue.
· If the node has no network connectivity issues, do the following:
a. Log in to that node, and then restart the OSD.
In Ubuntu, execute the restart ceph-OSD id={id} command to restart the OSD.
In CentOS, execute the systemctl restart ceph-OSD@{id}.service command to restart the OSD.
b. Check whether the OSD operates correctly.
If the issue persists, contact Technical Support.
· If the node has a network connectivity issue, solve that issue, and then check whether the OSD operates correctly.
0x01010102
Basic information
|
Item |
Description |
|
Type ID |
0x01010102 |
|
OID |
1.3.6.1.4.1.25506.2.2.67 |
|
Trap name |
nodeAlarmCpuModuleAbsent |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A CPU module is not in place |
|
Text |
CPU module $3 on node $1 ($2) is not in place. $1: nodeName $2: nodeIp $3: nodeCpuModule |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The CPU module is absent or has a poor contact with the host.
In this situation, the system will operate incorrectly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.24(nodeCpuModule) |
OCTET STRING |
$3: CPU module. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check whether the CPU is absent. If yes, install it correctly.
2. Check whether the socket of the CPU is faulty. If yes, manually repair it.
3. If the issue persists, contact Technical Support.
0x01010202
Basic information
|
Item |
Description |
|
Type ID |
0x01010202 |
|
OID |
1.3.6.1.4.1.25506.2.2.68 |
|
Trap name |
nodeAlarmMemoryModuleAbsent |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A memory module is not in place |
|
Text |
Memory module $3 on node $1 ($2) is not in place. $1: nodeName $2: nodeIp $3: nodeMemModule |
|
Source |
DEVICE |
|
Severity |
Warning |
|
Default status |
OFF |
Description
The memory module is absent or has a poor contact with the host.
In this situation, the system will operate incorrectly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.25(nodeMemModule) |
OCTET STRING |
$3: Memory module. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check whether the memory module is absent. If yes, install it correctly.
2. Check whether the memory module has a poor contact with the host. If yes, manually repair it.
3. If the issue persists, contact Technical Support.
0x01010302
Basic information
|
Item |
Description |
|
Type ID |
0x01010302 |
|
OID |
1.3.6.1.4.1.25506.2.2.69 |
|
Trap name |
nodeAlarmFanModuleAbsent |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A fan module is not in place |
|
Text |
Fan module $3 on node $1 ($2) is not in place. $1: nodeName $2: nodeIp $3: nodeFanModule |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
The fan module is pulled out or has a poor contact with the host.
In this situation, the system will operate incorrectly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.26(nodeFanModule) |
OCTET STRING |
$3: Fan module. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check whether the fan module is absent. If yes, install it correctly.
2. Check whether the fan module has a poor contact with the host. If yes, manually repair it.
3. If the issue persists, contact Technical Support.
0x01010402
Basic information
|
Item |
Description |
|
Type ID |
0x01010402 |
|
OID |
1.3.6.1.4.1.25506.2.2.70 |
|
Trap name |
nodeAlarmPowerModuleAbsent |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A power module is not in place |
|
Text |
Power module $3 on node $1 ($2) is not in place. $1: nodeName $2: nodeIp $3: nodeMemModule |
|
Source |
DEVICE |
|
Severity |
Warning |
|
Default status |
ON |
Description
The host is powered off or has a poor contact with the power module.
In this situation, the system will operate incorrectly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.3(nodeIp) |
OCTET STRING |
$2: Host IP. |
|
1.3.6.1.4.1.25506.1.2.1.27(nodePwrModule) |
OCTET STRING |
$3: Power module. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check whether the power module is absent. If yes, install it correctly.
2. Check whether the memory module has a poor contact with the host. If yes, manually repair it.
3. If the issue persists, contact Technical Support.
0x02020604
Basic information
|
Item |
Description |
|
Type ID |
0x02020604 |
|
OID |
1.3.6.1.4.1.25506.2.1.31 |
|
Trap name |
sysAlarmSendMailFailed |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Email sending failure |
|
Text |
Failed to send the email notification. |
|
Source |
OS |
|
Severity |
Major |
|
Default status |
ON |
Description
This issue might occur in one of the following conditions:
· The email service is not configured.
· The email service is not enabled.
· Connection to the email server cannot be established.
· Email server authentication fails.
· The reception email address is incorrect.
When this issue occurs, the user cannot view the alarm notification immediately.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check whether the email server operates correctly. If no, recover it.
2. Check whether the email service is enabled. If no, enable it.
3. Check whether the email server has a network connectivity issue. If yes, recover it.
4. Check whether the username and password is correct.
5. Check whether the reception email address is valid and effective. If the email address is invalid, reconfigure the reception email address.
6. Check whether the reception email address has sufficient space for email reception. If no, delete the useless emails or expand the email space.
7. If the issue persists, contact Technical Support.
0x01042015
Basic information
|
Item |
Description |
|
Type ID |
0x01042015 |
|
OID |
1.3.6.1.4.1.25506.2.1.8 |
|
Trap name |
sysAlarmMonitorStatus |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Cluster MON-DOWN |
|
Text |
Cluster $1 monitor node $2 became abnormal. |
|
Source |
CLUSTER |
|
Severity |
Critical |
|
Default status |
ON |
Description
The monitor node failed and cannot provide monitoring services temporarily.
If more than 50% of the monitor nodes in the cluster fail, the cluster will operate incorrectly.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.2.1.2 (sysMonitors) |
OCTET STRING |
Monitor node name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Log in to the management page of the cluster.
2. From the navigation pane, select Hosts.
3. Select Monitor Nodes.
4. Check the status of monitor nodes.
If a monitor node is in an abnormal state, access the monitor node to check for its ceph-mon daemon.
a. Start the daemon if it is not running.
In Ubuntu, execute the start ceph-mon-all command to start the daemon.
In CentOS, execute the systemctl start ceph-mon.target command to start the daemon.
b. Two minutes later, check for the daemon again.
c. If the daemon is not running, contact Technical Support.
0x01042016
Basic information
|
Item |
Description |
|
Type ID |
0x01042016 |
|
OID |
1.3.6.1.4.1.25506.2.1.32 |
|
Trap name |
clusterMONNum |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Inappropriate number of monitor nodes |
|
Text |
The number of monitor nodes changed to an even number $2. $2: sysMonitorNumber |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The number of monitor nodes is even.
In this situation, the cluster cannot elect a new active monitor node when the original active monitor node fails.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
$1: Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.18 (sysMonitorNumber) |
OCTET STRING |
$2: Number of monitor nodes. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Delete a monitor node from the cluster or add a monitor node to the cluster. Make sure the number of monitor nodes is odd.
0x01042016
Basic information
|
Item |
Description |
|
Type ID |
0x01030104 |
|
OID |
1.3.6.1.4.1.25506.2.2.108 (Branch 50) |
|
Trap name |
nodeAlarmNetworkClusterCardFault |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Bond network port is abnormal |
|
Text |
NIC $2 on host $1 became abnormal. $1: nodeName $2: nodeNetCardName |
|
Source |
NET |
|
Severity |
Major |
|
Default status |
ON |
Description
A NIC on the back-end network of the cluster failed.
In this situation, the cluster might have a network connectivity issue.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.38 (nodeNetCardIP) |
OCTET STRING |
NIC IP. |
|
1.3.6.1.4.1.25506.1.2.1.39(nodeNetCardName) |
OCTET STRING |
$2: NIC name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check for abnormal NICs, and then recover their network connections.
If the issue persists, contact Technical Support.
0x01030105
Basic information
|
Item |
Description |
|
Type ID |
0x01030105 |
|
OID |
1.3.6.1.4.1.25506.2.2.109 |
|
Trap name |
nodeAlarmNetworkPublicCardFault |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Bond network port is abnormal |
|
Text |
NIC $2 on host $1 became abnormal. $1: nodeName $2: nodeNetCardName |
|
Source |
NET |
|
Severity |
Major |
|
Default status |
ON |
Description
A NIC on the front-end network of the cluster failed.
In this situation, the cluster might have a network connectivity issue.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.38 (nodeNetCardIP) |
OCTET STRING |
NIC IP. |
|
1.3.6.1.4.1.25506.1.2.1.39(nodeNetCardName) |
OCTET STRING |
$2: NIC name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check for abnormal NICs, and then recover their network connections.
If the issue persists, contact Technical Support.
NAS server in file storage
This section contains notifications generated by the NAS server modules in file storage.
0x01042307
Basic information
|
Item |
Description |
|
Type ID |
0x01042307 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The es sync service is abnormal |
|
Text |
N/A |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
The sync state of metadata search is abnormal.
In this situation, metadata search service is not available.
Objects
N/A
Recommended action
1. Check whether the sync nodes of metadata search have network connectivity issues.
2. If the alarm persists for more than 10 minutes, contact Technical Support.
0x01042308
Basic information
|
Item |
Description |
|
Type ID |
0x01042308 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The haproxy service is abnormal |
|
Text |
N/A |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
The HA state of the metadata search engine is abnormal.
In this situation, metadata search service is not available.
Objects
N/A
Recommended action
1. Check whether the HA nodes of the metadata search engine have network connectivity issues.
2. If the alarm persists for more than 10 minutes, contact Technical Support.
0x01042309
Basic information
|
Item |
Description |
|
Type ID |
0x01042309 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The elasticsearch service is abnormal |
|
Text |
N/A |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
The metadata search engine is faulty.
In this situation, metadata search service is not available.
Objects
N/A
Recommended action
1. Check whether the metadata search engine nodes have network connectivity issues.
2. If the alarm persists for more than 10 minutes, contact Technical Support.
0x01042310
Basic information
|
Item |
Description |
|
Type ID |
0x01042310 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Metadata search service state |
|
Text |
N/A |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
The state of metadata search service is abnormal.
In this situation, metadata search service is not available.
Objects
N/A
Recommended action
1. Check whether the nodes that provide metadata search services have network connectivity issues.
2. If the alarm persists for more than 10 minutes, contact Technical Support.
0x02055001
Basic information
|
Item |
Description |
|
Type ID |
0x02055001 |
|
OID |
1.3.6.1.4.1.25506.2.2.38 |
|
Trap name |
nodeAlarmSmbdStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
CIFS service error |
|
Text |
Server $1. CIFS service error $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
If this alarm occurs, the NAS server cannot operate correctly and DIP migration is present. Storage services might be unstable or be interrupted and the NAS group might be unmanageable from the Web interface.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: nodeName. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Access the CLI of the abnormal NAS server to identify the service that is using port 445, and then terminate the service.
2. If the alarm persists, contact Technical Support.
0x02054963
Basic information
|
Item |
Description |
|
Type ID |
0x02054963 |
|
OID |
1.3.6.1.4.1.25506.2.2.39 |
|
Trap name |
nodeAlarmWinbindStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
User mapping service error |
|
Text |
Server $1. User mapping service error. $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
If this alarm occurs, the NAS server cannot operate correctly and DIP migration is present. Storage services might be unstable or be interrupted and the NAS group might be unmanageable from the Web interface.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Make sure the network connectivity is normal for the cluster and the AD server.
2. If the network connectivity is normal, execute the service smbd restart command on the abnormal NAS server to restart Samba.
3. If the alarm persists, contact Technical Support.
0x02054901
Basic information
|
Item |
Description |
|
Type ID |
0x02054901 |
|
OID |
1.3.6.1.4.1.25506.2.2.39 |
|
Trap name |
nodeAlarmWinbindStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
User mapping service error |
|
Text |
Server $1. User mapping service error $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
If this alarm occurs, the NAS server cannot operate correctly and DIP migration is present. Storage services might be unstable or be interrupted and the NAS group might be unmanageable from the Web interface.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Make sure the network connectivity is normal for the cluster and the AD server.
2. If the network connectivity is normal, execute the service smbd restart command on the abnormal NAS server to restart Samba.
3. If the alarm persists, contact Technical Support.
0x02055101
Basic information
|
Item |
Description |
|
Type ID |
0x02055101 |
|
OID |
1.3.6.1.4.1.25506.2.2.40 |
|
Trap name |
nodeAlarmNmbdStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Name service error |
|
Text |
Server $1. Name service error $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
If this alarm occurs, the NAS server cannot operate correctly and DIP migration is present. Storage services might be unstable or be interrupted and the NAS group might be unmanageable from the Web interface.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Access the CLI of the abnormal NAS server to identify the services that are using ports 137 and 138, and then terminate the services.
2. If the alarm persists, contact Technical Support.
0x02054863
Basic information
|
Item |
Description |
|
Type ID |
0x02054863 |
|
OID |
1.3.6.1.4.1.25506.2.2.41 |
|
Trap name |
nodeAlarmAdsStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The NAS node is not in the AD domain |
|
Text |
Server $1. The NAS node is not in the AD domain $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
The NAS server is not in the AD domain.
If the alarm occurs, the AD service is not available.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Make sure the following requirements are met:
¡ The cluster and AD server has network connectivity.
¡ The time skew between the cluster and the AD server is less than five minutes.
¡ The AD server and the DNS server are operating correctly.
2. If the alarm is not cleared, reset AD authentication.
3. If the alarm persists, contact Technical Support.
0x02056001
Basic information
|
Item |
Description |
|
Type ID |
0x02056001 |
|
OID |
1.3.6.1.4.1.25506.2.2.42 |
|
Trap name |
nodeAlarmNfsStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
NFS service error |
|
Text |
Server $1. NFS service error $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
If this alarm occurs, the NAS server cannot operate correctly and DIP migration is present. Storage services might be unstable or be interrupted and the NAS group might be unmanageable from the Web interface.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Access the CLI of the abnormal NAS server to identify the service that is using port 2049, and then terminate the service.
2. If the alarm persists, contact Technical Support.
0x01040387
Basic information
|
Item |
Description |
|
Type ID |
0x01040387 |
|
OID |
1.3.6.1.4.1.25506.2.2.43 |
|
Trap name |
nodeAlarmUmountFail |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to unmount the file system while deleting the NAS node |
|
Text |
Server $1. Failed to unmount the file system while deleting the NAS node $1: nodeName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
During NAS node deletion, an error was reported that the file system unmounting failed.
If this alarm occurs, the NAS server cannot operate correctly and DIP migration is present. Storage services might be unstable or be interrupted and the NAS group might be unmanageable from the Web interface.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Unmount the file system from the NAS node if the file system is mounted.
2. If the alarm persists, contact Technical Support.
0x02050101
Basic information
|
Item |
Description |
|
Type ID |
0x02050101 |
|
OID |
1.3.6.1.4.1.25506.2.2.44 |
|
Trap name |
nodeAlarmMdsSessionStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
MDS session error |
|
Text |
Server $1. MDS session error $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
If this alarm occurs, the NAS server cannot operate correctly and DIP migration is present. Storage services might be unstable or be interrupted and the NAS group might be unmanageable from the Web interface.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check the cluster health. If the cluster is not healthy, manually recover the cluster health.
2. Verify that the directory debugs has been mounted correctly. If the directory is not mounted, mount it.
3. If the file system has multiple mounts, Perform unmounting operations to make sure the file system has only one mount.
4. Remount the file system to the abnormal node.
5. If the alarm persists, contact Technical Support.
0x02050201
Basic information
|
Item |
Description |
|
Type ID |
0x02050201 |
|
OID |
1.3.6.1.4.1.25506.2.2.72 |
|
Trap name |
nodeAlarmGaneshaMdsSessionStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Ganesha mds session error |
|
Text |
Server $1. Ganesha MDS session error $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
If this alarm occurs, the NAS server has a Ganesha session error. Storage services might be unstable or be interrupted and the NAS group might be unmanageable from the Web interface.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check the cluster health. If the cluster is not healthy, manually recover the cluster health.
2. Verify that the Ganesha daemon exists on the NAS server.
3. If the alarm persists, contact Technical Support.
0x02050301
Basic information
|
Item |
Description |
|
Type ID |
0x02050301 |
|
OID |
1.3.6.1.4.1.25506.2.2.73 |
|
Trap name |
nodeAlarmSmbdMdsSessionStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
MDS session error |
|
Text |
Server $1. SMBD MDS session error $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
If this alarm occurs, the NAS server has an SMBD session error. Storage services might be unstable or be interrupted and the NAS group might be unmanageable from the Web interface.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check the cluster health. If the cluster is not healthy, manually recover the cluster health.
2. Verify that the SMBD daemon exists on the NAS server.
3. If the alarm persists, contact Technical Support.
0x02055260
Basic information
|
Item |
Description |
|
Type ID |
0x02055260 |
|
OID |
1.3.6.1.4.1.25506.2.2.45 |
|
Trap name |
nodeAlarmLdapNoExist |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The process NSLCD does not exist |
|
Text |
Server $1. The process nslcd doesn't exist $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
The service nslcd is abnormal.
If this alarm occurs, the LDAP service is not available.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Verify that the process nslcd is normal. If the process does not exist, execute the service nslcd restart command on the abnormal node.
2. If the alarm persists, contact Technical Support.
0x02055261
Basic information
|
Item |
Description |
|
Type ID |
0x02055261 |
|
OID |
1.3.6.1.4.1.25506.2.2.52 |
|
Trap name |
nodeAlarmLdapNoInstalled |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
NSLCD is not installed |
|
Text |
Server $1. nslcd isn't installed $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
The command nslcd has not been installed.
If this alarm occurs, the LDAP service is not available.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Verify that the process nslcd is normal. If the process does not exist, execute the service nslcd restart command on the abnormal node.
2. If the alarm persists, contact Technical Support.
0x02055262
Basic information
|
Item |
Description |
|
Type ID |
0x02055262 |
|
OID |
1.3.6.1.4.1.25506.2.2.53 |
|
Trap name |
nodeAlarmLdapNoJoined |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
NAS doesn’t have LDAP |
|
Text |
Server $1. NAS doesn't have LDAP $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
No LDAP domain has been configured on the NAS node.
If this alarm occurs, the NAS node is not available.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Add the NAS node to an LDAP domain from the Web interface.
2. If the alarm persists, contact Technical Support.
0x02055263
Basic information
|
Item |
Description |
|
Type ID |
0x02055263 |
|
OID |
1.3.6.1.4.1.25506.2.2.54 |
|
Trap name |
nodeAlarmLdapJoinFailed |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The NAS node is not in the LDAP domain |
|
Text |
Server $1. NAS isn't in LDAP $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
No LDAP domain has been configured on the NAS node.
If this alarm occurs, the NAS node is not available.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check the cluster and the LDAP server for network connectivity.
2. Verify that the LDAP is operating correctly.
3. If the alarm persists, contact Technical Support.
0x02054001
Basic information
|
Item |
Description |
|
Type ID |
0x02054001 |
|
OID |
1.3.6.1.4.1.25506.2.2.46 |
|
Trap name |
nodeAlarmFtpStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
FTP service error |
|
Text |
Server $1. FTP service error $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
Exception occurs on the FTP service.
If this alarm occurs, the NAS server cannot operate correctly and DIP migration is present. Storage services might be unstable or be interrupted and the NAS group might be unmanageable from the Web interface.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Add FTP share users or enable anonymous access mode.
2. Access the CLI of the NAS server to identify the process that is using FTP port 21, and then terminate the process.
3. If the alarm persists, contact Technical Support.
0x02051001
Basic information
|
Item |
Description |
|
Type ID |
0x02051001 |
|
OID |
1.3.6.1.4.1.25506.2.2.47 |
|
Trap name |
nodeAlarmPubEthStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
All NICs are disconnected |
|
Text |
Server $1. All NICs are disconnected $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
If this alarm occurs, the NAS server cannot operate correctly and DIP migration is present. Storage services might be unstable or be interrupted and the NAS group might be unmanageable from the Web interface.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Reconnect the disconnected NICs to recover network connectivity.
2. If the alarm persists, contact Technical Support.
0x02051063
Basic information
|
Item |
Description |
|
Type ID |
0x02051063 |
|
OID |
1.3.6.1.4.1.25506.2.2.48 |
|
Trap name |
nodeAlarmPartPubEthStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Some NICs are disconnected |
|
Text |
Server $1. Some NICs are disconnected $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
If this alarm occurs, DIP migration is present. Storage services might be unstable or be interrupted.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Reconnect the disconnected NICs to recover network connectivity.
2. If the alarm persists, contact Technical Support.
0x02054862
Basic information
|
Item |
Description |
|
Type ID |
0x02054862 |
|
OID |
1.3.6.1.4.1.25506.2.4.9 |
|
Trap name |
nasAlarmAdsTimeoutOID |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Network Connection Exception from the NAS node to the AD domain |
|
Text |
Server $1. The network connection between the NAS server and the AD server became abnormal. $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
If this alarm occurs, AD authentication is not available.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check whether the AD server is started. If no, start the AD server.
2. If the alarm persists, contact Technical Support.
0x02057001
Basic information
|
Item |
Description |
|
Type ID |
0x02057001 |
|
OID |
1.3.6.1.4.1.25506.2.2.83 |
|
Trap name |
nodeAlarmHttpStat |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
HTTP service error |
|
Text |
Server $1. HTTP service error $1: nodeName |
|
Source |
NAS |
|
Severity |
Major |
|
Default status |
ON |
Description
Exception occurs on the HTTP service.
If this alarm occurs, the management node might fail to communicate with the faulty node.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Access the CLI of the faulty node to identify the process that is using port 18090, and then terminate the process.
2. If the alarm persists, contact Technical Support.
Snapshot management in file storage
This section contains notifications about the snapshot management module in file storage.
0x01040382
Basic information
|
Item |
Description |
|
Type ID |
0x01040382 |
|
OID |
1.3.6.1.4.1.25506.2.3.16 |
|
Trap name |
blockAlarmSnapshotRollbackNospaceleft |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The system does not have sufficient resources to restore the snapshot |
|
Text |
The system does not have sufficient resources to restore snapshot $1 $1: appSnapShotName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when the capacity for snapshot restoration is insufficient.
In this situation, the snapshot restoration task will fail.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.12(appSnapShotName) |
OCTET STRING |
$1: Snapshot name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Expand the cluster.
0x01040383
Basic information
|
Item |
Description |
|
Type ID |
0x01040383 |
|
OID |
1.3.6.1.4.1.25506.2.3.17 |
|
Trap name |
blockAlarmSnapshotRollbackNoQuota |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The quota does not have sufficient resources to restore the snapshot |
|
Text |
The quota does not have sufficient resources to restore snapshot $1 $1: appSnapShotName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when the quota for snapshot restoration is insufficient.
In this situation, the restoration task will fail.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.12(appSnapShotName) |
OCTET STRING |
$1: Snapshot name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Verify that the quota is sufficient. If the quota is insufficient, expand the quota for the target directory.
2. If the alarm persists, contact Technical Support.
0x01040384
Basic information
|
Item |
Description |
|
Type ID |
0x01040384 |
|
OID |
1.3.6.1.4.1.25506.2.3.18 |
|
Trap name |
blockAlarmSnapshotRollbackNoAuthority |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Snapshot operate failed |
|
Text |
The system does not have sufficient resources to restore snapshot $1 $1: appSnapShotName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when the system is not authorized to use some files or directories.
In this situation, the restoration task will fail.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.12(appSnapShotName) |
OCTET STRING |
$1: Snapshot name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check whether WORM, quota, or other related features are set in the snapshot directory. If those features are set, remove the settings and perform the snapshot restoration again.
2. If the alarm persists, contact Technical Support.
0x01040388
Basic information
|
Item |
Description |
|
Type ID |
0x01040388 |
|
OID |
1.3.6.1.4.1.25506.2.3.19 |
|
Trap name |
blockAlarmSnapshotRollbackNoEmpty |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
There is currently writing IOs in snap dirs, or the NAS node has an exception, snapshot rollback failed |
|
Text |
The system rollback snapshot $1 failed, remove some non-empty dirs $1: appSnapShotName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when snapshot restoration failed because of data writes during rollback.
In this situation, the snapshot restoration task will fail.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.12(appSnapShotName) |
OCTET STRING |
$1: Snapshot name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Perform snapshot restoration after stopping writing data.
2. If the alarm persists, contact Technical Support.
0x01040385
Basic information
|
Item |
Description |
|
Type ID |
0x01040385 |
|
OID |
1.3.6.1.4.1.25506.2.3.20 |
|
Trap name |
blockAlarmSnapshotCreateExceed1 |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to create the scheduled snapshot. The number of snapshots for the directory has reached the limit of 1024 |
|
Text |
Failed to create the scheduled snapshot. The number of snapshots for the directory has reached the limit of 1024 |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The number of snapshots in a directory has exceeded 1024.
In this situation, creating a snapshot schedule failed.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Delete useless snapshots.
2. If the alarm persists, contact Technical Support.
0x01040386
Basic information
|
Item |
Description |
|
Type ID |
0x01040386 |
|
OID |
1.3.6.1.4.1.25506.2.3.21 |
|
Trap name |
blockAlarmSnapshotCreateExceed2 |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to create the scheduled snapshot. The number of snapshots in the cluster has reached the limit of 8192 |
|
Text |
Failed to create the scheduled snapshot. The number of snapshots in the cluster has reached the limit of 8192 |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The number of snapshots in the cluster has exceeded 8192.
In this situation, creating a snapshot schedule failed.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Delete useless snapshots.
2. If the alarm persists, contact Technical Support.
0x01040389
Basic information
|
Item |
Description |
|
Type ID |
0x01040389 |
|
OID |
1.3.6.1.4.1.25506.2.3.22 |
|
Trap name |
blockAlarmSnapshotRollbackHardlink |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Not support rollback snap with hard links without keeping new data, snapshot rollback failed |
|
Text |
Not support rollback snap with hard links without keeping new data, snapshot $1 rollback failed $1: appSnapShotName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when a hard link exists in the directory and the restore type of deleting new data is selected.
In this situation, snapshot restoration will fail.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.12(appSnapShotName) |
OCTET STRING |
$1: Snapshot name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check the directory for hard links. If hard links exist, select the restore type of retaining new data.
2. If the alarm persists, contact Technical Support.
0x01040391
Basic information
|
Item |
Description |
|
Type ID |
0x01040391 |
|
OID |
1.3.6.1.4.1.25506.2.4.15 |
|
Trap name |
nasAlarmSnapStraydirsExceed |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The total number of subdirectories deleted from directories that have snapshots has reached the limit |
|
Text |
MDS:$1. The total number of subdirectories deleted from directories that have snapshots has reached the limit. $1: appSnapShotName |
|
Source |
CLUSTER |
|
Severity |
Warning |
|
Default status |
ON |
Description
The total number of subdirectories deleted from directories that have snapshots has reached the limit.
In this situation, snapshot restoration will fail.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.12(appSnapShotName) |
OCTET STRING |
$1: Snapshot name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Delete a minimum of one snapshot, and then check whether the alarm is cleared.
2. If the alarm persists, contact Technical Support.
0x01040392
Basic information
|
Item |
Description |
|
Type ID |
0x01040392 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to get the rollback task list of the snapshot, the snapshot rollback operation failed |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when the system failed to get the rollback task list of the snapshot.
In this situation, snapshot restoration will fail.
Objects
N/A
Recommended action
1. Check whether the cluster has a high service load or a network connectivity issue, and then solve the detected issues.
2. Manually acknowledge the alarm.
3. If the alarm persists, contact Technical Support.
0x01040393
Basic information
|
Item |
Description |
|
Type ID |
0x01040393 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
There are long subdirectories or files in the snapshot directory. The snapshot rollback operation fails |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when long subdirectories or files exist in the snapshot directory.
In this situation, snapshot restoration will fail.
Objects
N/A
Recommended action
1. Check whether long subdirectories or files exist in the snapshot directory.
2. Manually acknowledge the alarm.
3. If the alarm persists, contact Technical Support.
0x01040394
Basic information
|
Item |
Description |
|
Type ID |
0x01040394 |
|
OID |
1.3.6.1.4.1.25506.2.4.16 |
|
Trap name |
nasAlarmSnapshotRollbackCommandFailed |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to restore the snapshot because the system cannot determine whether the current node is the primary PEON node or not |
|
Text |
Failed to restore snapshot $1, because the system cannot determine whether the current node is the primary PEON node or not. $1: appSnapShotName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when the system cannot determine whether the current node is the primary PEON node.
In this situation, snapshot restoration will fail.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.12(appSnapShotName) |
OCTET STRING |
$1: Snapshot name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Restart the PEON process on each NAS node.
2. Restart the snapshot restoration task.
3. Manually acknowledge the alarm.
4. If the alarm persists, contact Technical Support.
0x01040395
Basic information
|
Item |
Description |
|
Type ID |
0x01040395 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to obtain the current rollback content, the snapshot rollback operation failed |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when the system failed to obtain the current rollback content.
In this situation, snapshot restoration will fail.
Objects
N/A
Recommended action
1. Check whether the snapshot contains file data.
2. Manually acknowledge the alarm.
3. If the alarm persists, contact Technical Support.
0x01040396
Basic information
|
Item |
Description |
|
Type ID |
0x01040396 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
A directory/file with the same name exists in the directory for the rollback file/directory, the snapshot rollback operation failed |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when a directory/file with the same name exists in the directory for the rollback file/directory.
In this situation, snapshot restoration will fail.
Objects
N/A
Recommended action
1. Check whether a directory/file with the same name exists in the directory for the rollback file/directory.
If yes, have a backup for the directory/file, delete the directory/file, and then roll back the snapshot again.
2. Manually acknowledge the alarm.
3. If the alarm persists, contact Technical Support.
0x01040397
Basic information
|
Item |
Description |
|
Type ID |
0x01040397 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The current state of file system is Read-only, the snapshot rollback operation failed |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when the file system is read-only.
In this situation, snapshot restoration will fail.
Objects
N/A
Recommended action
1. Roll back the snapshot after the system state restores to normal.
2. Manually acknowledge the alarm.
3. If the alarm persists, contact Technical Support.
0x01040398
Basic information
|
Item |
Description |
|
Type ID |
0x01040398 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Rollback content or params exception, the snapshot rollback operation failed |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when the rollback content has an error or the rollback parameters are incorrect.
In this situation, snapshot restoration will fail.
Objects
N/A
Recommended action
1. Verify that the rollback content and the rollback parameters are correct.
2. Manually acknowledge the alarm.
3. If the alarm persists, contact Technical Support.
Quota management in file storage
This section contains notifications about the quota management module in file storage.
0x02042581
Basic information
|
Item |
Description |
|
Type ID |
0x02042581 |
|
OID |
1.3.6.1.4.1.25506.2.1.19 |
|
Trap name |
sysAlarmQuotaReachWarning |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Quota limit has been reached |
|
Text |
Quota limit has been reached |
|
Source |
CLUSTER |
|
Severity |
Minor |
|
Default status |
ON |
Description
Quotas cannot be created or used. Data writes are not impacted.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.5.1.10(fsAlarmContentEN) |
OCTET STRING |
English alarm description. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Change the hard threshold and alarm threshold as appropriate.
0x01050201
Basic information
|
Item |
Description |
|
Type ID |
0x01050201 |
|
OID |
1.3.6.1.4.1.25506.2.4.1 |
|
Trap name |
nasAlarmQuotaReferenceLimited |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Reference quota was not created |
|
Text |
Reference quota was not created |
|
Source |
NAS SERVER |
|
Severity |
Minor |
|
Default status |
ON |
Description
The number of common quotas has reached the limit.
In this situation, the system is unable to create new reference quotas automatically.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.5.1.10(fsAlarmContentEN) |
OCTET STRING |
English alarm description. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
A maximum of 8192 common quotas can be created. Delete useless common quotas.
0x01050202
Basic information
|
Item |
Description |
|
Type ID |
0x01050202 |
|
OID |
1.3.6.1.4.1.25506.2.4.18 |
|
Trap name |
nasAlarmQuotaFileReachWarning |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Quota file number limit has been reached |
|
Text |
$1: Quota: (Directory: {}, Quota Type: {}, User (Group): {}, Limit Type: {}), reached the alarm threshold |
|
Source |
CLUSTER |
|
Severity |
Minor |
|
Default status |
ON |
Description
The number of files in the directory has reached the alarm threshold.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.5.1.10(fsAlarmContentEN) |
OCTET STRING |
English alarm description. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Change the quota limit and the alarm threshold as appropriate.
0x01050203
Basic information
|
Item |
Description |
|
Type ID |
0x01050203 |
|
OID |
1.3.6.1.4.1.25506.2.4.19 |
|
Trap name |
nasAlarmQuotaSpaceReachWarning |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Quota space limit has been reached |
|
Text |
The used capacity of the directory has reached the alarm threshold. |
|
Source |
CLUSTER |
|
Severity |
Minor |
|
Default status |
ON |
Description
The used capacity of the directory has reached the alarm threshold.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.5.1.10(fsAlarmContentEN) |
OCTET STRING |
English alarm description. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Change the quota limit and the alarm threshold as appropriate.
Recycle bins in file storage
This section contains notifications about the recycle bin modules.
0x01041001
Basic information
|
Item |
Description |
|
Type ID |
0x01041001 |
|
OID |
1.3.6.1.4.1.25506.2.4.2 |
|
Trap name |
nasAlarmTrashDeleteCephfsError |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to delete file under the trash, error occur in filesystem |
|
Text |
Failed to delete file under the trash, error occur in filesystem |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
A file system error occurs while you are deleting files in the recycle bin. This failure results in an increase in irrelevant files in the recycle bin.
In this situation, file restoration or movement in the recycle bin might be impacted.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.5.1.10(fsAlarmContentEN) |
OCTET STRING |
English alarm description. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Try the deletion again later.
2. If the alarm persists, contact Technical Support.
0x01041002
Basic information
|
Item |
Description |
|
Type ID |
0x01041002 |
|
OID |
1.3.6.1.4.1.25506.2.4.3 |
|
Trap name |
nasAlarmTrashDeleteExceptError |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to delete file under the trash, caught exception |
|
Text |
Failed to delete file under the trash because of an exception |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
Failed to delete files in the recycle bin.
A non-file system error occurs while you are deleting files in the recycle bin. This failure results in an increase in irrelevant files in the recycle bin.
In this situation, file restoration or movement in the recycle bin might be impacted.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.5.1.10(fsAlarmContentEN) |
OCTET STRING |
English alarm description. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Try the deletion again later.
2. If the alarm persists, contact Technical Support.
0x01041003
Basic information
|
Item |
Description |
|
Type ID |
0x01041003 |
|
OID |
1.3.6.1.4.1.25506.2.4.4 |
|
Trap name |
nasAlarmTrashRestoreSameName |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to restore or move file under the trash, file with same name exists |
|
Text |
Failed to restore or move file under the trash, because a file with the same name exists |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This failure might occur when the target path already has a file with the same name.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.5.1.10(fsAlarmContentEN) |
OCTET STRING |
English alarm description. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Perform either of the following tasks:
¡ Restore or move the file after deleting the file with the same name in the target path.
¡ Restore or move the file by not overwriting the existing files.
2. If the alarm persists, contact Technical Support.
0x01041004
Basic information
|
Item |
Description |
|
Type ID |
0x01041004 |
|
OID |
1.3.6.1.4.1.25506.2.4.5 |
|
Trap name |
nasAlarmTrashRestoreNotEmpty |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to restore or move directory under the trash, directory is not empty |
|
Text |
Failed to restore or move directory under the trash, because the directory is not empty |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This failure might occur when you restore or move a file to a directory that is not empty.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.5.1.10(fsAlarmContentEN) |
OCTET STRING |
English alarm description. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Perform either of the following tasks:
¡ Restore or move files after clearing the directory.
¡ Restore or move files by not overwriting the existing directories.
2. If the alarm persists, contact Technical Support.
0x01041005
Basic information
|
Item |
Description |
|
Type ID |
0x01041005 |
|
OID |
1.3.6.1.4.1.25506.2.4.6 |
|
Trap name |
nasAlarmTrashRestoreNotDir |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to restore or move file under the trash directory, path is not directory |
|
Type ID |
Failed to restore or move file under the trash directory, because the path is not directory. |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm might occur when you restore or move files in the recycle bin to the specified path that is not a directory.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.5.1.10(fsAlarmContentCN) |
OCTET STRING |
English alarm description. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Make sure the path for restoring or moving files is a directory
2. If the alarm persists, contact Technical Support.
0x01041006
Basic information
|
Item |
Description |
|
Type ID |
0x01041006 |
|
OID |
1.3.6.1.4.1.25506.2.4.7 |
|
Trap name |
nasAlarmTrashRestoreCephfsError |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to restore or move file under the trash directory, error occur in filesystem |
|
Text |
Failed to restore or move file under the trash directory because of a file system exception |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
A file system error occurs while you are restoring or moving files in the recycle bin.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.5.1.10(fsAlarmContentEN) |
OCTET STRING |
English alarm description. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content |
Recommended action
1. Try the operation again later.
2. If the alarm persists, contact Technical Support.
0x01041007
Basic information
|
Item |
Description |
|
Type ID |
0x01041007 |
|
OID |
1.3.6.1.4.1.25506.2.4.8 |
|
Trap name |
nasAlarmTrashRestoreExceptError |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to restore or move file under the trash directory, caught exception |
|
Text |
Failed to restore or move file under the trash directory because of an exception |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
A non-file system error occurs while you are restoring or moving files in the recycle bin.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.5.1.10(fsAlarmContentEN) |
OCTET STRING |
English alarm description. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Try the operation again later.
2. If the alarm persists, contact Technical Support.
0x01041008
Basic information
|
Item |
Description |
|
Type ID |
0x01041008 |
|
OID |
1.3.6.1.4.1.25506.2.4.10 |
|
Trap name |
nasAlarmTrashRestoreQuotaExceedError |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to restore or move file under the trash directory, the dest directory has no sufficient capacity |
|
Text |
Failed to restore or move directory or file:$1. The destination directory does not have sufficient space. $1: nodeName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm might occur when you restore or move files in the recycle bin to the destination directory that does not have sufficient capacity.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Try the operation again later.
2. If the alarm persists, contact Technical Support.
0x01041009
Basic information
|
Item |
Description |
|
Type ID |
0x01041009 |
|
OID |
1.3.6.1.4.1.25506.2.4.11 |
|
Trap name |
nasAlarmTrashRestoreOperatorProhibited |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to restore or move file under the trash directory, the operation to destination directory not permitted |
|
Text |
Failed to restore or move directory or file: $1. The destination directory has been configured with features incompatible with the recycle bin feature. $1: nodeName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm might occur when you restore or move files in the recycle bin to the destination directory that does not have sufficient capacity.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Try the operation again later.
2. If the alarm persists, contact Technical Support.
0x01041010
Basic information
|
Item |
Description |
|
Type ID |
0x01041010 |
|
OID |
1.3.6.1.4.1.25506.2.4.12 |
|
Trap name |
nasAlarmTrashRestorePermissionDenied |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to restore or move file under the trash directory, don't have permission of the destination directory |
|
Text |
Failed to restore or move directory:$1. The destination directory has been configured with features incompatible with the recycle bin feature. $1: nodeName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm might occur when you restore or move files in the recycle bin to the destination directory that has been configured with features incompatible with the recycle bin feature.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Try the operation again later.
2. If the alarm persists, contact Technical Support.
0x01041011
Basic information
|
Item |
Description |
|
Type ID |
0x01041011 |
|
OID |
1.3.6.1.4.1.25506.2.4.14 |
|
Trap name |
nasAlarmEventTrashDeleteResidual |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Residual information exists while deleting the trash bin of directory |
|
Text |
A directory on $1 has residual information in the directory recycle bin. The directory might not be deleted correctly. $1: nodeName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
If this alarm occurs, the directory deletion fails.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check whether the cluster is healthy, and delete the directory on the management page of the cluster.
2. If you cannot delete the directory on the management page of the cluster, contact Technical Support.
3. To delete the directory on the NAS node, do the following:
a. Access the CLI of the node and then enter the view of the directory.
b. Use the mkdir .NAS_Storage_Trash command, and then use the rm -rf .NAS_Storage_Trash command to delete the directory.
4. Manually acknowledge the alarm.
Volume mapping in block storage
This section contains volume mapping notifications in block storage.
0x01010171
Basic information
|
Item |
Description |
|
Type ID |
0x01010171 |
|
OID |
1.3.6.1.4.1.25506.2.3.11 |
|
Trap name |
blockAlarmTgtConfigRbFail |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Block storage TGT configuration rollback |
|
Text |
Failed to restore TGT configuration on node $1. $1: appTgtNodeOID |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
This failure might occur if a network or process error recurs while you are rolling back volume mappings after a network or process error occurred during previous volume mapping operations.
This failure will cause inconsistency between nodes in volume mapping configuration.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.11(appTgtNodeOID) |
OCTET STRING |
$1: Node OID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Review the TGT log to troubleshoot the issue, and then manually reboot the tgt process to restore the configuration.
0x01010170
Basic information
|
Item |
Description |
|
Type ID |
0x01010170 |
|
OID |
1.3.6.1.4.1.25506.2.3.10 |
|
Trap name |
blockAlarmTgtConfigFail |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Volume mapping configuration inconsistency |
|
Text |
The following nodes are inconsistent in volume mapping configuration:$1. $1: appTgtNodeOID |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
This issue might occur if network or process error occurs during the mapping operation.
This issue causes inconsistency between nodes in volume mapping configuration.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.11(appTgtNodeOID) |
OCTET STRING |
$1: Node OID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Execute the service tgt forcedrestart command on the faulty node to remove this issue.
0x02010172
Basic information
|
Item |
Description |
|
Type ID |
0x02010172 |
|
OID |
1.3.6.1.4.1.25506.2.3.30 |
|
Trap name |
blockAlarmIscsiVridConflict |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
VRID conflict of iSCSI high availability IP |
|
Text |
VRID conflict, iSCSI high availability IP:$1 cannot use, please modify VRID parameters of iSCSI high availability IP. $1: appIscsiIP |
|
Source |
DEVICE |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs if the network has multiple devices that use the same VRID and comply with the VRRP protocol.
In this situation, the impacted iSCSI high availability IP is not available.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.16 (appIscsiIP) |
OCTET STRING |
$1: iSCSI HA VIP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Edit the VRID for iSCSI high availability from the storage management interface.
Volume copy in block storage
This section contains notifications about the volume copy module in block storage.
0x01040160
Basic information
|
Item |
Description |
|
Type ID |
0x01040160 |
|
OID |
1.3.6.1.4.1.25506.2.3.1 |
|
Trap name |
blockAlarmCopyRepioFail |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Background copy failed |
|
Text |
Background copy operation failed to volume copy pair $1. $1: appCopyID |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
A volume copy task failed in the back-end.
This failure might occur when volume I/O fails because of a storage pool error.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.9(appCopyID) |
OCTET STRING |
$1: Volume copy pair ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Verify that the storage pool is in normal state.
2. Verify that the network connectivity is available. Manually recover the network connectivity if network connectivity is unavailable.
Volume migration in block storage
This section contains notifications about volume migration in block storage.
0x01040161
Basic information
|
Item |
Description |
|
Type ID |
0x01040161 |
|
OID |
1.3.6.1.4.1.25506.2.3.2 |
|
Trap name |
blockAlarmMigrationRepioFail |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Background migration failed |
|
Text |
Background volume migration failed, ID: $1. $1: appMigrationID |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
Volume migration failed in the back-end.
This failure might occur if volume I/O error occurs during volume migration.
Objects
|
OID (object name) |
Metric |
Description |
|
1.3.6.1.4.1.25506.1.6.1.10(appMigrationID) |
OCTET STRING |
$1: Migration ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Verify that the storage pool is in normal state.
2. Verify that the network connectivity is available. Manually recover the network connectivity if network connectivity is unavailable.
Volume snapshot in block storage
This section contains notifications about the volume snapshot module in block storage.
0x01040150
Basic information
|
Item |
Description |
|
Type ID |
0x01040150 |
|
OID |
1.3.6.1.4.1.25506.2.3.12 |
|
Trap name |
blockAlarmSnapRollbackFail |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Snapshot rollback failed |
|
Text |
Restoring snapshot $1 failed. $1: appSnapShotName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This failure might occur if cluster error (for example, a Ceph restart) occurred during snapshot restoration.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.12(appSnapShotName) |
OCTET STRING |
$1: Snapshot name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Review the VAE log for issues about block storage services.
2. If the alarm persists, contact Technical Support.
0x01040153
Basic information
|
Item |
Description |
|
Type ID |
0x01040153 |
|
OID |
1.3.6.1.4.1.25506.2.3.15 |
|
Trap name |
blockAlarmCSnapRollBackFail |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Consistency group snapshot rollback failed. |
|
Text |
Restoring consistency group snapshot $1 failed $1: appCSnapShotName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
Restoring a consistency group snapshot failed.
This failure might occur if Ceph error occurred during snapshot restoration.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.15(appCSnapShotName) |
OCTET STRING |
$1: Consistency snapshot name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Review the VAE log for issues about block storage services.
2. If the alarm persists, contact Technical Support.
0x01040151
Basic information
|
Item |
Description |
|
Type ID |
0x01040151 |
|
OID |
1.3.6.1.4.1.25506.2.3.13 |
|
Trap name |
blockAlarmCreateTimerSnapFail |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to create scheduled snapshots. |
|
Text |
Failed to take an automatic snapshot of volume $1 $1: appVolumeName |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
Creating an auto-snapshot schedule failed in the back-end.
This failure might occur if Ceph error occurs during the creation operation.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.14(appVolumeName) |
OCTET STRING |
$1: Volume name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Review the VAE log for issues about block storage services.
2. If the alarm persists, contact Technical Support.
0x01040152
Basic information
|
Item |
Description |
|
Type ID |
0x01040152 |
|
OID |
1.3.6.1.4.1.25506.2.3.14 |
|
Trap name |
blockAlarmDelStrategyFail |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Failed to delete the snapshot schedule |
|
Text |
Failed to delete auto-snapshot schedule $1. $1: appStrategy |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
Deleting an auto-snapshot schedule failed in the back-end.
This issue might occur if Ceph error occurs while the system is deleting snapshots for an auto-snapshot schedule.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.6.1.13(appStrategy) |
OCTET STRING |
$1: Auto-snapshot schedule ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Review the VAE log for issues about block storage services.
2. If the alarm persists, contact Technical Support.
Async remote replication in block storage
This section contains notifications about the async remote replication module in block storage.
0x01040162
Basic information
|
Item |
Description |
|
Type ID |
0x01040162 |
|
OID |
1.3.6.1.4.1.25506.2.3.23 |
|
Trap name |
blockAlarmRMARDevIdRunError |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The running status of remote device has been offline |
|
Text |
Remote device $1 has been linkdown. $1: blockAalrmLinkDeviceIdOID |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
An error occurred on the physical link.
In this situation, the services provided by the remote device will be interrupted.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.7.1.86(blockAalrmLinkDeviceIdOID) |
OCTET STRING |
$1: Remote device ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
OCTET STRING |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
Unsigned32 |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Make sure both the physical network for async remote replication and the link-related replication nodes are in good condition.
0x01040163
Basic information
|
Item |
Description |
|
Type ID |
0x01040163 |
|
OID |
1.3.6.1.4.1.25506.2.3.24 |
|
Trap name |
blockAlarmLinkDrlinkLinkoff |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Replication link disconnected |
|
Text |
The replication link between $2 and $3 for remote device $1 has been disconnected. $1: blockAalrmLinkDeviceIdOID $2: blockAlarmLinkLocalHostIpOID $3: blockAlarmLinkRemoteHostIpOID |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The physical link for async remote replication is disconnected.
In this situation, the physical link cannot be used for data replication.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.7.1.86(blockAalrmLinkDeviceIdOID) |
OCTET STRING |
$1: Remote device ID. |
|
1.3.6.1.4.1.25506.1.7.1.87(blockAlarmLinkLocalHostIpOID) |
OCTET STRING |
$2: IP address of the local replication node. |
|
1.3.6.1.4.1.25506.1.7.1.88(blockAlarmLinkRemoteHostIpOID) |
OCTET STRING |
$3: IP address of the remote replication node. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Verify that the physical link is connected.
0x01040164
Basic information
|
Item |
Description |
|
Type ID |
0x01040164 |
|
OID |
1.3.6.1.4.1.25506.2.3.25 |
|
Trap name |
blockAlarmLinkDrlinkLatency |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The latency of Replication link has been out of range |
|
Text |
The latency($4 ms) of replication link between $2 and $3 for remote device $1 was more than limitation. $1: blockAalrmLinkDeviceIdOID $2: blockAlarmLinkLocalHostIpOID $3: blockAlarmLinkRemoteHostIpOID $4: blockAlarmLinkLatency |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
High physical link delay alarm occurred.
In this situation, the async remote replication is not available.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.7.1.86(blockAalrmLinkDeviceIdOID) |
OCTET STRING |
$1: Remote device ID. |
|
1.3.6.1.4.1.25506.1.7.1.87(blockAlarmLinkLocalHostIpOID) |
OCTET STRING |
$2: IP address of the local replication node. |
|
1.3.6.1.4.1.25506.1.7.1.88(blockAlarmLinkRemoteHostIpOID) |
OCTET STRING |
$3: IP address of the remote replication node. |
|
1.3.6.1.4.1.25506.1.7.1.89(blockAlarmLinkLatency) |
OCTET STRING |
$4: Latency of the replication link. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
OCTET STRING |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
Unsigned32 |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Control the traffic of concurrent services in the network to reduce the network traffic.
0x01040165
Basic information
|
Item |
Description |
|
Type ID |
0x01040165 |
|
OID |
1.3.6.1.4.1.25506.2.3.26 |
|
Trap name |
blockAlarmLinkRedundency |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
The remote device has no redundancy replication node |
|
Text |
The remote device $1 lacks redundancy replication node. $1: blockAalrmLinkDeviceIdOID |
|
Source |
CLUSTER |
|
Severity |
Warning |
|
Default status |
ON |
Description
The address pool for remote device creation has no redundant replication nodes.
In this situation, the remote device will go offline if the only replication node fails.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.7.1.86(blockAalrmLinkDeviceIdOID) |
OCTET STRING |
$1: Remote device ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
OCTET STRING |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
Unsigned32 |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Add replications nodes to the address pool for the remote device.
0x01040167
Basic information
|
Item |
Description |
|
Type ID |
0x01040167 |
|
OID |
1.3.6.1.4.1.25506.2.3.27 |
|
Trap name |
blockAlarmRMAPairRollbackFail |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
RMA pair snap rollback failed |
|
Text |
RMA pair:$1 snap rollback failed. $1: blockAlarmRMAPairId |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The replication pair restoration failed.
This failure might occur if the network or cluster becomes abnormal.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.7.1.90(blockAlarmRMAPairId) |
OCTET STRING |
$1: Replication pair ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Make sure both the network and the cluster are in normal state.
0x01040168
Basic information
|
Item |
Description |
|
Type ID |
0x01040168 |
|
OID |
1.3.6.1.4.1.25506.2.3.28 |
|
Trap name |
blockAlarmRMAPairInvalid |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
RMA pair is invalid |
|
Text |
RMA pair:$1 is invalid. $1: blockAlarmRMAPairId |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This failure might occur if you delete the pair only from the local cluster or pair I/O fails.
In this situation, the pair becomes invalid.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.7.1.90(blockAlarmRMAPairId) |
OCTET STRING |
$1: Replication pair ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
OCTET STRING |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
Unsigned32 |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Delete the invalid pair, and then create a new pair.
0x01040169
Basic information
|
Item |
Description |
|
Type ID |
0x01040169 |
|
OID |
1.3.6.1.4.1.25506.2.3.29 |
|
Trap name |
blockAlarmRMAPairInterrupt |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
RMA pair is interrupted. |
|
Text |
RMA pair:$1 is interrupted $1: blockAlarmRMAPairId |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
The remote device went offline or the replication task failed on the backstage.
In this situation, you cannot perform a sync for the pair.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.7.1.90(blockAlarmRMAPairId) |
OCTET STRING |
$1: Replication pair ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
OCTET STRING |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
Unsigned32 |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
Recommended action
1. Verify that the remote device is in up state.
2. Verify that the cluster is in normal state.
Self-healing framework in block storage
This section contains notifications about the self-healing framework (the Themis module) in block storage.
0x01030140
Basic information
|
Item |
Description |
|
Type ID |
0x01030140 |
|
OID |
1.3.6.1.4.1.25506.2.3.3 |
|
Trap name |
blockAlarmThemisNetworkHighDelay |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
High network delay |
|
Text |
Host $1 detected having high delay on $2 network. $1: sysAlarmContentPara1 $2: sysAlarmContentPara2 |
|
Source |
NET |
|
Severity |
Major |
|
Default status |
ON |
Description
In a storage front-end and back-end separated scenario, each ping operation sends 20 ICMP echo requests to test the network delay. This alarm occurs if the number of packets with a network delay of 200 milliseconds exceeds 50%.
High network delay occurred in the storage front-end network or storage back-end network will result in a decrease in back-end I/O performance.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.31(sysAlarmContentPara1) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.32(sysAlarmContentPara2) |
OCTET STRING |
$2: Front-end NIC name or back-end NIC name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
If the NIC is not a bond NIC, check the NIC for network issues. The system will clear the alarm automatically after the issue is removed.
If the NIC is a bond NIC and is operating in active/standby mode, check the NIC or the operating link for network issues. Manually clear the alarm on the management page after confirming no issue exists in the network or the issue is removed.
0x01030141
Basic information
|
Item |
Description |
|
Type ID |
0x01030141 |
|
OID |
1.3.6.1.4.1.25506.2.3.4 |
|
Trap name |
blockAlarmThemisNetworkDisconnect |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Network disconnected |
|
Text |
Host $1 detected having lost connectivity to the $2 network. $1: sysAlarmContentPara1 $2: sysAlarmContentPara2 |
|
Source |
NET |
|
Severity |
Major |
|
Default status |
ON |
Description
Network connectivity has been lost.
In a storage front-end and back-end separated scenario, each ping operation sends 20 ICMP echo requests to determine the reachability of an IP address. This alarm occurs if these ICMP echo requests all time out.
Loss of network connectivity causes cluster error and might incur placement group (PG) degradation.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.31(sysAlarmContentPara1) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.32(sysAlarmContentPara2) |
OCTET STRING |
$2: Front-end NIC name or back-end NIC name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
If the NIC is not a bond NIC, check the NIC for network issues. The system will clear the alarm automatically after the issue is removed.
If the NIC is a bond NIC and is operating in active/standby mode, check the NIC or the operating link for network issues.
0x01030142
Basic information
|
Item |
Description |
|
Type ID |
0x01030142 |
|
OID |
1.3.6.1.4.1.25506.2.3.5 |
|
Trap name |
blockAlarmThemisNetworkPoorConnect |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Poor network performance |
|
Text |
Host $1 detected having poor connectivity to the $2 network. $1: sysAlarmContentPara1 $2: sysAlarmContentPara2 |
|
Source |
NET |
|
Severity |
Major |
|
Default status |
ON |
Description
In a storage front-end and back-end separated scenario, each ping operation sends 20 ICMP echo requests to determine the reachability of an IP address. This alarm occurs if the number of network connectivity failures reaches 33%. The short-term alarm might be caused by NIC failure and the long-term alarm might be caused by heavy work load in the network.
Loss of network connectivity to the storage front-end network or storage back-end network causes cluster error and might incur PG degradation.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.31(sysAlarmContentPara1) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.32(sysAlarmContentPara2) |
OCTET STRING |
$2: Front-end NIC name or back-end NIC name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
If the NIC is not a bond NIC, check the NIC for network issues. The system will clear the alarm automatically after the issue is removed.
If the NIC is a bond NIC and is operating in active/standby mode, check the NIC or the operating link for network issues.
0x01030143
Basic information
|
Item |
Description |
|
Type ID |
0x01030143 |
|
OID |
1.3.6.1.4.1.25506.2.3.6 |
|
Trap name |
blockAlarmThemisNetworkFlash |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Network flapping |
|
Text |
Host $1 detected having flapping connectivity to the $2 network. $1: sysAlarmContentPara1 $2: sysAlarmContentPara2 |
|
Source |
NET |
|
Severity |
Major |
|
Default status |
ON |
Description
Network flapping occurred during the detection interval.
Loss of network connectivity to the storage front-end network or storage back-end network causes cluster error and might incur PG degradation.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.31(sysAlarmContentPara1) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.32(sysAlarmContentPara2) |
OCTET STRING |
$2: Front-end NIC name or back-end NIC name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check the NIC of the unreachable node or check the network to identify the cause.
2. Replace the NIC or remove the network issues as appropriate.
0x01030144
Basic information
|
Item |
Description |
|
Type ID |
0x01030144 |
|
OID |
1.3.6.1.4.1.25506.2.3.7 |
|
Trap name |
blockAlarmThemisNetworkHighErr |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
NIC error packets |
|
Text |
Host $1 detected having a large number of error packets on the $2 network $: sysAlarmContentPara1 $2: sysAlarmContentPara2 |
|
Source |
NET |
|
Severity |
Major |
|
Default status |
ON |
Description
A minimum of one NIC has received too many erroneous packets.
This alarm occurs if a minimum of 5% of packets received by any NICs from the public or a cluster network are erroneous.
Too many erroneous packets will result in a decrease in back-end I/O performance.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.31(sysAlarmContentPara1) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.32(sysAlarmContentPara2) |
OCTET STRING |
$2: Front-end NIC name or back-end NIC name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
If the NIC is not a bond NIC, check the NIC for network issues. The system will clear the alarm automatically after the issue is removed.
If the NIC is a bond NIC and is operating in active/standby mode, check the NIC or the operating link for network issues.
0x01030145
Basic information
|
Item |
Description |
|
Type ID |
0x01030145 |
|
OID |
1.3.6.1.4.1.25506.2.3.8 |
|
Trap name |
blockAlarmThemisNetworkHighDrop |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
NIC packet drops |
|
Text |
Host $1 detected having a large number of packet drops on the $2 network. $1: sysAlarmContentPara1 $2: sysAlarmContentPara2 |
|
Source |
NET |
|
Severity |
Major |
|
Default status |
ON |
Description
If a NIC in the storage front-end network or storage back-end network fails to receive a minimum of 5% packets during a detection interval, this alarm occurs.
Too many lost packets will result in a decrease in back-end I/O performance.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.31(sysAlarmContentPara1) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.32(sysAlarmContentPara2) |
OCTET STRING |
$2: Front-end NIC name or back-end NIC name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
If the NIC is not a bond NIC, check the NIC for network issues. The system will clear the alarm automatically after the issue is removed.
If the NIC is a bond NIC and is operating in active/standby mode, check the NIC or the operating link for network issues.
0x01030146
Basic information
|
Item |
Description |
|
Type ID |
0x01030146 |
|
OID |
1.3.6.1.4.1.25506.2.3.9 |
|
Trap name |
blockAlarmThemisNetworkHighOthersDown |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Peer host offline |
|
Type ID |
Host $1 was offline. $1: sysAlarmContentPara1 |
|
Source |
NET |
|
Severity |
Major |
|
Default status |
ON |
Description
A node has been down.
This alarm occurs when a node cannot be reached on the storage front-end network or storage back-end network.
Loss of network connectivity to the storage front-end network or storage back-end network causes cluster error and might incur PG degradation.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.31(sysAlarmContentPara1) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
1. Check the network connection of the peer node for connectivity issues.
2. Make sure the peer node is in up state
Object storage
This section contains object storage notifications.
0x02047061
Basic information
|
Item |
Description |
|
Type ID |
0x02047061 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
N/A |
|
Metric |
rgw_bucket_objnum_exceed_threshold1 |
|
Text |
The number of objects in bucket {$1} has exceeded 85% of the upper limit. $1: Bucket name |
|
Source |
CLUSTER |
|
Severity |
Minor |
|
Default status |
ON |
Description
This alarm occurs when the number of objects in a bucket has exceeded 85 million.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Use another bucket for object data storage.
0x02047062
Basic information
|
Item |
Description |
|
Type ID |
0x02047062 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
N/A |
|
Metric |
rgw_bucket_objnum_exceed_threshold2 |
|
Text |
The number of objects in bucket {$1} has exceeded the upper limit. Object upload might fail. $1: Bucket name |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when the number of objects in a bucket has exceeded the limit. In this situation, object upload might fail.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.1.1.2(fsid) |
OCTET STRING |
Cluster ID. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Do not write new object data to the bucket and use another bucket for object data storage.
0x02047063
Basic information
|
Item |
Description |
|
Type ID |
0x02047063 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
N/A |
|
Metric |
AS_cache_capacity_insufficient |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when the cache capacity usage of archive storage has reached 85%.
In this situation, data writing during archive storage is not affected.
Objects
N/A
Recommended action
Delete the cached files that do not need archiving.
If the cache capacity for archive storage cannot meet the service requirement, increase the cache capacity.
0x02047064
Basic information
|
Item |
Description |
|
Type ID |
0x02047064 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
N/A |
|
Metric |
AS_cache_about_exhaust |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Critical |
|
Default status |
ON |
Description
This alarm occurs when the cache capacity usage of archive storage has reached 95%.
In this situation, data writing during archive storage is not affected.
Objects
N/A
Recommended action
Delete the cached files that do not need archiving.
If the cache capacity for archive storage cannot meet the service requirement, increase the cache capacity.
0x02047065
Basic information
|
Item |
Description |
|
Type ID |
0x02047065 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
N/A |
|
Metric |
AS_total_capacity_insufficient |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Major |
|
Default status |
ON |
Description
This alarm occurs when the capacity usage of archive storage has reached 85%.
In this situation, data writing during archive storage is not affected.
Objects
N/A
Recommended action
Delete the files that do not need archiving.
0x02047066
Basic information
|
Item |
Description |
|
Type ID |
0x02047066 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
N/A |
|
Metric |
AS_total_space_about_exhaust |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Critical |
|
Default status |
ON |
Description
This alarm occurs when the capacity usage of archive storage has reached 95%.
In this situation, data writing during archive storage is not affected.
Objects
N/A
Recommended action
If the storage capacity for archive storage cannot meet the service requirement, increase the cache capacity.
0x02047067
Basic information
|
Item |
Description |
|
Type ID |
0x02047067 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
N/A |
|
Metric |
RGW read latency |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Critical |
|
Default status |
ON |
Description
This alarm occurs when the read latency of the object gateway has reached or exceeded the alarm threshold.
Objects
N/A
Recommended action
Check whether the object gateway operates correctly.
0x02047068
Basic information
|
Item |
Description |
|
Type ID |
0x02047068 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
N/A |
|
Metric |
RGW write latency |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Critical |
|
Default status |
ON |
Description
This alarm occurs when the write latency of the object gateway has reached or exceeded the alarm threshold.
Objects
N/A
Recommended action
Check whether the object gateway operates correctly.
0x02047070
Basic information
|
Item |
Description |
|
Type ID |
0x02047070 |
|
OID |
N/A |
|
Trap name |
N/A |
|
MIB file |
N/A |
|
Metric |
Abnormal object gateways in site |
|
Text |
N/A |
|
Source |
CLUSTER |
|
Severity |
Critical |
|
Default status |
ON |
Description
This alarm occurs when more than 50% of the object gateways that participate in multisite sync in a site are not accessible.
In this situation, users cannot access object storage resources normally.
Objects
N/A
Recommended action
Check whether the object gateways in the site operate correctly.
0x01030100
Basic information
|
Item |
Description |
|
Type ID |
0x01030100 |
|
OID |
1.3.6.1.4.1.25506.2.2.101 |
|
Trap name |
nodeAlarmNetworkDelay |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Network flapping |
|
Text |
$7 The network condition on node $1 $2 is suboptimal. The lantency of NIC $3 is $4. The NIC port is isolated. $1: nodeName $2: nodeNetCardIP $3: nodeNetCardName $4: nodeNetCardTimeDelay $7: sysAlarmTime |
|
Source |
NET |
|
Severity |
Major |
|
Default status |
ON |
Description
The cluster has detected that the BM network is suboptimal. The network might have latency.
In this situation, the node might have a network connectivity issue.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.38 (nodeNetCardIP) |
OCTET STRING |
$2: NIC IP. |
|
1.3.6.1.4.1.25506.1.2.1.39(nodeNetCardName) |
OCTET STRING |
$3: NIC name. |
|
1.3.6.1.4.1.25506.1.2.1.40(nodeNetCardTimeDelay) |
OCTET STRING |
$4: Latency on the NIC. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
$7: Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check the network for faults, and then recover the network.
0x01030101
Basic information
|
Item |
Description |
|
Type ID |
0x01030101 |
|
OID |
1.3.6.1.4.1.25506.2.2.102 |
|
Trap name |
nodeAlarmNetworkLoss |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
NIC packet drops |
|
Text |
$7 The network condition on node $1 $2 is suboptimal. The packet loss rate of NIC $3 is $4. The NIC port is isolated. $1: nodeName $2: nodeNetCardIP $3: nodeNetCardName $4: nodeNetCardLossRate $7: sysAlarmTime |
|
Source |
NET |
|
Severity |
Major |
|
Default status |
ON |
Description
The network condition on the BM NIC is suboptimal. The NIC might have packet loss.
In this situation, the node might have a network connectivity issue.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.38 (nodeNetCardIP) |
OCTET STRING |
$2: NIC IP. |
|
1.3.6.1.4.1.25506.1.2.1.39(nodeNetCardName) |
OCTET STRING |
$3: NIC name. |
|
1.3.6.1.4.1.25506.1.2.1.41(nodeNetCardLossRate) |
OCTET STRING |
$4: Packet loss rate of the NIC. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
$7: Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check the network for faults, and then recover the network.
0x01030102
Basic information
|
Item |
Description |
|
Type ID |
0x01030102 |
|
OID |
1.3.6.1.4.1.25506.2.2.103 |
|
Trap name |
nodeAlarmNetworkLossAndDelay |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Network disconnected |
|
Text |
$8 The network condition on node $1 $2 is suboptimal. On NIC $3, the packet loss rate is $4 and the lantency is $5. The NIC port is isolated. $1: nodeName $2: nodeNetCardIP $3: nodeNetCardName $4: nodeNetCardLossRate $5: nodeNetCardTimeDelay $7: sysAlarmTime |
|
Source |
NET |
|
Severity |
Major |
|
Default status |
ON |
Description
The network condition on the BM NIC is suboptimal. The NIC might have packet loss and latency.
In this situation, the node might have a network connectivity issue.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.38 (nodeNetCardIP) |
OCTET STRING |
$2: NIC IP. |
|
1.3.6.1.4.1.25506.1.2.1.39(nodeNetCardName) |
OCTET STRING |
$3: NIC name. |
|
1.3.6.1.4.1.25506.1.2.1.41(nodeNetCardLossRate) |
OCTET STRING |
$4: Packet loss rate on the NIC. |
|
1.3.6.1.4.1.25506.1.2.1.40(nodeNetCardTimeDelay) |
OCTET STRING |
$5: Latency on the NIC. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
$8: Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check the network for faults, and then recover the network.
0x01030103
Basic information
|
Item |
Description |
|
Type ID |
0x01030103 |
|
OID |
1.3.6.1.4.1.25506.2.2.104 |
|
Trap name |
nodeAlarmSeparate |
|
MIB file |
H3C-Unistor-MIB-en.mib |
|
Metric |
Poor network performance |
|
Text |
A network disconnection occurred on node $1 $2. $1: nodeName $2: nodeNetCardIP |
|
Source |
NET |
|
Severity |
Major |
|
Default status |
ON |
Description
The network condition on the BM NIC is suboptimal. The NIC might have a poor network connection.
In this situation, the node might have a network connectivity issue.
Objects
|
OID (object name) |
Syntax |
Description |
|
1.3.6.1.4.1.25506.1.2.1.2(nodeName) |
OCTET STRING |
$1: Host name. |
|
1.3.6.1.4.1.25506.1.2.1.38 (nodeNetCardIP) |
OCTET STRING |
$2: NIC IP. |
|
1.3.6.1.4.1.25506.1.1.1.16(sysAlarmRank) |
Unsigned32 |
Alarm severity: · 1—Critical. · 2—Major. · 3—Minor. · 4—Warning. |
|
1.3.6.1.4.1.25506.1.1.1.25(sysAlarmStatus) |
OCTET STRING |
Alarm status: · real-time—The alarm is still present. · auto-recovery—The alarm has been cleared. |
|
1.3.6.1.4.1.25506.1.1.1.30(sysAlarmTime) |
OCTET STRING |
Date and time when the alarm occurred. |
|
1.3.6.1.4.1.25506.1.1.1.35(sysAlarmKey) |
OCTET STRING |
Alarm content. |
Recommended action
Check the network for faults, and then recover the network.
.
Appendix A Summary of SNMP notifications
|
OID |
Trap name |
Type ID |
Metric |
|
1.3.6.1.4.1.25506.2.1.2 |
sysAlarmPoolStatus |
0x02042101 |
Storage pool error |
|
1.3.6.1.4.1.25506.2.1.3 |
sysAlarmPoolDegrade |
0x02042102 |
Degrade storage pool |
|
1.3.6.1.4.1.25506.2.1.5 |
sysAlarmCpuUtilization |
0x02040102 |
Cluster CPU Usage |
|
1.3.6.1.4.1.25506.2.1.6 |
sysAlarmMemoryUtilization |
0x02040202 |
Cluster Memory Usage |
|
1.3.6.1.4.1.25506.2.1.8 |
sysAlarmMonitorStatus |
0x01042015 |
Cluster MON_DOWN |
|
1.3.6.1.4.1.25506.2.1.12 |
sysAlarmClusterSystemWarnHealth |
0x02042001 |
Cluster health warning |
|
1.3.6.1.4.1.25506.2.1.13 |
sysAlarmClusterSystemErrorHealth |
0x02042002 |
Cluster health error |
|
1.3.6.1.4.1.25506.2.1.14 |
clusterSqlSynchronize |
0x01042304 |
Database synchronization exception |
|
1.3.6.1.4.1.25506.2.1.15 |
clusterZKNum |
0x01042301 |
Inappropriate number of zookeeper nodes |
|
1.3.6.1.4.1.25506.2.1.16 |
clusterZKHealth |
0x01042302 |
Cluster management configuration service exception |
|
1.3.6.1.4.1.25506.2.1.17 |
ifDownWhenOperate |
0x01042303 |
Network failure during host operations |
|
1.3.6.1.4.1.25506.2.1.19 |
sysAlarmQuotaReachWarning |
0x02042581 |
Quota limit has been reached |
|
1.3.6.1.4.1.25506.2.1.20 |
sysAlarmCapabilityUtilizationL1 |
0x02040303 |
Cluster Storage Capacity Usage Level 1 |
|
1.3.6.1.4.1.25506.2.1.21 |
0x02040304 |
Cluster Storage Capacity Usage Level 2 |
|
|
1.3.6.1.4.1.25506.2.1.22 |
sysAlarmCapabilityUtilizationL3 |
0x02040305 |
Cluster Storage Capacity Usage Level 3 |
|
1.3.6.1.4.1.25506.2.1.23 |
sysAlarmLicsServerErr |
0x02030401 |
License server sync fail |
|
1.3.6.1.4.1.25506.2.1.24 |
sysAlarmNtpExtAutoDisabled |
0x01020303 |
Cluster changed to inner NTP synchronizing node mode automatically |
|
1.3.6.1.4.1.25506.2.1.26 |
sysAlarmPatchStatus |
0x02040129 |
Patch_warn |
|
1.3.6.1.4.1.25506.2.1.31 |
sysAlarmSendMailFailed |
0x02020604 |
Email sending failure |
|
1.3.6.1.4.1.25506.2.2.7 |
nodeAlarmCpuUtilization |
0x02010102 |
Node CPU Usage |
|
1.3.6.1.4.1.25506.2.2.8 |
nodeAlarmMemoryUtilization |
0x02010202 |
Node Memory Usage |
|
1.3.6.1.4.1.25506.2.2.16 |
nodeAlarmRaidControler |
0x01010601 |
A RAID controller become abnormal |
|
1.3.6.1.4.1.25506.2.2.24 |
nodeAlarmCpuStat |
0x01010101 |
A CPU module became abnormal |
|
1.3.6.1.4.1.25506.2.2.25 |
nodeAlarmMemStat |
0x01010201 |
A Memory module became abnormal |
|
1.3.6.1.4.1.25506.2.2.26 |
nodeAlarmFanStat |
0x01010301 |
A Fan module became abnormal |
|
1.3.6.1.4.1.25506.2.2.27 |
nodeAlarmPwrStat |
0x01010401 |
A power module became abnormal |
|
1.3.6.1.4.1.25506.2.2.28 |
nodeAlarmEthStat |
0x01010501 |
A NIC became abnormal |
|
1.3.6.1.4.1.25506.2.2.29 |
nodeAlarmEthPlug |
0x01010502 |
A NIC was removed |
|
1.3.6.1.4.1.25506.2.2.30 |
nodeAlarmIbStat |
0x01010503 |
An RDMA NIC became abnormal |
|
1.3.6.1.4.1.25506.2.2.31 |
nodeAlarmPdPlug |
0x01010701 |
A disk was removed |
|
1.3.6.1.4.1.25506.2.2.32 |
nodeAlarmPdLine |
0x01010703 |
A disk went offline |
|
1.3.6.1.4.1.25506.2.2.33 |
nodeAlarmPdTemp |
0x01010705 |
The temperature of a disk is too high |
|
1.3.6.1.4.1.25506.2.2.34 |
nodeAlarmDiskState |
0x01013232 |
Host failure |
|
1.3.6.1.4.1.25506.2.2.35 |
nodeAlarmDiskUtilizationL1 |
0x02010303 |
Node Disk Usage Level 1 |
|
1.3.6.1.4.1.25506.2.2.36 |
nodeAlarmDiskUtilizationL2 |
0x02010304 |
Node Disk Usage Level 2 |
|
1.3.6.1.4.1.25506.2.2.37 |
nodeAlarmDiskUtilizationL3 |
0x02010305 |
Node Disk Usage Level 3 |
|
1.3.6.1.4.1.25506.2.2.38 |
nodeAlarmSmbdStat |
0x02055001 |
CIFS service error |
|
1.3.6.1.4.1.25506.2.2.39 |
nodeAlarmWinbindStat |
0x02054901 |
User mapping service error |
|
1.3.6.1.4.1.25506.2.2.40 |
nodeAlarmNmbdStat |
0x02055101 |
Name service error |
|
1.3.6.1.4.1.25506.2.2.41 |
nodeAlarmAdsStat |
0x02054863 |
The NAS node is not in the AD domain |
|
1.3.6.1.4.1.25506.2.2.42 |
nodeAlarmNfsStat |
0x02056001 |
NFS service error |
|
1.3.6.1.4.1.25506.2.2.43 |
nodeAlarmUmountFail |
0x01040387 |
Failed to unmount the file system while deleting the NAS node |
|
1.3.6.1.4.1.25506.2.2.44 |
nodeAlarmMdsSessionStat |
0x02050101 |
MDS session error |
|
1.3.6.1.4.1.25506.2.2.45 |
nodeAlarmLdapNoExist |
0x02055260 |
The process NSLCD does not exist |
|
1.3.6.1.4.1.25506.2.2.46 |
nodeAlarmFtpStat |
0x02054001 |
FTP service error |
|
1.3.6.1.4.1.25506.2.2.47 |
nodeAlarmPubEthStat |
0x02051001 |
All NICs are disconnected |
|
1.3.6.1.4.1.25506.2.2.48 |
nodeAlarmPartPubEthStat |
0x02051063 |
Some NICs are disconnected |
|
1.3.6.1.4.1.25506.2.2.49 |
nodeAlarmNetHighDelay |
0x01010803 |
Node NIC or Direct connected switch failure |
|
1.3.6.1.4.1.25506.2.2.50 |
nodeAlarmNetHigherDelay |
0x01010804 |
Node NIC or Direct connected switch failure |
|
1.3.6.1.4.1.25506.2.2.51 |
nodeAlarmNetHighestDelay |
0x01010805 |
Node NIC or Direct connected switch failure |
|
1.3.6.1.4.1.25506.2.2.52 |
nodeAlarmLdapNoInstalled |
0x02055261 |
NSLCD is not installed |
|
1.3.6.1.4.1.25506.2.2.53 |
nodeAlarmLdapNoJoined |
0x02055262 |
NAS does not have LDAP |
|
1.3.6.1.4.1.25506.2.2.54 |
nodeAlarmLdapJoinFailed |
0x02055263 |
The NAS node is not in the LDAP domain |
|
1.3.6.1.4.1.25506.2.2.55 |
nodeAlarmBadDisk |
0x01013233 |
OSD not available as the disk is broken |
|
1.3.6.1.4.1.25506.2.2.56 |
nodeAlarmMediumErrTrigBadDisk |
0x01013234 |
OSD not available as the Medium Error |
|
1.3.6.1.4.1.25506.2.2.57 |
nodeAlarmCpuSpecifications |
0x02020601 |
Node does not meet the CPU requirements |
|
1.3.6.1.4.1.25506.2.2.58 |
nodeAlarmMemorySpecifications |
0x02020701 |
Node does not meet the memory requirements |
|
1.3.6.1.4.1.25506.2.2.59 |
nodeAlarmNtpClientStat |
0x02020301 |
NTP client status |
|
1.3.6.1.4.1.25506.2.2.60 |
nodeAlarmNtpOffset |
0x02020304 |
Offset with NTP server |
|
1.3.6.1.4.1.25506.2.2.61 |
nodeAlarmNtpChange |
0x02020302 |
NTP external server status |
|
1.3.6.1.4.1.25506.2.2.62 |
nodeAlarmSlowDisk |
0x02010707 |
Slow disk appears(AIO) |
|
1.3.6.1.4.1.25506.2.2.63 |
nodeAlarmDiskIOTimeout |
0x02010708 |
IO timeout |
|
1.3.6.1.4.1.25506.2.2.64 |
nodeAlarmExternIOTimeout |
0x02010709 |
IO timeout(external check) |
|
1.3.6.1.4.1.25506.2.2.65 |
nodeAlarmOsdAssert |
0x02010710 |
OSD assert appears |
|
1.3.6.1.4.1.25506.2.2.66 |
nodeAlarmSlowDiskSoftEnv |
0x02010706 |
Slow disk appears |
|
1.3.6.1.4.1.25506.2.2.67 |
nodeAlarmCpuModuleAbsent |
0x01010102 |
A CPU module is not in place |
|
1.3.6.1.4.1.25506.2.2.68 |
nodeAlarmMemoryModuleAbsent |
0x01010202 |
A memory module is not in place |
|
1.3.6.1.4.1.25506.2.2.69 |
nodeAlarmFanModuleAbsent |
0x01010302 |
A fan module is not in place |
|
1.3.6.1.4.1.25506.2.2.70 |
nodeAlarmPowerModuleAbsent |
0x01010402 |
A power module is not in place |
|
1.3.6.1.4.1.25506.2.2.71 |
nodeAlarmOsdDown |
0x02043001 |
OSD service error |
|
1.3.6.1.4.1.25506.2.2.74 |
nodeAlarmProcessMemoryUsage |
0x02020401 |
Memory used by the process has exceeded the threshold |
|
1.3.6.1.4.1.25506.2.2.76 |
nodeAlarmDownStat |
0x01010706 |
Node Management Network Abnormal |
|
1.3.6.1.4.1.25506.2.2.101 |
nodeAlarmNetworkDelay |
0x01030100 |
Network flapping |
|
1.3.6.1.4.1.25506.2.2.102 |
nodeAlarmNetworkLoss |
0x01030101 |
NIC packet drops |
|
1.3.6.1.4.1.25506.2.2.103 |
nodeAlarmNetworkLossAndDelay |
0x01030102 |
Network disconnected |
|
1.3.6.1.4.1.25506.2.2.104 |
nodeAlarmSeparate |
0x01030103 |
Poor network performance |
|
1.3.6.1.4.1.25506.2.3.1 |
blockAlarmCopyRepioFail |
0x01040160 |
Background copy failed |
|
1.3.6.1.4.1.25506.2.3.2 |
blockAlarmMigrationRepioFail |
0x01040161 |
Background migration failed |
|
1.3.6.1.4.1.25506.2.3.3 |
blockAlarmThemisNetworkHighDelay |
0x01030140 |
High network delay |
|
1.3.6.1.4.1.25506.2.3.4 |
blockAlarmThemisNetworkDisconnect |
0x01030141 |
Network disconnected |
|
1.3.6.1.4.1.25506.2.3.5 |
blockAlarmThemisNetworkPoorConnect |
0x01030142 |
Poor network performance |
|
1.3.6.1.4.1.25506.2.3.6 |
blockAlarmThemisNetworkFlash |
0x01030143 |
Network flapping |
|
1.3.6.1.4.1.25506.2.3.7 |
blockAlarmThemisNetworkHighErr |
0x01030144 |
NIC error packets |
|
1.3.6.1.4.1.25506.2.3.8 |
blockAlarmThemisNetworkHighDrop |
0x01030145 |
NIC packet drops |
|
1.3.6.1.4.1.25506.2.3.9 |
blockAlarmThemisNetworkHighOthersDown |
0x01030146 |
Peer host offline |
|
1.3.6.1.4.1.25506.2.3.10 |
blockAlarmTgtConfigFail |
0x01010170 |
Volume mapping configuration inconsistency |
|
1.3.6.1.4.1.25506.2.3.11 |
blockAlarmTgtConfigRbFail |
0x01010171 |
Block storage TGT configuration rollback |
|
1.3.6.1.4.1.25506.2.3.12 |
blockAlarmSnapRollbackFail |
0x01040150 |
Snapshot rollback failed |
|
1.3.6.1.4.1.25506.2.3.13 |
blockAlarmCreateTimerSnapFail |
0x01040151 |
Failed to create scheduled snapshots |
|
1.3.6.1.4.1.25506.2.3.14 |
blockAlarmDelStrategyFail |
0x01040152 |
Failed to delete the snapshot schedule |
|
1.3.6.1.4.1.25506.2.3.15 |
blockAlarmCSnapRollBackFail |
0x01040153 |
Consistency group snapshot rollback failed |
|
1.3.6.1.4.1.25506.2.3.16 |
blockAlarmSnapshotRollbackNospaceleft |
0x01040382 |
The system does not have sufficient resources to restore the snapshot |
|
1.3.6.1.4.1.25506.2.3.17 |
blockAlarmSnapshotRollbackNoQuota |
0x01040383 |
The quota does not have sufficient resources to restore the snapshot |
|
1.3.6.1.4.1.25506.2.3.18 |
blockAlarmSnapshotRollbackNoAuthority |
0x01040384 |
Snapshot operate failed |
|
1.3.6.1.4.1.25506.2.3.19 |
blockAlarmSnapshotRollbackNoEmpty |
0x01040388 |
There is currently writing IOs in sanp dirs, or the NAS node has an exception, snapshot rollback failed |
|
1.3.6.1.4.1.25506.2.3.20 |
blockAlarmSnapshotCreateExceed1 |
0x01040385 |
Failed to create the scheduled snapshot. The number of snapshots for the directory has reached the limit of 1024 |
|
1.3.6.1.4.1.25506.2.3.21 |
blockAlarmSnapshotCreateExceed2 |
0x01040386 |
Failed to create the scheduled snapshot. The number of snapshots in the cluster has reached the limit of 8192 |
|
1.3.6.1.4.1.25506.2.3.22 |
blockAlarmSnapshotRollbackHardlink |
0x01040389 |
Not support rollback snap with hard links without keeping new data, snapshot rollback failed |
|
1.3.6.1.4.1.25506.2.3.23 |
blockAlarmRMARDevIdRunError |
0x01040162 |
The running status of remote device has been offline |
|
1.3.6.1.4.1.25506.2.3.24 |
blockAlarmLinkDrlinkLinkoff |
0x01040163 |
Replication link disconnected |
|
1.3.6.1.4.1.25506.2.3.25 |
blockAlarmLinkDrlinkLatency |
0x01040164 |
The latency of Replication link has been out of range |
|
1.3.6.1.4.1.25506.2.3.26 |
blockAlarmLinkRedundency |
0x01040165 |
The remote device has no redundancy replication node |
|
1.3.6.1.4.1.25506.2.3.27 |
blockAlarmRMAPairRollbackFail |
0x01040167 |
RMA pair snap rollback failed |
|
1.3.6.1.4.1.25506.2.3.28 |
blockAlarmRMAPairInvalid |
0x01040168 |
RMA pair is invalid |
|
1.3.6.1.4.1.25506.2.3.29 |
blockAlarmRMAPairInterrupt |
0x01040169 |
RMA pair is interrupted |
|
1.3.6.1.4.1.25506.2.3.30 |
blockAlarmIscsiVridConflict |
0x02010172 |
VRID conflict of iSCSI high availability IP |
|
1.3.6.1.4.1.25506.2.3.32 |
blockAlarmTrashUsage |
0x02040801 |
Exceeding the upper limit of trash lun |
|
1.3.6.1.4.1.25506.2.4.1 |
nasAlarmQuotaReferenceLimited |
0x01050201 |
Reference quota was not created |
|
1.3.6.1.4.1.25506.2.4.2 |
nasAlarmTrashDeleteCephfsError |
0x01041001 |
Failed to delete file under the trash ,error occur in filesystem |
|
1.3.6.1.4.1.25506.2.4.3 |
nasAlarmTrashDeleteExceptError |
0x01041002 |
Failed to delete file under the trash, caught exception |
|
1.3.6.1.4.1.25506.2.4.4 |
nasAlarmTrashRestoreSameName |
0x01041003 |
Failed to restore or move file under the trash, file with same name exists |
|
1.3.6.1.4.1.25506.2.4.5 |
nasAlarmTrashRestoreNotEmpty |
0x01041004 |
Failed to restore or move directory le under the trash, directory is not empty |
|
1.3.6.1.4.1.25506.2.4.6 |
nasAlarmTrashRestoreNotDir |
0x01041005 |
Failed to restore or move file under the trash directory, path is not directory |
|
1.3.6.1.4.1.25506.2.4.7 |
nasAlarmTrashRestoreCephfsError |
0x01041006 |
Failed to restore or move file under the trash directory, error occur in filesystem |
|
1.3.6.1.4.1.25506.2.4.8 |
nasAlarmTrashRestoreExceptError |
0x01041007 |
Failed to restore or move file under the trash directory, caught exception |
|
1.3.6.1.4.1.25506.2.4.9 |
nasAlarmAdsTimeoutOID |
0x02054862 |
Network Connection Exception from the NAS node to the AD domain |
|
1.3.6.1.4.1.25506.2.4.10 |
nasAlarmTrashRestoreQuotaExceedError |
0x01041008 |
Failed to restore or move file under the trash directory, the dest directory have no sufficient capacity |
|
1.3.6.1.4.1.25506.2.4.11 |
nasAlarmTrashRestoreOperatorProhibited |
0x01041009 |
Failed to restore or move file under the trash directory, the operation to destination directory not permitted |
|
1.3.6.1.4.1.25506.2.4.12 |
nasAlarmTrashRestorePermissionDenied |
0x01041010 |
Failed to restore or move file under the trash directory, don’t have permission of the destination directory |
|
1.3.6.1.4.1.25506.2.4.18 |
nasAlarmQuotaFileReachWarning |
0x01050202 |
Quota file number limit has been reached |
|
1.3.6.1.4.1.25506.2.4.19 |
nasAlarmQuotaSpaceReachWarning |
0x01050203 |
Quota space limit has been reached |
|
1.3.6.1.4.1.25506.2.2.84 |
0x02042011 |
Host failure |
|
|
1.3.6.1.4.1.25506.2.2.85 |
0x02042012 |
Unavailable host |
|
|
1.3.6.1.4.1.25506.2.1.18 |
sysAlarmDiskPoolCapabilityUtilization |
0x02040402 |
Diskpool Capacity Usage |
|
1.3.6.1.4.1.25506.2.1.27 |
sysAlarmClusterVerDiff |
0x02040701 |
node_version_inconsistent |
|
1.3.6.1.4.1.25506.2.1.29 |
sysAlarmVerDiffUpgrade |
0x02040702 |
component_version_maybe_inconsistent |
|
1.3.6.1.4.1.25506.2.1.33 |
sysAlarmClusterPoolWritable |
0x02042103 |
Un-writable storage pool |
|
1.3.6.1.4.1.25506.1.7.1.186 |
sysAlarmClusterHealthOID |
0x02042003 |
Cluster unavailable |
|
1.3.6.1.4.1.25506.2.2.88 |
nodeAlarmHostMaintain |
0x01040130 |
Host_maintain_warn |
|
1.3.6.1.4.1.25506.2.1.28 |
sysAlarmUpgradeStatus |
0x01040601 |
upgrade_warn |
|
1.3.6.1.4.1.25506.2.3.31 |
blockAlarmIscsiLinkAbnormal |
0x01010172 |
iSCSI link disconnected abnormally |
|
1.3.6.1.4.1.25506.2.2.9 |
nodeAlarmBandWidthUtilization |
0x01010504 |
Node NIC Bandwidth Usage |
|
1.3.6.1.4.1.25506.2.2.106 |
nodeAlarmEthLinkSpeed |
0x01010505 |
Maximum data transmission rate of a NIC not achieved |
|
1.3.6.1.4.1.25506.2.2.75 |
nodeAlarmSsdEraseOverThreshold |
0x01010704 |
Number of SSD rewrite times has reached the threshold |
|
1.3.6.1.4.1.25506.2.2.77 |
nodeAlarmPdRemappErrCnt |
0x01010707 |
Number of disk remapping times has reached the threshold |
|
1.3.6.1.4.1.25506.2.2.78 |
nodeAlarmPdBadBlockCnt |
0x01010708 |
Number of bad blocks on a disk has reached the threshold |
|
1.3.6.1.4.1.25506.2.2.79 |
nodeAlarmPdReadErrCnt |
0x01010709 |
Number of disk read errors has reached the threshold |
|
1.3.6.1.4.1.25506.2.2.80 |
nodeAlarmPdSelfTestSenseCheckErr |
0x0101070a |
SMART failure predicted |
|
1.3.6.1.4.1.25506.2.2.81 |
nodeAlarmDiskIoSlow |
0x0101070b |
Slow disk I/O |
|
1.3.6.1.4.1.25506.2.2.89 |
nodeAlarmCpuTemp |
0x0101070c |
The temperature of a CPU is too high |
|
1.3.6.1.4.1.25506.2.2.90 |
nodeAlarmEnvTemp |
0x0101070d |
The temperature of server environment is too high |
|
1.3.6.1.4.1.25506.2.2.86 |
nodeAlarmDiskAbnormal |
0x0101070e |
Abnormal disk state |
|
1.3.6.1.4.1.25506.2.2.92 |
nodeAlarmEvtIothWarnCannotRecover |
0x0101070f |
Unrecoverable disk errors |
|
1.3.6.1.4.1.25506.2.2.108 (Primary) |
nodeAlarmDiskIoSlowDetect |
0x01010711 |
Disk IO Timeout |
|
1.3.6.1.4.1.25506.2.2.107 |
nodeAlarmPdPreFailure |
0x01010710 |
The disk might fail |
|
1.3.6.1.4.1.25506.2.2.82 |
nodeAlarmPowerOff |
0x01010801 |
A node was powered off |
|
1.3.6.1.4.1.25506.2.2.98 |
nodeAlarmNodeFailure |
0x01010802 |
Node failure |
|
1.3.6.1.4.1.25506.2.2.99 |
nodeAlarmCpuIsolation |
0x01020001 |
Node CPU Isolation |
|
1.3.6.1.4.1.25506.2.2.100 |
nodeAlarmMemIsolation |
0x01020002 |
Node Memory Isolation |
|
1.3.6.1.4.1.25506.2.1.32 |
clusterMONNum |
0x01042016 |
Inappropriate number of monitor nodes |
|
1.3.6.1.4.1.25506.2.2.72 |
nodeAlarmGaneshaMdsSessionStat |
0x02050201 |
Ganesha mds session error |
|
1.3.6.1.4.1.25506.2.2.73 |
nodeAlarmSmbdMdsSessionStat |
0x02050301 |
MDS session error |
|
1.3.6.1.4.1.25506.2.2.83 |
nodeAlarmHttpStat |
0x02057001 |
HTTP service error |
|
1.3.6.1.4.1.25506.2.4.15 |
nasAlarmSnapStraydirsExceed |
0x01040391 |
The total number of subdirectories deleted from directories that have snapshots has reached the limit |
|
1.3.6.1.4.1.25506.2.4.16 |
nasAlarmSnapshotRollbackCommandFailed |
0x01040394 |
Failed to restore the snapshot because the system cannot determine whether the current node is the primary PEON node or not |
|
1.3.6.1.4.1.25506.2.4.14 |
nasAlarmEventTrashDeleteResidual |
0x01041011 |
Residual information exists while deleting the trash bin of directory |
|
1.3.6.1.4.1.25506.2.2.108 (Branch 50) |
nodeAlarmNetworkClusterCardFault |
0x01030104 |
Bond network port is abnormal |
|
1.3.6.1.4.1.25506.2.2.109 |
nodeAlarmNetworkPublicCardFault |
0x01030105 |
Bond network port is abnormal |
|
1.3.6.1.4.1.25506.2.2.87 |
nodeAlarmLogPartitionUsage |
0x02010306 |
Log partition usage |
|
1.3.6.1.4.1.25506.2.2.97 |
nodeAlarmDiskInfoInconsistent |
0x02010331 |
The disk info in cluster is inconsistent with the actual info |
|
N/A |
N/A |
0x01040395 |
Failed to obtain the current rollback content, the snapshot rollback operation failed |
|
N/A |
N/A |
0x01040396 |
A directory/file with the same name exists in the directory for the rollback file/directory, the snapshot rollback operation failed |
|
N/A |
N/A |
0x01040397 |
The current state of file system is Read-only, the snapshot rollback operation failed |
|
N/A |
N/A |
0x01040398 |
Rollback content or params exception, the snapshot rollback operation failed |
|
N/A |
N/A |
0x01040392 |
Failed to get the rollback task list of the snapshot, the snapshot rollback operation failed |
|
N/A |
N/A |
0x01040393 |
There are long subdirectories or files in the snapshot directory. The snapshot rollback operation fails |
|
N/A |
N/A |
0x01042307 |
The es sync service is abnormal |
|
N/A |
N/A |
0x01042308 |
The haproxy service is abnormal |
|
N/A |
N/A |
0x01042309 |
The elasticsearch service is abnormal |
|
N/A |
N/A |
0x01042310 |
Metadata search service state |
|
N/A |
N/A |
0x02040130 |
AI Engine container state alarm |
|
N/A |
N/A |
0x02010712 |
OSD IO timeout(internal check) |
|
N/A |
N/A |
0x01040700 |
DISK added failed |
|
N/A |
N/A |
0x01042201 |
Database configuration reconstruction failure |
|
N/A |
N/A |
0x01042305 |
Conflict of HA VIP |
|
N/A |
N/A |
0x01042306 |
The Handy service is abnormal |
|
N/A |
N/A |
0x02010099 |
Abnormal disk status |
|
N/A |
N/A |
0x01040131 |
Abnormal AI ENGINE Container Deployment |
|
N/A |
N/A |
0x02042104 |
Cluster Pool Capacity Usage |
|
N/A |
N/A |
0x02010711 |
BAD CRC |
|
N/A |
N/A |
0x02047061 |
rgw_bucket_objnum_exceed_threshold1 |
|
N/A |
N/A |
0x02047062 |
rgw_bucket_objnum_exceed_threshold2 |
|
N/A |
N/A |
0x02047063 |
AS_cache_capacity_insufficient |
|
N/A |
N/A |
0x02047064 |
AS_cache_about_exhaust |
|
N/A |
N/A |
0x02047065 |
AS_total_capacity_insufficient |
|
N/A |
N/A |
0x02047066 |
AS_total_space_about_exhaust |
|
N/A |
N/A |
0x02047067 |
RGW read latency |
|
N/A |
N/A |
0x02047068 |
RGW write latency |
|
N/A |
N/A |
0x02047070 |
Abnormal object gateways in site |
Appendix B Acronyms
|
Acronym |
Full name |
|
A |
|
|
AD |
Active Directory |
|
C |
|
|
CIFS |
Common Internet File System |
|
D |
|
|
DNS |
Domain Name System |
|
F |
|
|
FTP |
File Transfer Protocol |
|
I |
|
|
IO |
Input/Output |
|
L |
|
|
LDAP |
Lightweight Directory Access Protocol |
|
M |
|
|
MDS |
MetaData Server |
|
MIB |
Management Information Base |
|
N |
|
|
NAS |
Network Attached Storage |
|
NFS |
Network File System |
|
O |
|
|
OID |
Object Identifier |
|
P |
|
|
PG |
Placement Group |
|
S |
|
|
SNMP |
Simple Network Management Protocol |
|
V |
|
|
VRRP |
Virtual Router Redundancy Protocol |
