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 an IPv4 Direct Route to Respond to L3VE Interface Status Changes After a Delay

Configuring an IPv4 Direct Route to Respond to L3VE Interface Status Changes After a Delay

This section describes how to configure an IPv4 direct route to respond to Layer 3 virtual Ethernet (L3VE) interface status changes after a delay on an IP radio access network (RAN). During traffic switchback after the master AGG recovers, this configuration can reduce traffic loss and improve network reliability.

Usage Scenario

On the network shown in Figure 2-2, a Layer 2 virtual private network (VPN) connection is set up between each AGG and the CSG through L2VE interfaces, and Border Gateway Protocol (BGP) VPNv4 peer relationships are set up between the AGGs and RSGs on an L3VPN. L3VE interfaces are configured on the AGGs, and VPN instances are bound to the L3VE interfaces so that the CSG can access the L3VPN. BGP is configured on the AGGs to import IPv4 direct routes between the CSG and AGGs. The AGGs convert these IPv4 direct routes to BGP VPNv4 routes before advertising them to the RSGs.

Figure 2-2 Networking for the IPv4 direct route responding to L3VE interface status changes after a delay

AGG1 functions as the master device. In most cases, the RSGs select routes advertised by AGG1, and traffic travels along Link A. If AGG1 or the CSG-AGG1 link fails, traffic switches over to Link B. After AGG1 or the CSG-AGG1 link recovers, the L3VE interface on AGG1 goes from Down to Up, and AGG1 immediately generates an IPv4 direct route destined for the CSG and advertises the route to the RSGs. Downstream traffic then switches over to Link A. However, AGG1 has not learned the MAC address of the NodeB yet. As a result, downstream traffic is lost.

After you configure the IPv4 direct route to respond to L3VE interface status changes after a delay, the cost of the IPv4 direct route between the CSG and AGG1 is modified to the configured cost (greater than 0) when the L3VE interface on AGG1 goes from Down to Up. In this case, the RSG does not select the IPv4 direct routes, and downstream traffic still travels along Link B. After the configured delay expires, the cost of the IPv4 direct route to the CSG restores to the default value 0. Then, the RSG selects the IPv4 direct routes, and downstream traffic is switched over to Link A. By this time, AGG1 has learned the MAC address of the NodeB, and downstream traffic loss is reduced.

Pre-configuration Tasks

Before you configure an IPv4 direct route to respond to L3VE interface status changes after a delay, configure link-layer protocol parameters and IP addresses for interfaces and ensure that the link layer protocol of each interface is Up.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface virtual-ethernet interface-number

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

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

    The VE interface is configured as an L3VE interface 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.

  4. Run quit

    Return to the system view.

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

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

  6. Run direct-route degrade-delay delay-time degrade-cost cost

    The IPv4 direct route is configured to respond to L3VE interface status changes after a delay.

    After you run the direct-route degrade-delay command on an L3VE interface, and the L3VE interface goes from Down to Up, the cost of the L3VE interface's IPv4 direct route to the CSG is modified to the configured cost. After the configured delay-time expires, the IPv4 direct route cost is restored to the default value 0.

    NOTE:

    The direct-route track pw-state, direct-route degrade-delay, and direct-route track vrrp commands cannot all be configured on one L3VE interface. If you run the three commands on one L3VE interface, the latest configuration overrides the previous ones.

  7. Run commit

    The configuration is committed.

Checking the Configurations

If an AGG's L3VE interface goes from Down to 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 the L3VE interface's IPv4 direct route to the CSG is the configured cost. After the configured delay-time expires, 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 the IPv4 direct route to the L3VE interface is the default value 0.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059437

Views: 20931

Downloads: 15

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