Why Do Many IP Addresses Accessing the Backend ECSs Associated with a Load Balancer Start with 100.125?


This issue is caused by the health checks.

In addition to forwarding access requests to the backend ECSs using the internal IP addresses of system servers, ELB performs health checks for the ECSs to monitor their status. When forwarding access requests or initiating health check requests, the ELB system translates source IP addresses contained in the requests into IP addresses starting with 100.125, such as

To make your external services available, ensure that the security group containing the ECSs allows traffic from these IP addresses.

Other related questions:
Load balancing
The functions and meanings of load balancing are described as follows: When multiple routes have the same routing protocol preference and metric, these routes are called equal-cost routes, among which load balancing can be implemented. Routers support the multi-route mode, allowing you to configure multiple routes with the same destination and preference. If the destinations and costs of multiple routes discovered by the same routing protocol are the same, load balancing can be performed among the routes. Run the maximum load-balancing number command in the views of various protocols to implement load balancing. Load balancing falls into the following two modes: -Packet-by-packet When the packet-by-packet load balancing is configured, firewalls at the network layer forward packets to the same destination through various equal-cost paths. That is, switches always choose the next hop address that is different from the last one to send packets. -Session-by-session When session-by-session load balancing is configured, firewalls forward packets according to the source address, destination address, source port, destination port, and protocol contained in the packets. When the five factors are the same, firewalls always choose the same next hop address as the last one used to send the packets.

Why does a trunk interface not load balance packets with different MAC addresses
The load balancing function of the trunk interface takes effect only for known unicast packets. To enable the load balancing function of the trunk interface for broadcast packets, Layer 3 multicast packets, and unknown unicast packets on the S3752 and the S5700, you can run the unknown-unicast load-balance command in the system view. At present, the S3728 and the S2700 do not support this command.

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.

Methods used to implement virtual load balancing
Currently, virtual and physical SVN load balancing can be implemented. vLB is used to balance the load of multiple WIs. Physical LB balances the load of WIs to prevent a large number of users from accessing the same WI.

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