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-M2 V800R010C10SPC500 Feature Description - User Access 01

This is NE40E-M2 V800R010C10SPC500 Feature Description - User Access
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).
Load Balancing

Load Balancing

Load Balancing Between Equipment

User session information of multiple NE40Es is backed up on the NE40E. When a master device is faulty, user services are switched to the slave device.

As shown in Figure 9-15, the NE40E in the middle serves as the slave device, and the NE40Es on both sides serve as the master devices. Under normal circumstances, users go online using the master devices. When master devices or the links of master devices are faulty, the slave device takes over user services.

Figure 9-15 Deployment of equipment-level load balancing

In the topology shown in Figure 9-15, focus on the VLAN planning, and make sure that the two NE40Es can be accessed by users simultaneously.

Load Balancing Between Links

As shown in Figure 9-16, when the NE40E needs to access multiple aggregation switches or links, load balancing can be applied according to the granularity of links. Two NE40Es can serve as the master and slave devices to protect each other. Two NE40Es can also be accessed by users simultaneously.

Figure 9-16 Deployment of link-level load balancing

Load Balancing Between VLANs

As shown in Figure 9-17, if you need to enable access links to work concurrently to save link resources, deploy load balancing at the VLAN level. Two VRRP groups need to be deployed. One VRRP group allows some VLAN users to go online from the NE40E on the left side, and the other VRRP group allows other VLAN users to go online from the NE40E on the right side.

Figure 9-17 Deployment of VLAN-level load balancing

Load Balancing Based on Odd and Even MAC Addresses

This section describes load balancing based on the odd and even media access control (MAC) addresses carried in user packets.

Figure 9-18 Load balancing based on odd and even MAC addresses

As shown in Figure 9-18, two Virtual Router Redundancy Protocol (VRRP) backup groups are deployed on the access side. One VRRP backup group uses NE40E 1 as the master and NE40E 2 as the backup, and the other uses NE40E 2 as the master and NE40E 1 as the backup.

In multi-device backup scenarios, configure load balancing based on odd and even MAC addresses to enable the master NE40E to forward only user packets carrying odd or even MAC addresses.

To determine the forwarding path of uplink traffic and prevent packet disorder, the master and backup NE40Es in the same virtual local area network (VLAN) must use different virtual MAC addresses to establish sessions with hosts.

Download
Updated: 2019-01-02

Document ID: EDOC1100058415

Views: 12088

Downloads: 8

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