Retaining online services of clients connected to a faulty node


The InfoEqualizer feature introduces dynamic IP addresses, which each corresponds to a dynamic domain name. If domain names are not resolved, when clients access a node using the node's IP address and the node becomes faulty later, this IP address can automatically "float" to another node.

Other related questions:
In FusionInsight,How to handle Service Node Faulty
1.FusionInsight Manager regularly checks the running status of each node. In case one node is lost due to network or hardware problems, FusionInsight Manager generates the alarm "ALM-12006 Node Fault". Handle the alarm based on the handling procedure. 2.If the alarm persists after step 1, see 10.2.3 Replacing a Faulty Nodeto resolve the problem.

Checking clients connected to a node
Procedure for checking clients connected to a node: 1. Log in to DeviceManager. 2. Choose System > Device View. 3. Click the name of a node on the Node List tab page. 4. Click the Clients tab to view client information about the node.

In FusionInsight,How does Service Node Faulty impact on the system.
?The DataNode service is installed on service nodes by default. If less than three service nodes are lost, the service is not affected, but the service response time prolongs. You need to rectify the fault promptly. ?If more than three service nodes are lost, files stored in the Hadoop distributed file system (HDFS) may be lost and the service can be affected. You are advised to stop all service reading operations and rectify the fault immediately.

Does MFF allow online users to retain online after the switch restarts
In V100R006 and later versions, when both MFF and DHCP snooping are enabled, you can use the dhcp snooping user-bind autosave file-name command to back up DHCP snooping binding entries in a specified file. This configuration allows online users to retain online after the switch restarts. Note that the backup file saves only the first gateway address of users.

Controlling the range of nodes connected to each client
The InfoEqualizer feature introduces the concepts of zone and subnet. A zone corresponds to a group of nodes and can have its own domain name and load balancing policy. Clients can send access requests to nodes in a specific zone using the domain name of the zone.

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