Preventing failures of clients re-initiating access requests after one node is faulty

0

The InfoEqualizer feature employs a node failover mechanism that can detect a faulty node and forward access requests from the faulty node to other nodes.

Other related questions:
Forwarding access requests initiated by clients using a node's static IP address to another node after node failover
The InfoEqualizer feature employs a domain name resolution mechanism that can dynamically allocate access requests initiated by clients using domain names to other nodes after node failover.

Evenly distributing access requests initiated by clients using nodes' static IP addresses based on load balancing policies
The InfoEqualizer feature employs a domain name resolution mechanism that can dynamically allocate access requests initiated by clients using domain names to target nodes based on load balancing policies.

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.

Client-initiated VPN
In client-initiated VPN, the LNS authenticates users through PPP authentication (PAP or CHAP). In CLI configurations, this is the PPP authentication configured on the VT interface.

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