Actions taken if an IP address fails to be configured

2

If an IP address fails to be configured, perform the following procedure:
1. Modify the configurations based on the error message.
2. Ensure that the physical, virtual, and management IP addresses do not conflict with each other. This is because the physical and virtual IP addresses that you are supposed to enter are the start IP addresses �?ISM then automatically configures subsequent IP addresses based on the number of network ports.

Other related questions:
Actions taken if the start physical IP address cannot be connected
If a PC fails to connect to the start physical IP address of a file engine's management network port, perform the following procedure: 1. Ensure that management network cables are correctly connected. 2. Ensure that other IP addresses of the file engine are on the same network segment with its start physical IP address. For example, the configured start physical IP address of a file engine is 192.168.1.1/255.255.0.0. The file engine's access network ports must have an IP address from the 192.168.X.X network segment. 3. Run the ping command.

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 to be taken if an account of a WLAN device is locked
For WLAN devices, if incorrect password is entered repeatedly during a certain period of time, the account will be locked. Generally, the account will be automatically unlocked after 5 minutes. Therefore, if an account is locked, try again 5 minutes later, or use another user account to log in to the device.

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