No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NE40E V800R010C00 Feature Description - NAT and IPv6 Transition 01

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
NAT Load Balancing

NAT Load Balancing

Principles

With the limited public IP addresses and the ever-increasing private users and access bandwidth, a single VSUF-80/160 fails to meet service deployment requirements. Multiple service boards need to be used to provide more session and bandwidth resources.

Figure 3-16 shows the centralized NAT load balancing scenario. When multiple user packets are transmitted, the LPU uses the source IP address (SIP) in the packets to select a VSUF based on hash algorithm. The packets are then forwarded from the SFU to the selected VSUF for NAT implementation.

During centralized NAT load balancing, the multi-core CPU of a VSUF can share multiple global static address pools that are matched by different ACL. In addition, one NAT instance can be bound to multiple CPUs to ensure flexible extension for a single NAT user.

Figure 3-16  Centralized NAT load balancing

Figure 3-17 shows the distributed NAT load balancing scenario. The VSUF is deployed on a BRAS. When a user goes online, load balancing can be implemented by instance and CPU to associate with CGN for allocation of public IP addresses. All the NAT instances and CPUs on the same domain are calculated as a whole. The NAT instance and CPU with the lowest number of online users are selected for evenly load balancing. After a NAT instance and a CPU are selected, public IP addresses are obtained from this CPU, and both the forward traffic and reverse traffic are distributed to the CPU in the NAT instance for service processing.

During distributed NAT load balancing, multiple CPUs are bound to a NAT instance. When a BRAS is associated to allocate public IP addresses, multiple CPUs on the NAT instance are used for load balancing, and user traffic is allocated to these CPUs for NAT service processing.

Figure 3-17  Distributed NAT load balancing
Download
Updated: 2018-07-04

Document ID: EDOC1100027155

Views: 19725

Downloads: 67

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next