Failure to detect file engines during file configuration

0

All file engines or one specific engine may fail to be detected.

If all file engines fail to be detected, perform the following procedure:
1. Disable software that impedes MAC broadcasting, such as Symantec firewall.
2. Ensure that the PC and file engines are connected to the same subnet.
3. Verify that the management ports of file engines are correctly connected.
4. Verify that file engines are correctly started.

If one specific file engine fails to be detected, perform the following procedure:
1. Ensure that the PC and the file engine are connected to the same subnet.
2. Verify that the management port of the file engine is correctly connected.
3. Verify that the file engine is correctly started.

Other related questions:
How Can I Do If a Node of a File Engine Fails to Be Detected During File Engine Configuration?
If you fail to detect a node of a file engine, perform the following operations: Verify that the management port of the file engine is correctly connected. Verify that the file engine is correctly started.

Failure to clear file engine configurations during re-deployment
If file engine configurations fail to be cleared during re-deployment, perform the following procedure: 1. Verify that file system data is no longer needed and can be deleted. 2. Delete all file systems (including _LogFS_ which is used to store system logs), network bonds, and storage pools as prompted. 3. Restart all nodes for re-deployment.

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 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 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.

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