3Com Switch 8800 Advanced Software V5 Configuration Guide

992 CHAPTER 76: NAT CONFIGURATION
If an internal server belongs to an MPLS VPN instance, you should specify the
vpn-instance-name argument. With this argument not provided, the internal
server is considered belonging to a private network.
Configuring an Internal
Server
Follow the following steps to configure an internal server:
Configuring the
Binding
Introduction to Binding Through the use of the L3+NAT module on a switch, the NAT services can be
handled centrally and more efficiently thanks to the quick handling capability of
the hardware.
When a VLAN interface is configured with NAT, you can bind the VLAN interface
with the NAT virtual interface so that all the packets that pass through the VLAN
interface are redirected to the L3+NAT module for handling.
Before configuring the binding, you must configure the VLAN interface first.
Configuration Procedure Follow these steps to configure the binding:
c
CAUTION: Once bound to the NAT virtual interface, a VLAN interface can no
longer serve as the outbound interface of QoS redirection. This is because the
To do... Use the command... Remarks
Enter system view system-view -
Enter VLAN interface view interface interface-type
interface-number
-
Configure an internal server nat server [ vpn-instance
vpn-instance-name ] protocol
pro-type global
global-address [ global-port ]
inside host-address [
host-port ]
Use either command
nat server [ vpn-instance
vpn-instance-name ] protocol
pro-type global
global-address global-port1
global-port2 inside
host-address1 host-address2
host-port
To do... Use the command... Remarks
Enter system view system-view -
Enter NAT service interface
view
interface nat number -
Configure the binding nat binding interface
interface-type
interface-number
Required
Only VLAN interfaces can be
bound. A NAT service
interface can be bound with
multiple NAT-enabled
interfaces.