How Can I Do If a Node of a File Engine Fails to Be Detected During File Engine Configuration?

2

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.

Other related questions:
Failure to detect file engines during file configuration
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.

How Can I Do If the ISM Fails to Detect File Engines?
This fault may occur because of the abnormal network, incorrect file engine, incorrect password, or locked user. To rectify the fault, perform the following operations: ? Ensure that the management network of the file engines is correct. ? Log in to the file engines as user master and ensure that the file engines are working correctly. ? If you fail to log in to the file engines as user master, log in as user support. Then run su —master to switch to the master mode. Run admin lockeduser show to check whether user master is locked. If it is locked, run admin unlock master to unlock it. If you enter wrong passwords for consecutive three times, you will be locked for five minutes. When logging in to the ISM as an administrator, you are user master on the underlying devices. ? If file engines still fail 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. (The earlier storage device uses a non-security requirement 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 shownasinfo to check the users and user levels (a total of four levels). Run chanasinfo to change the password. The default passwords of user master, support, and only are respectively Master@storage, support@storage, and Readonly@storage.

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.

How Can I Do If I Fail to Clear File Engine Configurations During Re-Deployment?
If you fail to clear file engine configurations during re-deployment, perform the following operations: 1. Verify that file system data is no longer needed and can be deleted. 2. Delete all file systems and network port bindings as prompted. The file systems include _LogFS_. You are advised to manually delete all file systems and pools before re-deployment. 3. Restart all nodes for re-deployment.

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.

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