Actions taken if the hardware is inconsistent with the standard configuration during the adding of a secondary node

0

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.

Other related questions:
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.

Actions taken if the number of nodes exceeds the upper limit during the adding of a secondary node
This fault occurs if the model of the storage device is not detected, or the number of nodes in the license file is incorrect or exceeds the specifications. To rectify the fault, ensure the following: - That the storage device is correctly connected. Log in to the storage device as user support and check whether disk array information exists in Internet Small Computer Systems Interface (iSCSI). - That the number of nodes for each network attached storage (NAS) feature in the license file is consistent with that of configured nodes. The number of nodes for each NAS feature must be equal to or larger than that of configured nodes. - That the number of configured nodes does not exceed that of the nodes mapping to the storage device in the specifications list.

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.

How Can I Do If a Message Is Displayed Indicating That the Hardware Is Inconsistent with the Standard Configuration?
File engine configurations include maximum configuration and minimum configuration. Different device models correspond to different configurations. If an incorrect configuration is selected, the configuration fails. Use the correct control board or CPU/memory.

Actions taken if an IP address fails to be configured
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.

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