Actions taken if ISM can detect storage devices but cannot detect file engines

3

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.

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.

How Can I Do If the ISM Can Detect Storage Devices Only, But Cannot Detect File Engines?
This fault occurs because 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 devices and run chgnasinfo to register the management IP address of the file engine again.

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.

Can S series switches be configured not to take any action after a loop is detected
Huawei S series (except the S1700) and E series switches performs the configured default action after detecting a loop, that is, shutting down interfaces. The action can be changed but cannot be disabled. When the action is changed to trap, the switches only report traps and do not take any other action after detecting a loop. Command used to configure the action performed on an interface after LDT detects a loop: loop-detection mode { port-trap | port-blocking | port-nolearning | port-shutdown | port-quitvlan } Command used to configure the action performed on an interface after LBDT detects a loop: loopback-detect action { block | nolearn | shutdown | trap | quitvlan } Note: For S series switches, the port-quitvlan and quitvlan actions are supported in V200R002 and later versions.

Actions taken if a file engine node works incorrectly
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.

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