Precaution of NAT configure as USG9300 takes two-node cluster hot backup

Hello,

Handling Process
NullRoot Cause
Same precaution with middle and low-end firewall and something special.
Same Precaution:
1.If the two-node cluster hot backup NAT address pool is in the same network segment with the interface IP, It is necessary that binding NAT pool and VRRP team ID.
The reason is that, in this way, it will avoids the collision When upstream and downstream device request the ARP of NAT pool, Two USG9300 will respond ARP message.
2. If the two-node cluster hot backup NAT address pool is not in the same network segment with the interface IP, no special operation should be done.
Special Precaution:
In two-node cluster load balancing mode, to avoid the collision of NAT pool interface, the order “hrp nat ports-segment primary” should be configured in one USG9300,and the order “hrp nat ports-segment secondary” should be configured in another.Solution
Suggestions
In two-node cluster load balancing mode, the order “hrp nat ports-segment primary” and “hrp nat ports-segment secondary” should be configured specially.

Hope to help you!