Basic Information:
Item | Description |
Storage type | Distributed storage |
Product version | FusionStorage 8.0.0; FusionStorage 8.0.1; OceanStor 100D 8.0.2; OceanStor 100D 8.0.3; OceanStor Pacific series 8.1.0; OceanStor Atlantic series 8.1.0 |
Problem type | Alarm |
Keyword | Node adding; NIC port exceptions |
Symptom:
Alarm (ID: 0x1EA620007) indicating that an NIC port is abnormal is reported on DeviceManager and cannot be automatically cleared.
Diagnosis:
In the Management IP Address text box on the hardware management page of DeviceManager, search for the IP address of the node for which the alarm is generated. If the corresponding node is not found, this document is applicable. In this case, rectify the fault by referring to operations described in Solution. If yes, go to 2.
Log in to the faulty node and run the following commands to query its front-end and back-end storage IP addresses:
cat /opt/fusionstorage/agent/conf/node_cluster_ip
cat /opt/fusionstorage/agent/conf/node_storage_ip
Run the ip addr | grep -B 2 "Front-end or back-end storage IP address of the faulty node" command to query the name of the corresponding network port. For example, in the following figure, the port name is eth0.
If the storage IP addresses of the node are not in bond mode, check whether the name of the faulty network port in the alarm information is the same as that of the port name queried in 3. If they are the same, this document is not applicable. Otherwise, rectify the fault by referring to this section.
If the storage IP addresses of the node are in bond mode, run the cat /sys/class/net/Bond port name/bonding/slaves command to check whether the faulty network port is a member port of the bond port. If yes, this document is not applicable. Otherwise, rectify the fault by referring to this section.
Causes:
After a user logs in to DeviceManager and successfully adds a node, the configured storage network port is faulty. As a result, an alarm is generated on DeviceManager. In this case, return to the Configure Storage Network page, remove the faulty node from the cluster, or select another normal network port to configure the storage IP address. After the configuration is successful, the faulty network port is no longer used and monitored. Therefore, the alarm cannot be cleared.
Solution:
Log in to DeviceManager and manually clear the alarm.
