Actions taken if a file engine node works incorrectly

1

If a file engine node is working incorrectly, perform the following procedure:
1. Ensure that heartbeat connections and heartbeat switches are working correctly.
2. Ensure that the faulty node is correctly started up.

Other related questions:
Actions taken if ISM fails to detect file engines
ISM fails to detect a file engine if the network is interrupted, the file engine is faulty, the password is incorrect, or the user is locked. To rectify the fault, perform the following procedure: 1. Ensure that the management network of the file engine is correct. 2. Log in to the file engine as user master and ensure that the file engine is working correctly. 3. If you fail to log in to the file engine as user master, log in as user support. Run the su -master command to switch to the master mode. Then run the admin lockeduser show command to check whether user master is locked. If the user is locked, run the admin unlock master command to unlock the user. If you enter incorrect passwords three consecutive times, you will be locked out of trying again for 5 minutes. After logging in to ISM as an administrator, you are user master on the underlying devices. 4. If the file engine still fails to be detected after user master is unlocked, it is likely that the password for logging in to the file engine saved on the storage device is incorrect. Note: The earlier storage device uses a non-security password. Therefore, the password is inconsistent with that in the file engine's new specifications during an upgrade. Log in to the storage device as user admin and enter the engineer mode. Then run the shownasinfo command to check the users and user levels (a total of four levels). Run the chanasinfo command to change the password. The default passwords of users master, support, and only are Master@storage, support@storage, and Readonly@storage, respectively.

Actions taken if the hardware is inconsistent with the standard configuration during the deployment of a file engine
The file engine configuration varies depending on the device model. If an incorrect configuration is selected, the configuration fails. Use the correct controller module or CPU/memory.

Actions taken if ISM can detect storage devices but cannot detect file engines
This fault occurs if no deployment tools are used for deployment and the procedure of manual deployment is incomplete, or the file engine information on the storage devices was deleted. To rectify the fault, enter the engineer mode on the storage device and run the chgnasinfo command to register the management IP address of the file engine again.

Actions taken if the number of nodes exceeds the upper limit during the adding of a secondary node
This fault occurs if the model of the storage device is not detected, or the number of nodes in the license file is incorrect or exceeds the specifications. To rectify the fault, ensure the following: - That the storage device is correctly connected. Log in to the storage device as user support and check whether disk array information exists in Internet Small Computer Systems Interface (iSCSI). - That the number of nodes for each network attached storage (NAS) feature in the license file is consistent with that of configured nodes. The number of nodes for each NAS feature must be equal to or larger than that of configured nodes. - That the number of configured nodes does not exceed that of the nodes mapping to the storage device in the specifications list.

Actions taken if the hardware is inconsistent with the standard configuration during the adding of a secondary node
The file engine configuration varies depending on the device model. If an incorrect configuration is selected, the configuration fails. Use the correct controller module or CPU/memory.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top