Administrator action
1. Locate the nodes that are no longer associated with the underprovisioned node pool.
a. If a node became unprovisioned, you will see that node identified in a separate event, 200010007. You can attempt to
provision the node back into the node pool by running the following command:
isi_evaluate_provision_drive
b. If a node was smartfailed, you can identify the node by running the following command:
isi status
Address the cause of the smartfail and add the node back to the cluster. The node will be automatically provisioned to its
original node pool.
2. If the issue persists, contact Support.
Gather logs, and then contact Technical Support for additional troubleshooting. For instructions on how to gather cluster
logs, see Gathering cluster logs.
200010009
Node has recovered from a panic.
Administrator action
A service request (SR) has been opened on your behalf.
200020001
An Ethernet link is not operating at maximum throughput.
Administrator action
Determine whether the issue is related to the cable or the node. Perform the following steps in the order listed. If the issue
resolves after a step, there is no need to complete the subsequent steps.
1. Verify the following connections:
● All of the cables in the rack and in adjacent racks are connected securely to the node and neither the cable nor the
connector is damaged.
● The cable is rated for the appropriate Ethernet speed.
● The switch port speed is set to the same or higher speed as the Ethernet cable.
●
The switch port is set to the Full Duplex setting.
2. If the cable is connected securely, plug the cable into a different node that has a network port functioning at full speed and
that has an identical network configuration. When you plug the cable into the other node, leave the other end of the cable
plugged into the same switch port.
● If the issue persists after plugging the cable into a different node, replace the cable.
● If the issue persists after replacing the cable, move the cable to another port on the switch.
● If the issue persists after moving the cable to another port on the switch, review the switch logs and consult your switch
user manual.
If the event persists, gather logs, and then contact Technical Support for additional troubleshooting. For instructions on how to
gather cluster logs, see Gathering cluster logs.
56
Software events
To Next Page
Loading...
Need help?
General