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

NE20E-S2 V800R010C10SPC500 Configuration Guide - IP Services 01

This is NE20E-S2 V800R010C10SPC500 Configuration Guide - IP Services
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).
Link Expansion

Link Expansion

Networking Requirements

As shown in Figure 10-4, four 10 G POS links connect R1 and R2. R1 and R2 establish an EBGP peer relationship through loopback interface addresses, and static routes are used.

To meet the service development needs, one 40 G POS link needs to be added between R1 and R2 so that the 40 G POS link can load-balance traffic with the other four 10 G POS links.

Figure 10-4 Link expansion

Solution 1: Deploy UCMP If It is Supported by the Software Ran by R1 and R2

UCMP can be deployed in two methods. Method 1 is recommended.

Method 1: Enable UCMP globally.

  1. Run the system-view command to enter the system view.
  2. Run the load-balance unequal-cost enable command to enable UCMP globally.

Method 2: Enable UCMP on the interfaces connected to the four 10 G POS links and the 40 G POS link. The interfaces need to be restarted.

  1. Run the system-view command to enter the system view.
  2. Run the interface interface-type interface-number command to enter the interface view.
  3. Run the load-balance unequal-cost enable command to enable UCMP on the interface.
  4. Run the restart command or run the shutdown and undo shutdown commands in order to restart the interface so that the UCMP configuration takes effect. Routes and FIB entries are refreshed only when you restart the interface after UCMP is enabled or disabled on the interface.
  5. Run the commit.

Solution 2: Configure Static Routes for Load Balancing

Configure four IP addresses on the local 40 G interface and four static routes to the remote 40 G interface.

  1. Run the system-view command to enter the system view.
  2. Run the interface interface-type interface-number command to enter the interface view.
  3. Run the ip address ip-address { mask | mask-length } command to configure an IP address for the interface.
  4. Run the ip address ip-address { mask | mask-length } [ sub ] command to configure three secondary IP addresses for the interface.
  5. Run the quit command to return to the system view.
  6. Run the ip route-static ip-address { mask | mask-length } nexthop-address command to configure four static routes to the remote 40 G loopback interface, with the four IP addresses of the remote 40 G loopback interface as the next hops.
  7. Run the commit.
interface Pos4/0/0
 undo shutdown
 ip address 168.1.0.34 255.255.255.252
 ip address 168.1.0.38 255.255.255.252 sub
 ip address 168.1.0.42 255.255.255.252 sub
 ip address 168.1.0.46 255.255.255.252 sub
#
 ip route-static 8.8.8.8 255.255.255.255 168.1.0.33
 ip route-static 8.8.8.8 255.255.255.255 168.1.0.37
 ip route-static 8.8.8.8 255.255.255.255 168.1.0.41
 ip route-static 8.8.8.8 255.255.255.255 168.1.0.45
NOTE:

By default, load balancing is enabled among static routes.

Solution two is limited by the maximum number of routes for load balancing that is supported by the software and the maximum number of IP addresses that can be configured on an interface.

For example, there are four 1 G interfaces before the expansion, and a 40 G interface is added for the expansion; the maximum number of static routes for load balancing is 32. Among the 32 static routes, the four 1 G interfaces occupy four, and 28 is left for the 40 G interface. Therefore, only 28 G traffic can be transmitted by the 40 G interface, and the bandwidth usage is low.

Solution 3: If the Four 10 G Interfaces Have Been Added to a Trunk Interface Before the Expansion, Configure Different Weights for the Member Interfaces of the Trunk Interface for Load Balancing

  1. Run the interface interface-type interface-number command to enter the interface view.
  2. Run the link-protocol hdlc command to set the link layer protocol to HDLC. The link layer protocol of the interface to be added to an IP-Trunk interface must be HDLC.
  3. Run the ip-trunk trunk-id command to add the 40 G interface to the IP-Trunk interface.
  4. Run the distribute-weight weight-value command to configure a weight for each member interface. In this instance, set the weight of the 40 G interface to 4, and the other member interface use the default weight 1.

    For an IP-Trunk interface, the total load balancing weight of all member interfaces cannot exceed 64.

    A Trunk (IP-Trunk or Eth-Trunk) interface performs load balancing among member links based on the weights of the links. The greater the weight of a Trunk member interface, the heavier the load carried by the member interface.

  5. Run the commit.

Follow-up Procedure

Run the save command to save the current configuration to the configuration file when a set of configuration is finished and the expected functions have been achieved.

Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055376

Views: 15613

Downloads: 33

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