HP VPN Firewall Appliances NAT and ALG Command Reference
14
Hardware Value ran
g
e
F5000 0 to 255
F5000-S/F5000-C 0 to 255
VPN firewall modules 0 to 2047
20-Gbps VPN firewall modules 0 to 2047
vpn-instance vpn-instance-name: Specifies the VPN to which the addresses of the address pool belong.
The vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. With this option,
inter-VPN access through NAT is supported. Without this option, the addresses in the address pool do
not belong to any VPN.
no-pat: Specifies not to use the TCP/UDP port number for many-to-many NAT. If this keyword is not
specified, the TCP/UDP port number is used for many-to-one NAT.
port-preserved: Tries to preserve port number for PAT.
track vrrp virtual-router-id: Associates address translation on a specific outbound interface with a VRRP
group. The virtual-router-id argument indicates the number of the VRRP group in the range of 1 to 255.
Without this argument specified, no VRRP group is associated.
Usage guidelines
You can configure multiple associations or use the undo command to remove an association from an
interface that serves as the egress of an internal network to the external network.
When the undo nat outbound command is executed to remove an association, the NAT entries
depending on the association are not deleted. They are aged out automatically after 5 to 10 minutes.
During this period, the involved users cannot access the external network whereas all the other users are
not affected.
When an ACL rule is not operative, no new NAT session entry depending on the rule can be created.
However, existing connections are still available for communication.
If a packet matches the specified next hop, the packet is translated using an IP address in the address
pool. If not, the packet is not translated.
You can bind an ACL to only one address pool on an interface. An address pool can be bound to
multiple ACLs.
NAPT cannot translate connections from external hosts to internal hosts.
In stateful failover networking, make sure you associate each address pool configured on an interface
with one VRRP group only. Otherwise, the system associates the address pool with the VRRP group
having the highest group ID.
For some devices, the ACL rules referenced by the same interface cannot conflict. That is, the source IP
address, destination IP address, and VPN instance information in two ACL rules cannot be the same. For
basic ACLs (in the range of 2000 to 2999), if the source IP address and VPN instance information in two
ACL rules are the same, a conflict occurs.
Examples
# Configure NAT for hosts on subnet 10.110.10.0/24. The NAT address pool contains addresses
202.110.10.10 through 202.110.10.12. Assume that interface GigabitEthernet 0/1 is connected to the
Internet.
<Sysname> system-view
[Sysname] acl number 2001