No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


How Can I Do If the ISM Fails to Detect File Engines?

Publication Date:  2016-11-28 Views:  258 Downloads:  0
Issue Description
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.