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

This is NE20E-S2 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 the EVC Model to Carry L2VPN Services

Configuring the EVC Model to Carry L2VPN Services

This section describes how to use the EVC model to carry L2VPN services to reduce enterprise costs.

Usage Scenario

The traditional service model supported by the NE20E uses either VPLS or VLL to access a carrier network. If VPLS is used, common sub-interfaces (VLAN type), dot1q VLAN tag termination sub-interfaces, or QinQ VLAN tag termination sub-interfaces must be created on the user-side interfaces of PEs and bound to different VSIs. If Layer 2 devices use different access modes on a network, network planning and management are complex and difficult. To resolve this issue and reduce enterprise costs, configure the EVC model to carry Layer 2 services.

Pre-configuration Tasks

Before configuring the EVC model to carry L2VPN services, complete the following tasks:

  1. Configure a routing protocol on the PEs so that they can communicate at the network layer.

  2. Configure basic Multiprotocol Label Switching (MPLS) functions, enable MPLS Label Distribution Protocol (LDP), and establish LDP Label Switched Paths (LSPs) on the PEs.

  3. Enable MPLS L2VPN on the PEs globally.

  4. Establish the EVC model. For details, see Establishing the EVC Model.

Configuration Procedures

Perform one or more of the following configurations as required.

Configuring the EVC Model to Carry VPLS Services

This section describes how to use the EVC model to carry Virtual Private LAN Service (VPLS) services to reduce enterprise costs.

Context

In the traditional service model supported by the NE20E, common sub-interfaces (VLAN type), dot1q VLAN tag termination sub-interfaces, or QinQ VLAN tag termination sub-interfaces are created on the user-side interfaces of PEs. These sub-interfaces are bound to different Virtual Switching Instances (VSIs) on the carrier network to isolate services in different departments of an enterprise. If the enterprise sets up another department, the enterprise must lease another VSI from the carrier to isolate the departments, which increases costs.

To allow the enterprise to dynamically adjust its departments and reduce costs, deploy the Ethernet Virtual Connection (EVC) model on the PEs to allow multiple Bridge Domains (BDs) to access the same VSI and also to be isolated from each other.

A BD can access a VPLS network in either of the following modes:
  • VSI pipe service mode

    A VSI functions as a network-side pipe, and BDs function as service instances at the access layer. A VSI can carry service traffic from multiple BDs. The Pseudo Wires (PWs) must work in tag mode. The BDs must use VLAN IDs as service delimiters.

    When a packet enters a PW from a BD, the ingress PE adds the BD ID to the packet as the outer tag (PW tag). When the packet leaves the PW, the egress PE searches for a VSI based on the VC label and searches for a BD based on the outer tag.

  • VSI-exclusive service mode

    Each VSI provides access services for only one BD, and the BD exclusively consumes the VSI resources. The services in the VSI can be planned as needed. The PWs can work in either raw mode (with the VSI encapsulation type being Ethernet) or tagged mode (with the VSI encapsulation type being VLAN). The ingress PE adds a PW tag to packets that enter a PW only after the PW tag has been configured and the PW works in tagged mode. The egress PE does not verify the PW tag of packets that leave the PW. If the PW works in raw mode, the egress PE directly forwards the packets to the corresponding BD. If the PW works in tagged mode, the egress PE removes the outer tag before forwarding the packets to the corresponding BD.

Precautions

On the network shown in Figure 10-6, different user networks connect to PE1 through the same CE, and a BD is bound to a VSI for VPLS access. However, due to VPLS split horizon, the user-side interface on PE1 will not forward packets it receives, and therefore users in the same VSI cannot communicate. To allow users to communicate, run the local-switch enable command on the user-side Layer 2 sub-interface on PE1 to enable local switching for the Layer 2 sub-interface.

Figure 10-6 Local switching for a Layer 2 sub-interface

Pre-configuration Tasks

Before configuring EVC to carry VPLS services, complete the following tasks:
  • Create VSIs. (VSI IDs are used to identify VSIs and used for PW signaling negotiation.)
    NOTE:
    The VSIs for BDs must be configured using the vsi bd-mode command.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bridge-domain bd-id

    The BD view is displayed.

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

    The BD is bound to a VSI.

    NOTE:
    If the VSI pipe service mode is used, multiple BDs can access the same VSI. In this case, you must specify a PW tag so that the peer BD can receive packets from the BD with the same PW tag.

Follow-up Procedure

In a VPLS over EVC scenario, each BD functions as an access-side service instance and EVC Layer 2 sub-interfaces join each BD as AC interfaces. The status of a BD is determined by the status of all EVC Layer 2 sub-interfaces in the BD and the VSI. A BD goes Down only when all its EVC Layer 2 sub-interfaces and the VSI are both Down. The EVC Layer 2 sub-interface status is independent of the VSI status. In a VPWS accessing VPLS scenario where a VSI VC is configured on the local end and a VPWS VC is configured on the remote end, if all EVC Layer 2 sub-interfaces in the BD are Down, the remote VPWS VC cannot quickly detect the fault. As a result, traffic is interrupted. To solve this problem, run the response-ac-state command, so that the VSI can learn the AC interface Down event immediately after all EVC Layer 2 sub-interfaces in a BD go Down. Then, the VSI will set the PW status to Down.
  1. Run systerm-view

    The system view is displayed.

  2. Run vsi vsi-name

    The VSI view is displayed.

  3. Run response-ac-state

    The VSI is enabled to learn the AC interface Down event when all EVC Layer 2 sub-interfaces in a BD are Down.

  4. Run commit

    The configuration is committed.

A BD goes Down after all EVC Layer 2 sub-interfaces leave the BD. By default, a PE sends MAC Withdraw messages with the 0x404 TLV type to all peers when a BD goes Down. After the interface-status-change mac-withdraw enable command is run, a PE sends MAC Withdraw messages with the 0x406 TLV type to all its peers each time an EVC Layer 2 sub-interface leaves the BD. As a result, when a BD goes Down, the PE will send MAC Withdraw messages with the 0x404 TLV type twice. To solve this problem, perform the following steps:
  1. Run systerm-view

    The system view is displayed.

  2. Run vsi vsi-name

    The VSI view is displayed.

  3. Run mac-withdraw bd-status down disable

    The PE is configured not to send MAC Withdraw messages with the 0x404 TLV type to all its peers when a BD goes Down.

  4. Run commit

    The configuration is committed.

When the status of an EVC Layer 2 sub-interface changes, a PE sends MAC Withdraw messages that do not carry the PW tag to all its peers. When a peer receives this message, it clears MAC addresses in the VSI based on the message, causing the MAC addresses of other BDs to be deleted incorrectly. To solve this problem, perform the following steps:
  1. Run systerm-view

    The system view is displayed.

  2. Run interface interface-type interface-number.subnum mode l2

    The EVC Layer 2 sub-interface view is displayed.

  3. Run interface-status-change [ up | down ] mac-withdraw enable

    The PE is enabled to send a MAC Withdraw message to all its peers when the EVC Layer 2 sub-interface status changes.

  4. Run quit

    Return to the system view.

  5. Run vsi vsi-name

    The BD VSI view is displayed.

  6. Run mac-withdraw enable

    MAC Withdraw is enabled.

  7. Run mac-withdraw bd pw-tag enable

    The PE is configured to send MAC Withdraw messages that carry the PW tag to its peers when a BD goes Down.

  8. Run commit

    The configuration is committed.

Configuring the EVC Model to Carry VPWS Services

This section describes how to use the EVC model to carry VPWS services. This implementation can facilitate network planning and management, thereby cutting down enterprise costs.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number.subnum mode l2

    The EVC Layer 2 sub-interface view is displayed.

  3. Run mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ tunnel-policy policy-name | [ control-word | no-control-word ] | [ raw | tagged ] | access-port | ignore-standby-state ] *

    A VPWS connection is created.

    NOTE:
    • The IDs of VCs using the same encapsulation type must be unique.

    • The raw, tagged, and access-port parameters can be specified in this command only when this command is applied to Ethernet links. The access-port parameter applies only to Ethernet main interfaces.

    • The default tunnel policy uses LDP LSPs for VPWS PWs. If you want to use other types of tunnels for a VPWS PW, configure the tunnel-policy policy-name parameter for a VPWS PW to reference the corresponding tunnel policy.

  4. Run commit

    The configuration is committed.

Checking the Configurations

After configuring the EVC model to carry L2VPN services, check the configurations.

Prerequisites

The EVC model has been configured to carry L2VPN services.

Procedure

  • Run the display vsi [ name vsi-name ] [ verbose ] command to check detailed VSI information.
  • Run the display mpls l2vc brief command to check brief VPWS connection information.

Checking the Configurations

Run the display vsi command. The following uses the command output on PE1 as an example. The command output shows that the VSI is Up and bridge domain 10 is accessed.

<HUAWEI> display vsi name ldp1 verbose
 ***VSI Name               : ldp1
    Work Mode              : bd-mode
    Administrator VSI      : no
    Isolate Spoken         : disable
    VSI Index              : 2
    PW Signaling           : ldp
    Member Discovery Style : --
    Bridge-domain Mode     : enable
    PW MAC Learn Style     : qualify
    Encapsulation Type     : ethernet
    MTU                    : 1500
    Diffserv Mode          : uniform
    Service Class          : --
    Color                  : --
    DomainId               : 255
    Domain Name            : 
    Ignore AcState         : disable
    P2P VSI                : disable
    Create Time            : 0 days, 0 hours, 1 minutes, 56 seconds
    VSI State              : up
    Resource Status        : --

    VSI ID                 : 2
   *Peer Router ID         : 2.2.2.9
    primary or secondary   : primary
    ignore-standby-state   : no
    VC Label               : 32830
    Peer Type              : dynamic
    Session                : up
    Tunnel ID              : 0x0000000001004c4b42
    Broadcast Tunnel ID    : --
    Broad BackupTunnel ID  : --
    CKey                   : 33
    NKey                   : 1409286261
    Stp Enable             : 0
    PwIndex                : 33
    Control Word           : disable

    Access Bridge-domain   : Bridge-domain 10 , PW tag 10 
    State                  : up 
    Last Up Time           : 2016/09/24 18:15:29
    Total Up Time          : 0 days, 16 hours, 51 minutes, 0 second

    Access Bridge-domain   : Bridge-domain 20 , PW tag 20 
    Last Up Time           : 2016/09/25 11:09:17
    Total Up Time          : 0 days, 0 hours, 0 minutes, 11 seconds

  **PW Information:

   *Peer Ip Address        : 2.2.2.9
    PW State               : up
    Local VC Label         : 32830
    Remote VC Label        : 32831
    Remote Control Word    : disable
    PW Type                : label
    Local  VCCV            : alert lsp-ping 
    Remote VCCV            : alert lsp-ping 
    Tunnel ID              : 0x0000000001004c4b42
    Broadcast Tunnel ID    : --
    Broad BackupTunnel ID  : --
    Ckey                   : 33
    Nkey                   : 1409286261
    Main PW Token          : 0x0
    Slave PW Token         : 0x0
    Tnl Type               : ldp
    OutInterface           :
    Backup OutInterface    : --
    Stp Enable             : 0
    Mac Flapping           : 0
    PW Last Up Time        : 2016/09/24 18:17:53
    PW Total Up Time       : 0 days, 0 hours, 0 minutes, 17 seconds

Run the display mpls l2vc brief command. The command output shows that one VC has been set up and is in the Up state.

<HUAWEI> display mpls l2vc brief
 Total LDP VC : 1     1 up       0 down

 *Client Interface  : GigabitEthernet0/1/1.1
  Administrator PW  : no
  AC status         : up
  VC state          : up
  Label state       : 0
  Token state       : 0
  VC ID             : 100
  VC Type           : Ethernet
  session state     : up
  Destination       : 2.2.2.9
  link state        : up
Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055378

Views: 16645

Downloads: 35

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