Contents

Introduction· 1

Prerequisites· 1

Restrictions and guidelines· 1

Example: Configuring basic NAT· 1

Network configuration· 1

Analysis· 2

Procedures· 2

Specifying IP addresses for the interfaces· 2

Configuring outbound NAT for internal users· 2

Implementing load sharing among FTP servers· 3

Configuring a QoS policy to redirect traffic to the local device· 3

Verifying the configuration· 4

Configuration files· 6

Related documentation· 6

 

Introduction

This document provides NAT configuration examples.

Prerequisites

This document is not restricted to specific software or hardware versions.

The configuration examples in this document were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.

The following information is provided based on the assumption that you have basic knowledge of NAT.

Restrictions and guidelines

A QoS policy is required on an interface to redirect the incoming traffic to the NAT-capable service module. For more information about QoS policies, see ACL and QoS Configuration Guide.

Example: Configuring basic NAT

Network configuration

As shown in Figure 1, the internal users use the IP addresses in the range of 10.110.0.0 to 10.110.2.255. The private IP addresses of the FTP servers are from 10.110.3.1 to 10.110.3.3. These servers provide FTP services to external users. The company has three public IP addresses from 61.16.0.1 to 61.16.0.3.

Configure NAT on the device to implement the following:

·     For outbound packets sent by the internal users, translate the private IP addresses of internal users to the public IP addresses in the range of 61.16.0.2 to 61.16.0.3.

·     Allow the internal and external users to use the IP address 61.16.0.1 to access the FTP servers.

·     Implement load sharing among the FTP servers and do not allow connections that are initiated by the FTP servers to the external network.

Figure 1 Network diagram

‌

Analysis

·     To translate IP addresses in the range of 10.110.0.0 to 10.110.2.255 into IP addresses in the range of 61.16.0.2 to 61.16.0.3, configure an ACL to identify these packets. Then configure outbound address translation on packets identified by the ACL on Ten-GigabitEthernet 0/0/16.

·     To allow three FTP servers to load share services, configure NAT server group to implement load sharing.

·     To allow internal hosts to access the internal FTP server by using a public IP address, enable AT hairpin on Ten-GigabitEthernet 0/0/15 of the device.

Procedures

Specifying IP addresses for the interfaces

# Specify IP addresses for Ten-GigabitEthernet 0/0/15 and Ten-GigabitEthernet 0/0/16.

<Device> system-view

[Device] interface Ten-GigabitEthernet0/0/15

[Device-Ten-GigabitEthernet0/0/15] ip address 10.110.0.1 255.255.252.0

[Device-Ten-GigabitEthernet0/0/15] quit

[Device] interface Ten-GigabitEthernet0/0/16

[Device-Ten-GigabitEthernet0/0/16] ip address 61.16.0.1 255.255.255.0

[Device-Ten-GigabitEthernet0/0/16] quit

Configuring outbound NAT for internal users

# Configure NAT address group 0, and add public IP address 61.16.0.2 and 61.16.0.3 to the group.

[Device] nat address-group 0

[Device-nat-address-group-0] address 61.16.0.2 61.16.0.3

[Device-nat-address-group-0] quit

# Configure ACL 2000 to identify packets only from subnet 10.110.0.0 to 10.110.2.255.

[Device] acl basic 2000

[Device-acl-ipv4-basic-2000] rule permit source 10.110.0.0 0.0.1.255

[Device-acl-ipv4-basic-2000] rule permit source 10.110.2.0 0.0.0.255

[Device-acl-ipv4-basic-2000] quit

# Configure outbound dynamic NAT on Ten-GigabitEthernet 0/0/16 to translate source IP address in packets permitted by ACL 2000 into the IP addresses in NAT address group 0.

[Device] interface Ten-GigabitEthernet0/0/16

[Device-Ten-GigabitEthernet0/0/16] nat outbound 2000 address-group 0

[Device-Ten-GigabitEthernet0/0/16] quit

Implementing load sharing among FTP servers

# Create NAT server group 0, and add servers at 10.110.3.1, 10.110.3.2, 10.110.3.3 to the group.

[Device] nat server-group 0

[Device-nat-server-group-0] inside ip 10.110.3.1 port 21

[Device-nat-server-group-0] inside ip 10.110.3.2 port 21

[Device-nat-server-group-0] inside ip 10.110.3.3 port 21

[Device-nat-server-group-0] quit

# Associate NAT server group 0 with Ten-GigabitEthernet 0/0/16 so that servers in the server group can load share FTP services.

[Device] interface Ten-GigabitEthernet0/0/16

[Device-Ten-GigabitEthernet0/0/16] nat server protocol tcp global 61.16.0.1 ftp inside server-group 0

# Enable NAT hairpin on Ten-GigabitEthernet 0/0/15.

[Device] interface Ten-GigabitEthernet0/0/15

[Device-Ten-GigabitEthernet0/0/15] nat hairpin enable

Configuring a QoS policy to redirect traffic to the local device

# Configure ACL 2001 to identify packets to be redirected to the NAT-capable service module. In this example, the packets are those to be translated, therefore, define the same ACL rules as those in ACL 2000.

[Device] acl basic 2001

[Device-acl-ipv4-basic-2001] rule permit source 10.110.0.0 0.0.1.255

[Device-acl-ipv4-basic-2001] rule permit source 10.110.2.0 0.0.0.255

[Device-acl-ipv4-basic-2001] quit

# Create traffic class 1 and define a match criterion for the traffic class to match ACL 2001.

[Device] traffic classifier 1 operator and

[Device-classifier-1] if-match acl 2001

[Device-classifier-1] quit

# Create traffic behavior 1 and configure redirecting traffic to the local device in the traffic behavior 1.

[Device] traffic behavior 1

[Device-behavior-1] redirect local

[Device-behavior-1] quit

# Create QoS policy 1 and associate traffic class 1 with traffic behavior 1 in the QoS policy.

[Device] qos policy 1

[Device-qospolicy-1] classifier 1 behavior 1

[Device-qospolicy-1] quit

# Apply the QoS policy to the inbound direction of Ten-GigabitEthernet 0/0/15.

[Device] interface Ten-GigabitEthernet0/0/15

[Device-Ten-GigabitEthernet0/0/15] qos apply policy 1 inbound

[Device-Ten-GigabitEthernet0/0/15] quit

Verifying the configuration

# Access the WWW server from PC 1. Verify that a NAT session is created on the device.

[Device] display nat session verbose

Initiator:

  Source      IP/port: 10.110.1.10/1024

  Destination IP/port: 200.1.1.10/80

  DS-Lite tunnel peer: -

  VPN instance/VLAN ID/Inline ID: -/-/-

  Protocol: TCP(6)

  Inbound interface: Ten-GigabitEthernet0/0/15

Responder:

  Source      IP/port: 200.1.1.10/80

  Destination IP/port: 61.16.0.2/1025

  DS-Lite tunnel peer: -

  VPN instance/VLAN ID/Inline ID: -/-/-

  Protocol: TCP(6)

  Inbound interface: Ten-GigabitEthernet0/0/16

State: TCP_CLOSE

Application: HTTP

Start time: 2014-07-08 13:30:47

Initiator->Responder:     0 packets 0 bytes

Responder->Initiator:     0 packets 0 bytes

 

Total sessions found: 1

# Use two external hosts at the IP address of 61.16.0.10 and 61.16.0.11 to request FTP services at the same time. On the device, verify that two NAT sessions are created, and FTP server 1 and FTP server 2 provide FTP services for the two hosts, respectively.

[Device] display nat session verbose

Initiator:

  Source      IP/port: 61.16.0.11/1024

  Destination IP/port: 61.16.0.1/21

  DS-Lite tunnel peer: -

  VPN instance/VLAN ID/Inline ID: -/-/-

  Protocol: TCP(6)

  Inbound interface: Ten-GigabitEthernet0/0/16

Responder:

  Source      IP/port: 10.110.3.1/21

  Destination IP/port: 61.16.0.11/1024

  DS-Lite tunnel peer: -

  VPN instance/VLAN ID/Inline ID: -/-/-

  Protocol: TCP(6)

  Inbound interface: Ten-GigabitEthernet0/0/15

State: TCP_ESTABLISHED

Application: FTP

Start time: 2014-07-08 14:11:41

Initiator->Responder:       0 packets   0 bytes

Responder->Initiator:       0 packets   0 bytes

 

Initiator:

  Source      IP/port: 61.16.0.10/1024

  Destination IP/port: 61.16.0.1/21

  DS-Lite tunnel peer: -

  VPN instance/VLAN ID/Inline ID: -/-/-

  Protocol: TCP(6)

  Inbound interface: Ten-GigabitEthernet0/0/16

Responder:

  Source      IP/port: 10.110.3.2/21

  Destination IP/port: 61.16.0.10/1024

  DS-Lite tunnel peer: -

  VPN instance/VLAN ID/Inline ID: -/-/-

  Protocol: TCP(6)

  Inbound interface: Ten-GigabitEthernet0/0/15

State: TCP_ESTABLISHED

Application: FTP

Start time: 2014-07-08 14:12:00

Initiator->Responder:        0 packets    0 bytes

Responder->Initiator:        0 packets    0 bytes

 

Total sessions found: 2

# Access an FTP server through 61.16.0.1 from PC 1. Verify that a NAT session is created.

[Device] display nat session verbose

Initiator:

  Source      IP/port: 10.110.1.10/1024

  Destination IP/port: 61.16.0.1/21

  DS-Lite tunnel peer: -

  VPN instance/VLAN ID/Inline ID: -/-/-

  Protocol: TCP(6)

  Inbound interface: Ten-GigabitEthernet0/0/15

Responder:

  Source      IP/port: 10.110.3.1/21

  Destination IP/port: 61.16.0.2/1025

  DS-Lite tunnel peer: -

  VPN instance/VLAN ID/Inline ID: -/-/-

  Protocol: TCP(6)

  Inbound interface: Ten-GigabitEthernet0/0/15

State: TCP_ESTABLISHED

Application: FTP

Start time: 2014-07-08 14:24:15

Initiator->Responder:       0 packets   0 bytes

Responder->Initiator:       0 packets   0 bytes

 

Total sessions found: 1

Configuration files

#

traffic classifier 1 operator and

 if-match acl 2001

#

traffic behavior 1

redirect local

#

qos policy 1

 classifier 1 behavior 1

#

interface Ten-GigabitEthernet0/0/15

 port link-mode route

 ip address 10.110.0.1 255.255.252.0

 qos apply policy 1 inbound

 nat hairpin enable

#

interface Ten-GigabitEthernet0/0/16

 port link-mode route

 ip address 61.16.0.1 255.255.255.0

 nat outbound 2000 address-group 0

 nat server protocol tcp global 61.16.0.1 21 inside server-group 0

#

acl basic 2000

 rule 0 permit source 10.110.0.0 0.0.1.255

 rule 5 permit source 10.110.2.0 0.0.0.255

#

acl basic 2001

 rule 0 permit source 10.110.0.0 0.0.1.255

 rule 5 permit source 10.110.2.0 0.0.0.255

#

nat address-group 0

 address 61.16.0.2 61.16.0.3

#

nat server-group 0

 inside ip 10.110.3.1 port 21

 inside ip 10.110.3.2 port 21

 inside ip 10.110.3.3 port 21

#

Related documentation

·     H3C CR16000-M1A Router NAT Configuration Guide

·     H3C CR16000-M1A Router NAT Command Reference