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 an L2VPN Service on a QinQ Stacking Sub-interface

Configuring an L2VPN Service on a QinQ Stacking Sub-interface

To enable a physical interface to provide multiple users with access to an L2VPN, configure a QinQ stacking sub-interface and bind it to a VSI or L2VC.

Applicable Environment

In early stages, QinQ was primarily deployed on CEs on Layer 2 networks. VLAN tags are added to packets using VLAN stacking and services are forwarded on Layer 2 networks based on the outer VLAN tags. QinQ stacking sub-interfaces are configured on PEs to identify user VLANs and add outer VLAN tags to Layer 2 frames.

This implementation, however, faces a problem that one physical interface cannot provide L2VPN access to multiple users. To address this problem, you can configure a QinQ stacking sub-interface and bind it to a VSI or L2VC to provide L2VPN access to multiple users.

NOTE:

QinQ stacking sub-interfaces cannot forward packets at Layer 2 and must be deployed with the L2VPN.

  • VPWS

    VPWS is a point-to-point virtual leased line technology and supports almost all link layer protocols. VPWS simulates the traditional leased line services on IP networks and provides asymmetric and low-cost digital data network (DDN) services. To users on both ends of the leased line, VPWS is similar to the traditional leased line services.

  • VPLS

    VPLS makes a multipoint-to-multipoint VPN networking possible. With VPLS, the carrier can transmit Ethernet-based multipoint-to-multipoint services for users over an MPLS backbone network.

NOTE:
After receiving a user-destined Layer 2 multicast packet, a QinQ stacking or QinQ mapping sub-interface that connects to a VPLS network removes the outer tag from the packet, adds the learned inner and outer tags to the packet, and then forwards the packet to a downstream device.

Pre-configuration Task

Before you configure the QinQ stacking sub-interface provide L2VPN access, plan user VLANs properly so that packets received by QinQ stacking sub-interfaces carry one VLAN tag.

Configuration Procedures

Figure 9-13 Flowchart for configuring a QinQ stacking sub-interface to provide L2VPN access

Configuring a QinQ Stacking Sub-interface

This section describes how to configure a QinQ stacking sub-interface on a provider edge (PE) to provide Layer 2 virtual private network (L2VPN) access so that the inner virtual local area network (VLAN) tags of user packets are transparently transmitted over a carrier network.

Context

After you enable QinQ stacking on an Ethernet sub-interface:
  • When the QinQ stacking sub-interface receives a packet, the sub-interface checks whether the VLAN ID or VLAN range in the VLAN tag of the packet matches the VLAN ID or VLAN range specified using the qinq stacking vid command. If they are consistent, the sub-interface adds an outer VLAN tag to the packet.

    • If the packet carries one VLAN tag and the VLAN ID in the tag is in the VLAN range specified by low-ce-vid [ to high-ce-vid ] in the qinq stacking vid command, the sub-interface adds an outer VLAN tag to the packet. If the VLAN ID in the VLAN tag is not in the specified VLAN range, the sub-interface discards the packet.
    • If the packet carries two VLAN tags and the VLAN ID in the outer tag is in the VLAN range specified by low-ce-vid [ to high-ce-vid ] in the qinq stacking vid command, the sub-interface adds another outer VLAN tag to the packet and forwards the packet. In this case, the inner VLAN tag is transmitted transparently. If the VLAN ID in the outer tag is not in the specified VLAN range, the sub-interface discards the packet.
    • If the packet does not carry any VLAN tag, the sub-interface directly discards the packet.
  • When the QinQ stacking sub-interface sends a packet, the sub-interface strips the outer VLAN tag of the packet.
NOTE:
After you run the qinq stacking vid command on an Ethernet sub-interface:
  • If you do not run the qinq stacking pe-vid command to specify an outer VLAN tag to be added to packets, the Ethernet sub-interface will add a default outer VLAN tag to received packets.

    The default outer VLAN tag is assigned by the device and cannot be modified.

  • If you run the qinq stacking pe-vid command to specify an outer VLAN tag to be added to packets, the Ethernet sub-interface will add the specified outer VLAN tag to received packets.

    Before you run the qinq stacking pe-vid pe-vid command on an Ethernet sub-interface, you must run the qinq stacking vid command on the sub-interface. Otherwise, the QinQ stacking function does not take effect.

Procedure

  1. Run system-view

    The system view is displayed.

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

    The view of an Ethernet sub-interface at the user-side of a PE is displayed.

  3. (Optional) Create a user VLAN group.

    1. Run vlan-group group-id

      A user VLAN group is created.

    2. Run group mode { single | multiple }

      The working mode of the VLAN group is configured.

      • single: A VLAN group is considered as a user. This means that you cannot collect statistics about QinQ packets or deploy quality of service (QoS) policies based on a VLAN or a VLAN range.
      • multiple: VLANs and VLAN ranges in a VLAN group are considered as different users. This means that you can collect statistics about QinQ packets or deploy QoS policies based on a VLAN or VLAN range to implement refined management.
    3. Run quit

      Return to the view of the Ethernet sub-interface at the user-side of the PE.

    NOTE:

    Configuring a VLAN group allows you to achieve the following purposes:

    • Deploy QoS policies based on services or users so that higher priority service traffic is preferentially forwarded, improving user experience.
    • View statistics about QinQ packets to check whether a device is functioning properly.

  4. Run either of the following commands:

    • To configure a QinQ stacking sub-interface, run the qinq stacking vid low-ce-vid [ to high-ce-vid ] [ vlan-group group-id ] command.

    • To configure a QinQ stacking sub-interface and a matching policy for the sub-interface based on VLAN ID+8021.p value/DSCP value/EthType, run the qinq stacking vid low-ce-vid [ to high-ce-vid ] { 8021p { 8021p-value1 [ to 8021p-value2 ] } &<1-8> | dscp { dscp-value1 [ to dscp-value2 ] } &<1-10> | eth-type eth-type-value | default } [ vlan-group group-id ] command.
    NOTE:
    • If you have run the vlan-group command to configure a VLAN group on the sub-interface, specify the vlan-group in the preceding commands.

    • If you have not run the vlan-group command to configure a VLAN group on the sub-interface, do not specify the vlan-group in the preceding commands.

    • If you configure QinQ stacking on Ethernet sub-interfaces on an interface, specify a unique ce-vid value for each sub-interface.

    • If you do not configure a matching policy, the QinQ stacking sub-interface adds an outer VLAN tag to packets based on the specified VLAN range. If you configure a matching policy, the QinQ stacking sub-interface adds an outer VLAN tag to packets based on the specified VLAN ID+802.1p value/DSCP value/EthType.

  5. (Optional) Run qinq stacking pe-vid pe-vid The QinQ stacking sub-interface is enabled to add a specified outer VLAN tag to received packets.

    If you skip this step, the QinQ stacking sub-interface will add a system-assigned outer VLAN tag to received packets.

  6. Run commit

    The configuration is committed.

(Optional) Configuring a PW-tag Action

This section describes how to configure a PW-tag action so that a PE changes the P-Tag of packets to be forwarded over a PW in tagged mode to ensure normal communication with non-Huawei devices on an L2VPN network.

Context

As shown in Figure 9-14, CE1 and CE2 are connected to the L2VPN network through PE sub-interfaces, PE1 and CE1 are Huawei devices, and PE2 and CE2 are non-Huawei devices.

When a PE transmits multiple services over one PW, the PE adds different P-Tags to packets of different services to isolate the packets on the L2VPN network. When the packets reach the sub-interfaces of another PE on the other end of the PW, each sub-interface accepts only those packets carrying the same P-Tag as that specified on the sub-interface.

However, because the P-Tags on PE1 and PE2 may be different, PE1 cannot communicate with PE2, and users from user networks connected to CE1 and CE2 cannot communicate with each other.

Figure 9-14 Networking for accessing an L2VPN through sub-interfaces

To address the problem, configure a PW-tag action on the user-side sub-interface of PE1. The PE1 sub-interface changes the P-Tag of packets to that on PE2 before forwarding the packets over the PW. This allows PE1 to communicate with PE2.

Table 9-14 provides the default P-Tag values and the P-Tag values after the PW-tag action.

Table 9-14 P-Tag values

Sub-Interface Type

Default P-Tag Value

P-Tag Value After the PW-Tag Action

Dot1q sub-interface

VLAN ID in a packet

New VLAN ID

Sub-interface for dot1q VLAN tag termination

Sub-interface for QinQ VLAN tag termination

Outer VLAN ID in a packet

QinQ stacking sub-interface

Minimum VLAN ID in the VLAN ID range specified on the sub-interface

QinQ mapping sub-interface

Fixed VLAN ID in the system

Procedure

  1. Run system-view

    The system view is displayed.

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

    The view of a user-side sub-interface on a PE is displayed.

  3. Run pw-tag { vlan-id | inner-vlan | outer-vlan } [ 8021p { 8021p-value | inner-vlan | outer-vlan } ]

    A PW-tag action is configured so that the sub-interface changes the P-Tag of packets before forwarding the packets over the PW in tagged mode.

  4. Run commit

    The configuration is committed.

Configuring an L2VPN Service

Layer 2 virtual private networks (L2VPNs) include Virtual Private Wire Service (VPWS) and Virtual Private LAN Service (VPLS) networks. After you configure QinQ stacking sub-interfaces, bind these sub-interfaces to a Virtual Switching Instance (VSI) or VPWS instance to provide L2VPN access for users.

Context

For detailed information, see the chapters "VPWS Configuration" and "VPLS Configuration" in the HUAWEI ME60 Configuration Guide - VPN.

If you use QinQ stacking sub-interfaces to provide VPWS access, the number of VLANs on both ends of the VPWS must be the same.

Perform the following steps on the device on which an L2VPN is to be configured.

Procedure

  1. Run system-view

    The system view is displayed.

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

    The view of the QinQ stacking sub-interface is displayed.

  3. Configure a QinQ stacking sub-interface to provide L2VPN access, as shown in Table 9-15.

    Table 9-15 QinQ stacking sub-interfaces providing L2VPN access

    Service Type

    QinQ Stacking Sub-interface Configuration

    Description

    VPWS

    Run the 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 ] * command to create a VPWS connection.

    • ip-interworking must be configured when Huawei devices interwork with each other over heterogeneous media.
    • ip-layer2 must be configured when Huawei devices interwork with non-Huawei devices over heterogeneous media.

    VPLS

    Run the l2 binding vsi vsi-name command to bind a VLAN tag termination sub-interface to a VSI instance.

    -

    NOTE:

    Run qinq stacking client-mode single command to enable a QinQ stacking subinterface to learn the MAC address mapped to the smallest VLAN ID among all VLAN ranges that share the MAC address when the subinterface accesses VPLS services.

  4. Run commit

    The configuration is committed.

Verifying the L2VPN Service Configuration on the QinQ Stacking Sub-interface

After you configure an L2VPN service on a QinQ stacking sub-interface, verify the configuration

Prerequisites

The configurations of the sub-interface for QinQ stacking to provide L2VPN access are complete.

Procedure

  • Run the display qinq information stacking [ interface interface-type interface-number [ .subinterface-number ] ] command to check QinQ stacking information.
  • View the configuration of the L2VPN in CCC mode.

    • Run the display vll ccc [ ccc-name | type { local | remote } ] command to check information about the CCC connection.

    • Run the display l2vpn ccc-interface vc-type ccc [ up | down ] command to check information about the interface in the Up or Down state.

  • View the configuration of the L2VPN in Martini mode.

    • Run the display mpls l2vc [ vc-id | interface interface-type interface-number ] command to check information about the Martini MPLS L2VPN connection on the PE.

    • Run the display mpls l2vc remote-info [ vc-id ] command to check information about the remote Martini MPLS L2VPN connection on the PE.

Example

Run the display qinq information stacking command on the PE. The details about the sub-interface for VLAN stacking are displayed. For example:

<HUAWEI> display qinq information stacking interface gigabitethernet 1/0/1
GigabitEthernet1/0/1.1
    L2VC bound
    Total QinQ Num: 2
      qinq stacking vid 100 vlan-group 1
      qinq stacking vid 200 vlan-group 1
    Total vlan-group Num: 1
      vlan-group 1
  • After VPWS is configured:
    • Run the display vll ccc command. The command output shows that the CCC VC status is Up. For example:

      <HUAWEI> display vll ccc
      total  ccc vc : 1
      local  ccc vc : 1,  1 up
      remote ccc vc : 0,  0 up
      
      name: ce1-ce2, type: local, state: up,
      intf1: GigabitEthernet3/0/0 (up),access-port: false
      
      intf2: GigabitEthernet3/0/2 (up),access-port: false
      VC last up time : 2012/03/08 05:13:10
      VC total up time:  4 days, 5 hours, 11 minutes, 22 seconds
    • Run the display l2vpn ccc-interface vc-type ccc command. The command output shows that the VC type is CCC and that the CCC status is Up. For example:

      <HUAWEI> display l2vpn ccc-interface vc-type all
      Total ccc-interface of CCC: 2
      up (2), down (0)
      Interface                            Encap Type               State     VC Type
      GigabitEthernet3/0/0                 ethernet                 up        ccc
      GigabitEthernet3/0/2                 ethernet                 up        ccc
    • Run the display mpls l2vc remote-info command. The command output shows that Peer Addr is the peer address of the specified VC. For example:

      <HUAWEI> display mpls l2vc remote-info
      Total remote ldp vc : 1
      
      Transport  Group      Peer            Remote         Remote     C   MTU/  N   S
      VC ID      ID         Addr            Encap          VC Label   Bit CELLS Bit Bit
      100        0          192.168.3.3     vlan           18         0   1500  1   0
  • After VPLS is configured:

    Run the display vsi [ name vsi-name ] [ verbose ] command. The command output shows that the VSI State is Up. If you specify verbose, the command output shows that PW Signaling is LDP and that VSI State is Up. For example:

    <HUAWEI> display vsi name vsi1 verbose
     ***VSI Name               : ldp1
        Administrator VSI      : no
        Isolate Spoken         : disable
        VSI Index              : 1
        PW Signaling           : ldp
        Member Discovery Style : static
        Bridge-domain Mode     : disable
        PW MAC Learn Style     : unqualify
        Encapsulation Type     : vlan
        MTU                    : 1500
        Diffserv Mode          : uniform
        Service Class          : --
        Color                  : --
        DomainId               : 255
        Domain Name            :
        Ignore AcState         : disable
        P2P VSI                : disable
        Create Time            : 0 days, 0 hours, 3 minutes, 8 seconds
        VSI State              : up
    
        VSI ID                 : 2
       *Peer Router ID         : 2.2.2.9
        primary or secondary   : primary
        ignore-standby-state   : no
        VC Label               : 17
        Peer Type              : dynamic
        Session                : up
        Tunnel ID              :0x0000000001006a5c21
        Broadcast Tunnel ID    : --
        Broad BackupTunnel ID  : --
        CKey                   : 1
        NKey                   : 3154116711
        Stp Enable             : 0
        PwIndex                : 0
        Control Word           : disable
       *Peer Router ID         : 3.3.3.9
        primary or secondary   : primary
        ignore-standby-state   : no
        VC Label               : 18
        Peer Type              : dynamic
        Session                : up
        Tunnel ID              : 0x0000000001004c4b43
        Broadcast Tunnel ID    : --
        Broad BackupTunnel ID  : --
        CKey                   : 2
        NKey                   : 3154116712
        Stp Enable             : 0
        PwIndex                : 0
        Control Word           : disable
    
        Interface Name         : GigabitEthernet1/0/1.1
        State                  : up
        Access Port            : false
        Last Up Time           : 2012/07/19 03:19:14
        Total Up Time          : 0 days, 0 hours, 3 minutes, 11 seconds
    
      **PW Information:
    
       *Peer Ip Address        : 2.2.2.9
        PW State               : up
        Local VC Label         : 17
        Remote VC Label        : 17
        Remote Control Word    : disable
        PW Type                : label
        Tunnel ID              : 0x0000000001006a5c21
        Broadcast Tunnel ID    : --
        Broad BackupTunnel ID  : --
        Ckey                   : 1
        Nkey                   : 3154116711
        Main PW Token          : 0x0
        Slave PW Token         : 0x0
        Tnl Type               : ldp
        OutInterface           : LDP LSP
        Backup OutInterface    :
        Stp Enable             : 0
        PW Last Up Time        : 2012/07/19 03:21:09
        PW Total Up Time       : 0 days, 0 hours, 0 minutes, 29 seconds
       *Peer Ip Address        : 3.3.3.9
        PW State               : up
        Local VC Label         : 18
        Remote VC Label        : 17
        Remote Control Word    : disable
        PW Type                : label
        Tunnel ID              : 0x0000000001004c4b43
        Broadcast Tunnel ID    : --
        Broad BackupTunnel ID  : --
        Ckey                   : 2
        Nkey                   : 3154116712
        Main PW Token          : 0x0
        Slave PW Token         : 0x0
        Tnl Type               : ldp
        OutInterface           : LDP LSP
        Backup OutInterface    :
        Stp Enable             : 0
        PW Last Up Time        : 2012/07/19 03:21:09
        PW Total Up Time       : 0 days, 0 hours, 0 minutes, 29 seconds
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059440

Views: 30086

Downloads: 23

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