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 - Virtual Access 01

This is ME60 V800R010C10SPC500 Configuration Guide - Virtual 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).
Planning an Explicit Path for a vaTunnel

Planning an Explicit Path for a vaTunnel

This section describes how to plan an explicit path for a virtual access tunnel (vaTunnel). You can plan flexibly specify the vaTunnel's paths used by vaPWs to evenly balance traffic in the virtual access system and improve service quality.

Context

In a virtual access scenario, each user's service corresponds to a virtual access interface (that is, a vaPW). By default, different vaPWs in a virtual access system are carried by the same automatically created vaTunnel. If multiple paths exist between a master and AP, the vaTunnel's paths used by vaPWs cannot be flexibly specified in this mode. This mode may cause traffic in the virtual access system to become uneven, affecting service quality. To resolve the preceding issue, plan an explicit path for the vaTunnel. You can flexibly specify a service traffic path based on the actual network conditions to implement even load balancing and improve service quality.

Pre-configuration Tasks

Before planning an explicit path for a vaTunnel, establish a virtual access system.

Configuration Procedures

Figure 2-4 Flowchart for planning an explicit path for a vaTunnel

Configuring a Virtual Access Explicit Path

This section describes how to configure a virtual access explicit path.

Context

A virtual access explicit path consists of a series of nodes. Each node is identified by an index, and the nodes form a vector path, which is used to restrict path selection for the vaTunnel between a master and AP. Perform the following steps on a master.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run va-explicit-path path-name

    A virtual access explicit path is created, and the corresponding view is displayed.

  3. Run primary

    A primary path is created for the virtual access explicit path, and the corresponding view is displayed.

    The system automatically creates a primary path when creating a virtual access explicit path. To enter the primary path view, run the primary command. Running the command re-creates a primary path only after the original primary path is deleted.

  4. Run index index-number admin-ip admin-ip

    A node is created on the primary path, and the corresponding view is displayed.

  5. (Optional) Run out-interface interfacetype interfacenum

    An outbound interface is specified for the node on the virtual access explicit path.

    If you do not perform this step, the outbound interfaces of a node on a virtual access explicit path are all available outbound interfaces from the node to the next hop.

  6. Run quit

    Return to the primary path view.

    Repeat Step 4 through Step 6 to create multiple nodes on the primary path. The master determines the sequence of a node on the explicit path based on the index. For example, create three nodes with the indexes set to 10, 20, and 30 respectively on the primary path of the virtual access explicit path between a master and AP. Then the primary path from the master to the AP is node 10 -> node 20 -> node 30, and the primary path from the AP to the master is node 30 -> node 20 -> node 10.

  7. Run quit

    Return to the virtual access explicit path view.

  8. Run hot-standby

    A hot-standby path is created for the virtual access explicit path, and the corresponding view is displayed.

  9. Run index index-number admin-ip admin-ip

    A node is created on the hot-standby path, and the corresponding view is displayed.

  10. (Optional) Run out-interface interfacetype interfacenum

    An outbound interface is specified for the node on the virtual access explicit path.

    If you do not perform this step, the outbound interfaces of a node on a virtual access explicit path are all available outbound interfaces from the node to the next hop.

  11. Run quit

    Return to the hot-standby path view.

    Repeat Step 9 through Step 11 to create multiple nodes on the hot-standby path. The master determines the sequence of a node on the explicit path based on the index. For example, create three nodes with the indexes set to 10, 20, and 30 respectively on the hot-standby path of the virtual access explicit path between a master and AP. Then the hot-standby path from the master to the AP is node 10 -> node 20 -> node 30, and the hot-standby path from the AP to the master is node 30 -> node 20 -> node 10.

    NOTE:
    • The first node on a virtual access explicit path must be a master, and the path cannot contain any other masters.

    • If the primary and hot-standby commands have been run for a virtual access explicit path but no node is created, the master automatically calculates the primary and hot-standby paths based on bandwidth information. When calculating the hot-standby path, the master first searches for an available path that is different from the primary path. If such available path does not exist, the hot-standby path is the same as the primary path.

    • If a complete primary path has been configured for a virtual access explicit path but only the hot-standby command is run (no node is created), the master automatically calculates the hot-standby path based on bandwidth information. When calculating the hot-standby path, the master first searches for an available path that is different from the primary path. If such available path does not exist, the hot-standby path is the same as the primary path.

    • If a complete hot-standby path has been configured for a virtual access explicit path but only the primary command is run (no node is created), the master automatically calculates the primary path based on bandwidth information. When calculating the primary path, the master first searches for an available path that is different from the hot-standby path. If such available path does not exist, the primary path is the same as the hot-standby path.

  12. Run quit

    Return to the virtual access explicit path view.

  13. Run commit

    The configuration is committed.

Binding a Virtual Access Explicit Path to a vaTunnel

This section describes how to bind a virtual access explicit path to a vaTunnel.

Context

Planning an explicit path for a vaTunnel involves the following modes:

  • Planning an explicit path for an automatically created vaTunnel. In this mode, you must bind the virtual access explicit path to the vaTunnel in the AP view.

  • Planning an explicit path for a manually created vaTunnel. In this mode, you must manually create a vaTunnel and bind the virtual access explicit path to the vaTunnel.

Perform the following steps on a master.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run ap-id ap-id

    The AP view is displayed.

  3. (Optional) Run va-tunnel vaTunnel-name

    A vaTunnel is manually created between the master and AP, and the corresponding view is displayed.

    If you plan an explicit path for a manually created vaTunnel, perform this step. If you plan an explicit path for an automatically created vaTunnel, skip this step and perform the next steps in the AP view.

  4. Run bind va-explicit-path path-name

    A specified virtual access explicit path is bound to the vaTunnel.

    You can run this command in different views.

    • To enable the automatically created vaTunnel between the master and AP to comply with the explicit path's constraints, run this command in the AP view.

    • To enable a manually created vaTunnel to comply with the explicit path's constraints, run this command in the vaTunnel view.

  5. Run commit

    The configuration is committed.

Binding a Specified vaTunnel to a vaPW

This section describes how to bind a specified vaTunnel to a manually created vaPW.

Context

In a virtual access scenario, each user's service corresponds to a virtual access interface (that is, a vaPW). To enable service traffic to be forwarded based on a planned path, bind the vaTunnel to which an explicit path has been applied to a vaPW. When you plan an explicit path for an automatically created vaTunnel, the vaTunnel is automatically bound to a vaPW. When you plan an explicit path for a manually created vaTunnel, you must bind the vaTunnel to a vaPW.

Perform the following steps on a master.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run one of the following commands:

    • interface interface-type interface-number
    • interface eth-trunk trunk-id remote

    The virtual access interface view or virtual access Eth-Trunk interface view is displayed.

  3. Run virtual-access pw bind tunnel vaTunnel-name

    A specified vaTunnel is bound to a vaPW.

  4. Run commit

    The configuration is committed.

Checking the Configurations

After planning an explicit path for a virtual access tunnel (vaTunnel), check the configurations.

Prerequisites

An explicit path has been planned for a vaTunnel.

Procedure

  • Run the display va-explicit-path [ path-name ] [ verbose ] command on a master to check basic or detailed information about a virtual access explicit path.
  • Run the display virtual-access va-tunnel p2p [ source source-address destination destination-address ] [ tunnel-name tunnel-name ] command on a master to check the vaTunnel name (Tunnel Name) and virtual access explicit path name (Va Explicit Path).
  • Run the display virtual-access va-pw [ ap ap-id | state { up | down } | interface interface-type interface-number ] command on a master to check the name (Virtual-access tunnel) of the vaTunnel bound to the vaPW.
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059451

Views: 3750

Downloads: 18

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