hrp nat resource
Function
The hrp nat resource command specifies the ranges of resource that can be used by the NAT address pools on the master and backup FWs.
The undo hrp nat resource command restores the default ranges of resource that can be used by the NAT address pools on the master and backup FWs.
Parameters
| Parameter | Description | Value |
|---|---|---|
primary-group |
Indicates the primary-group of resources. |
- |
secondary-group |
Indicates the secondary-group of resources. |
- |
Usage Guidelines
Usage Scenario
In the load balance dual-system hot backup environment, there is service traffics passing through both devices. When NAPT is configured on two devices, the same public port number may be assigned to them. As a result, port allocation fails and users cannot access the Internet. To avoid that conflict, configure available NAT resource on both devices respectively. On this situation, if the command hrp nat resource primary-group is configured on master device, the command hrp nat resource secondary-group will be generated on slave device automatically (if the command hrp nat resource secondary-group is configured on master device, the command hrp nat resource primary-group will be generated on slave device automatically).
After the function is configured, the resource on the master and slave device is divided into two equal segments. The primary-group indicates the primary-group of the resource. And the secondary-group indicates the secondary-group of the resource. If the NAPT is adopted, the ports of public IP address will be equally divided.
This command can be used together with port pre-allocation and static mapping, but the address pool mode of pre-allocation and static mapping must be PAT.
In the active/standby backup scenario, you need not configure this command. You must configure this command in hot standby deployment in load balancing mode.
If you run the command repeatedly, the latest configuration overwrites the original one.
Precautions
After this command is run, the device updates the session table and ages out the session resources that do not belong to the local device. As a result, the device needs to create sessions for some received traffic, instead of directly forwarding the traffic according to the session table. This affects service traffic forwarding efficiency.