HPE FlexNetwork HSR6800 Configuration Manual page 171

Figure 65 Network diagram
Requirements analysis
This is a typical application of twice NAT. Both the source and destination addresses of packets
between the two VPNs need to be translated. Configure static NAT on both interfaces connected to
the VPNs on the NAT device.
Configuration procedure
# Specify VPN instances and IP addresses for the interfaces on the router. (Details not shown.)
# Configure a static outbound NAT mapping between 192.168.1.2 in vpn 1 and 172.16.1.2 in vpn 2.
<Router> system-view
[Router] nat static outbound 192.168.1.2 vpn-instance vpn1 172.16.1.2 vpn-instance vpn2
# Configure a static outbound NAT mapping between 192.168.1.2 in vpn 2 and 172.16.2.2 in vpn 1.
[Router] nat static outbound 192.168.1.2 vpn-instance vpn2 172.16.2.2 vpn-instance vpn1
# Enable static NAT on interface GigabitEthernet 2/1/2.
[Router] interface gigabitethernet 2/1/2
[Router-GigabitEthernet2/1/2] nat static enable
[Router-GigabitEthernet2/1/2] quit
# Enable static NAT on interface GigabitEthernet 2/1/1.
[Router] interface gigabitethernet 2/1/1
[Router-GigabitEthernet2/1/1] nat static enable
[Router-GigabitEthernet2/1/1] quit
Verifying the configuration
# Verify that Host A and Host B can access each other. The public address for Host A is 172.16.1.2
and that for Host B is 172.16.2.2. (Details not shown.)
# Display all NAT configuration and statistics.
[Router] display nat all
Static NAT mappings:
Totally 2 outbound static NAT mappings.
IP-to-IP:
Local IP
Global IP
Local VPN
Global VPN
Config status: Active
IP-to-IP:
Local IP
Global IP
Local VPN
Global VPN
Config status: Active
: 192.168.1.2
: 172.16.1.2
: vpn1
: vpn2
: 192.168.1.2
: 172.16.2.2
: vpn2
: vpn1
158