Got it

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

109

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:
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.
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.
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.
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.
If you have more questions, you can seek help from following ways:
To WeiKnow To Live Chat

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.