R3204P16-HP Load Balancing Module Network Management Configuration Guide-6PW101
Table Of Contents
- Title page
- Contents
- Interface management configuration
- IP addressing configuration
- MAC address table configuration
- Layer 2 forwarding configuration
- Layer 2 forwarding overview
- Configuring general Layer 2 forwarding
- Configuring inline Layer 2 forwarding
- Configuring inter-VLAN Layer 2 forwarding
- Forward-type inline Layer 2 forwarding configuration example
- Blackhole-type inline Layer 2 forwarding configuration example
- Inter-VLAN Layer 2 forwarding configuration example
- VLAN configuration
- ARP configuration
- Gratuitous ARP configuration
- Proxy ARP configuration
- Layer 3 forwarding configuration
- NAT configuration
- Overview
- Configuring a NAT policy in the web interface
- Configuring NAT in the CLIs
- Configuration guidelines
- ALG configuration
- Static route configuration
- RIP configuration
- OSPF configuration
- BGP configuration
- Policy-based routing configuration
- Route displaying
- DNS configuration
- Overview
- Configuring DNS on the web interface
- Configuring DNS in the CLIs
- Troubleshooting IPv4 DNS configuration
- Support and other resources
- Index

101
To do… Use the command…
Remarks
Configure NAPT by associating an
ACL with an IP address pool on the
outbound interface for translating both
IP address and port number
nat outbound [ acl-number ] [ address-group
group-number [ track vrrp virtual-router-id ]
Required
Configuring an internal server
Introduction to internal server
To configure an internal server, you need to map an external IP address and port number to the internal
server. This is done through executing the nat server command on an interface.
Internal server configurations include external network information (external IP address global-address
and external port number global-port), internal network information (internal IP address local-address
and internal port number local-port), and internal server protocol type. According to different
internal/external network information configurations, internal servers can be classified into common
internal servers and load sharing internal servers.
Both internal servers and their public IP addresses can support MPLS VPN. If an internal server belongs
to an MPLS VPN instance, you also need to specify the vpn-instance-name argument. With this argument
not provided, the internal server is considered belonging to a normal private network.
NOTE:
The LB module does not support load sharing internal servers.
Configuring a common internal server
After mapping the private IP address/port number (local-address and local-port) of a common internal
server to a public IP address/port number (global-address and global-port), hosts in external networks
can access the server located in the private network.
Follow these steps to configure a common internal server:
To do… Use the command…
Remarks
Enter system view system-view —
Enter interface view interface interface-type interface-number —
Configure a common
internal server
nat server protocol pro-type global { global-address
current-interface | interface interface-type interface-number }
global-port1 global-port2 inside local-address1 local-address2
local-port [ track vrrp virtual-router-id ]
Required
NOTE:
• The LB module supports using the interface address as the public address of an internal server, which is
the Easy IP feature. If you want to specify an interface, the interface must be a loopback interface and
must already exist.
• If you confi
g
ure an internal server usin
g
Easy IP but do not confi
g
ure an IP address for the interface, the
internal server configuration does not take effect.