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 - LAN Access and MAN Access 01

This is ME60 V800R010C10SPC500 Configuration Guide - LAN Access and MAN 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).
Configuring BRAS Access Through a PW and a VXLAN Tunnel

Configuring BRAS Access Through a PW and a VXLAN Tunnel

As virtual networks develop, if device resources become insufficient for processing access user traffic, traffic can be load balanced to virtual BRASs in data centers. Specifically, a device can establish a VXLAN tunnel with a virtual BRAS for user access.

Usage Scenario

On the network shown in Figure 17-16, a VPLS network and a VXLAN network intersect at Device 2 and Device 4 that back up each other. VRRP is configured to implement device and link reliability. Users can access the BRAS through a PW and a VXLAN tunnel.

Figure 17-16 Configuring BRAS access through a PW and a VXLAN tunnel

Pre-configuration Tasks

Before configuring BRAS access through a PW and a VXLAN tunnel, complete the following tasks:
  • The VPLS network has been created.
  • The network is reachable at Layer 3.

Perform the following steps on devices at the intersection of the VPLS and VXLAN networks:

Procedure

  1. Configure an ingress replication list.
    1. Run system-view

      The system view is displayed.

    1. Run interface nve nve-number

      An NVE interface is created, and the NVE interface view is displayed.

    2. Run source ip-address

      An IP address is configured for the source VTEP.

      Either a physical interface's IP address or loopback interface address can be specified for a source VTEP. Using the loopback interface address as the source VTEP's IP address is recommended.

    3. Run vni vni-id head-end peer-list ip-address &<1-10>

      An ingress replication list is configured.

      NOTE:

      BUM packets can only be transmitted in ingress replication mode. When a Huawei device interworks with a non-Huawei device, the non-Huawei device must also have the ingress replication mode configured before they can establish a VXLAN tunnel.

    4. Run commit

      The configuration is committed.

  2. Configure a BD and bind it to a VSI.
    1. Run system-view

      The system view is displayed.

    2. Run bridge-domain bd-id

      A BD is created, and the BD view is displayed.

    3. Run vxlan vni vni-id split-horizon-mode

      A VNI is created and bound to a BD, and split horizon is configured for packet forwarding.

    4. Run l2 binding vsi vsi-name [ pw-tag pw-tag-value ]

      The BD is bound to a VSI.

    5. Run commit

      The configuration is committed.

  3. Configure a VRRP backup group to track interface status and create an mVRRP backup group.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number.subinterface-number

      The sub-interface view is displayed.

    3. Run vlan-type dot1q vlan-id

      VLAN encapsulation and a VLAN are configured for the sub-interface.

    4. Run ip address ip-address { mask | mask-length }

      An IP address is configured for the sub-interface.

    5. Run vrrp vrid virtual-router-id [ virtual-ip virtual-address ]

      A VRRP backup group is configured.

    6. Run vrrp vrid track virtual-router-id interface interface-type interface-number reduced value-reduced

      The VRRP backup group is configured to track an interface.

    7. Run admin-vrrp vrid virtual-router-id [ ignore-if-down ]

      An mVRRP backup group is created.

    8. Run commit

      The configuration is committed.

  4. Associate VRRP with the virtual VTEP's route priority.
    1. Run interface loopback loopback-number

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

    2. Run ip address ip-address { mask | mask-length }

      An IP address is configured for the loopback interface.

      The IP address configured for a loopback interface must be the one configured for the source VTEP.

    3. Run direct-route track vrrp vrrp interface interface-type interface-number vrid virtual-router-id degrade-cost cost-value

      VRRP is associated with the virtual VTEP's route priority.

      vrid virtual-router-id must be an mVRRP backup group that has been created.

    4. Run commit

      The configuration is committed.

  5. Bind a service PW in a service VSI to an mVRRP backup group.
    1. Run system-view

      The system view is displayed.

    2. Run vsi vsi-name [ static | auto ] bd-mode

      A VSI in BD mode is created.

    3. Run pwsignal ldp

      The VSI-LDP view is displayed.

    4. Run vsi-id vsi-id

      An ID is configured for the VSI.

    5. Run peer peer-address

      A peer is configured for the VSI.

    6. Run peer peer-address [ negotiation-vc-id vc-id ] track admin-vrrp interface interface-type interface-number vrid virtual-router-id pw-redundancy backup-block-all

      A service PW in a service VSI is bound to an mVRRP backup group.

    7. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059440

Views: 29925

Downloads: 23

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