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

ME60 V800R010C10SPC500 Configuration Guide - IP Routing 01

This is ME60 V800R010C10SPC500 Configuration Guide - IP Routing
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).
Configuring AGGs to Load-Balance RNC-to-CSG Traffic

Configuring AGGs to Load-Balance RNC-to-CSG Traffic

This section describes how to configure access aggregation gateways (AGGs) to load-balance radio network controller (RNC)-to-cell site gateway (CSG) traffic. The load balancing configuration can improve network resource usage and reliability.

Usage Scenario

Figure 2-6 shows a typical networking for a Layer 2 virtual private network (L2VPN) accessing an L3VPN. An L2VPN connection is set up between each AGG and CSG, whereas a Border Gateway Protocol (BGP) VPNv4 peer relationship is set up between each AGG and RNC site gateway (RSG) on the L3VPN; L3VE sub-interfaces are configured on each AGG, each L3VE sub-interface is bound to one VPN instance, and the CSGs access the L3VPN through the L3VE sub-interfaces. To improve network resource usage and reliability, carriers expect that AGG1 transmits RNC-to-CSG1 and RNC-to-CSG2 traffic and that AGG2 transmits RNC-to-CSG3 and RNC-to-CSG4 traffic.

Figure 2-6 Networking for an L2VPN accessing an L3VPN
To meet the preceding requirements, perform the following steps on each AGG:
  1. Configure a cost for ARP Vlink direct routes and routes to the directly connected network segment on the L3VE sub-interface of the secondary pseudo wire (PW).
  2. Configure a static route to each NodeB and allow the static route to inherit the cost of the route to which the static route is iterated.
    NOTE:
    After this configuration is complete, each static route is iterated to a route to the directly connected network segment on an L3VE sub-interface, and the static route inherits the cost of the route to the directly connected network. Because no cost is configured for the directly connected network on the L3VE sub-interface of the primary PW, the default cost 0 takes effect on these routes, and static routes inherit the cost 0 after they are iterated to the route to the directly connected network.
  3. Import the static routes to the BGP routing table.
    NOTE:
    After a static route is imported to the BGP routing table, the cost is changed to the BGP route MED, but the value remains unchanged. The cost of the static route to one NodeB varies with the AGG, so does the BGP route MED.

After the preceding configurations are complete, each AGG advertises the route destined for each NodeB to its BGP VPNv4 peers (RSGs). The RSGs can receive two routes with the same prefix (destined for the same NodeB) and select an optimal route with a smaller MED value from the two routes. Consequently, RSGs select routes advertised by AGG1 as the primary routes to CSG1 and CSG2 and routes advertised by AGG2 as the primary routes to CSG3 and CSG4. The AGGs therefore load-balance RNC-to-CSG traffic.

Pre-configuration Tasks

Before configuring AGGs to load-balance RNC-to-CSG traffic, configure link-layer protocol parameters and IP addresses for interfaces and ensure that the link layer protocol on each interface is Up.

Procedure

  1. Configure a cost for routes to the directly connected network segment on the L3VE sub-interface of the secondary PW.
    1. Run interface virtual-ethernet interface-number

      A VE interface is created, and the VE interface view is displayed.

    2. Run ve-group ve-group-id l3-access

      The VE interface is configured as an L3VE interface that accesses a BGP/Multiprotocol Label Switching (MPLS) IP VPN and bound to a VE group.

      NOTE:
      The L2VPN can access the L3VPN only if the L2VE and L3VE interfaces are bound to the same VE group and reside on the same board.

    3. Run quit

      Return to the system view.

    4. Run interface virtual-ethernet interface-number.subinterface-number

      A VE sub-interface is created, and the VE sub-interface view is displayed.

    5. Run direct-route cost cost

      A cost is configured for routes to the directly connected network segment on the L3VE sub-interface of the secondary PW.

    6. Run quit

      Return to the system view.

  2. Run ip route-static vpn-instance vpn-source-name destination-address { mask | mask-length } nexthop-address [ preference preference | tag tag ] * inherit-cost [ description text ]

    A static route is configured for a specified VPN instance and allowed to inherit the cost of the route to which the static route is iterated.

    vpn-source-name specifies the VPN instance that is bound to the L3VE sub-interface, and nexthop-address specifies the destination address of the route to which the static route is iterated.

  3. Run either of the following commands:
    • To import static routes to the BGP routing table automatically, run the import-route static command.

    • To import static routes to the BGP routing table manually, run the network command.

    If you run the import-route static command, some unneeded static routes may be imported to the BGP routing table. To import a static route with a specific prefix and mask to the BGP routing table, run the network command.

  4. Run commit

    The configuration is committed.

Checking the Configurations

If an AGG's L3VE sub-interface is Up, run the display ip routing-table vpn-instance vpn-instance-name [ ip-address ] [ verbose ] command on the AGG. The command output shows that the cost of routes to the directly connected network segment on the L3VE sub-interface is the configured value.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 20589

Downloads: 15

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