Got it

The traffic on the heartbeat interface is unbalanced.

Created: Oct 31, 2019 07:01:37Latest reply: Oct 31, 2019 07:17:03 744 2 0 0 0
  Rewarded HiCoins: 0 (problem resolved)

Hi all,

I have two firewalls configured with HRP. When the Eth-Trunk is used as the heartbeat interface, the traffic is unbalanced.


 

firewall


After HRP is established, only G1/0/0 has traffic and G2/0/0 has no traffic. We have checked the link problems. 

Are the HRP configurations incorrect?

#

 hrp enable

 hrp interface Eth-Trunk1 remote 10.10.0.2

undo hrp track trunk-member enable

 hrp preempt delay 200

 hrp track bfd-session 101

#

interface Eth-Trunk1

 ip address 10.10.0.1 255.255.255.30

 mode lacp-static

#

interface GigabitEthernet1/0/1

 eth-trunk 1

interface GigabitEthernet1/0/2

 eth-trunk 1


Thanks.

Featured Answers
Popeye_Wang
Admin Created Oct 31, 2019 07:03:31

Hi Steelblue,

If the Eth-Trunk is used as the heartbeat interface, you must run the load-balance packet-all command on the Eth-Trunk to set the load balancing mode to per-packet load balancing.

Why do you need to configure this command?

First, you need to know that the Eth-Trunk has two load balancing modes:

l   Per-flow load balancing: Packets are load balanced based on the source and destination IP addresses of packets. For example, the first packet of the flow from 1.1.1.1 to 2.2.2.2 is sent from interface A. Then follow-up packets are also sent from interface A. The configuration command is load-balance ip (in V500R001, the command is load-balance src-dst-ip). By default, the device uses per-flow load balancing.

l   Per-packet load balancing: All packets are load-balanced. For example, the Eth-Trunk member interfaces are interfaces A and B. The first packet is sent from interface A, the second from interface B, the third from interface A, the fourth from interface B, and the others follow the same rule.

Heartbeat packets are transmitted between heartbeat interfaces, and the source and destination addresses are fixed.

l   Source address: IP address of the heartbeat interface

l   Destination address: If parameter remote is not specified when the heartbeat interfaces are configured, heartbeat packets are VRRP packets, and the destination address is the multicast address 224.0.0.18. If parameter remote and the remote heartbeat interface address are specified when the heartbeat interfaces are configured, the heartbeat packets are encapsulated into unicast UDP packets, and the destination address is the remote heart interface address.

If the Eth-Trunk uses per-flow load balancing, packets are always sent from the same physical interface because the source and destination IP addresses of the heartbeat packets are fixed. In this case, the traffic is not balanced between multiple physical interfaces.

Hope this helps you.

View more
  • x
  • convention:

All Answers

Hi Steelblue,

If the Eth-Trunk is used as the heartbeat interface, you must run the load-balance packet-all command on the Eth-Trunk to set the load balancing mode to per-packet load balancing.

Why do you need to configure this command?

First, you need to know that the Eth-Trunk has two load balancing modes:

l   Per-flow load balancing: Packets are load balanced based on the source and destination IP addresses of packets. For example, the first packet of the flow from 1.1.1.1 to 2.2.2.2 is sent from interface A. Then follow-up packets are also sent from interface A. The configuration command is load-balance ip (in V500R001, the command is load-balance src-dst-ip). By default, the device uses per-flow load balancing.

l   Per-packet load balancing: All packets are load-balanced. For example, the Eth-Trunk member interfaces are interfaces A and B. The first packet is sent from interface A, the second from interface B, the third from interface A, the fourth from interface B, and the others follow the same rule.

Heartbeat packets are transmitted between heartbeat interfaces, and the source and destination addresses are fixed.

l   Source address: IP address of the heartbeat interface

l   Destination address: If parameter remote is not specified when the heartbeat interfaces are configured, heartbeat packets are VRRP packets, and the destination address is the multicast address 224.0.0.18. If parameter remote and the remote heartbeat interface address are specified when the heartbeat interfaces are configured, the heartbeat packets are encapsulated into unicast UDP packets, and the destination address is the remote heart interface address.

If the Eth-Trunk uses per-flow load balancing, packets are always sent from the same physical interface because the source and destination IP addresses of the heartbeat packets are fixed. In this case, the traffic is not balanced between multiple physical interfaces.

Hope this helps you.

View more
  • x
  • convention:

Hello,

You can configure a load balancing mode based on the traffic model. When a parameter of traffic changes frequently, you can set the load balancing mode based on this parameter to ensure that the traffic is evenly load balanced. For example, if IP addresses of packets change frequently, select the dst-ip, src-ip, or src-dst-ip load balancing mode. If MAC addresses of packets change frequently and IP addresses are fixed, select the dst-mac, src-mac, or src-dst-mac load balancing mode.


Thanks

View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

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.