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

NE40E V800R010C00 Configuration Guide - Virtual Access 01

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 L2VPN Access over VCs

Configuring L2VPN Access over VCs

This section describes how to configure L2VPN access over VCs to implement end-to-end service bearing.

Context

In time division multiplexing (TDM) service scenarios, one has to assign an IP address to each Remote-AP interface and establish a Label Distribution Protocol (LDP) virtual private wire service (VPWS) PW between the master and radio network controller site gateway (RSG) for L2VPN access over VCs, so that end-to-end service bearing can be implemented.

Prerequisites

Before configuring L2VPN access over VCs, complete the following tasks:
  • Configure an Interior Gateway Protocol (IGP) for interworking between the master and RSG.
  • Configure multiprotocol label switching (MPLS) traffic engineering (TE) or MPLS LDP to provide a public tunnel for the L2VPN.
  • Configuring IP RAN Virtual Cluster Access

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface remote-ap interface-number

    The Remote-AP interface view is displayed.

  3. Run:

    mpls l2vc [ instance-name instance-name ] encapsulation { cesopsn-basic | satop-e1 } ip-address vc-id [ [ control-word | no-control-word ] | tunnel-policy tunnel-policy-name | tdm-encapsulation-number tdm-encapsulation-number | tdm-sequence-number | jitter-buffer jitter-buffer | rtp-header | idle-code ] *

    An LDP VPWS PW is established between the master and RSG.

    In this command, parameterstdm-encapsulation-number tdm-encapsulation-number, jitter-buffer jitter-buffer, and idle-code idle-code must be the same as the default settings on the AP-side device so that the multi-segment VPWS connection between the AP and RSG can go Up and transmit TDM services.

  4. Run:

    commit

    The configuration is committed.

Checking the Configurations

  • Run the ping command to check whether the master and RSG can ping each other.

    [~HUAWEI] ping -a 10.1.1.2 1.2.0.1
      PING 1.2.0.1: 56  data bytes, press CTRL_C to break
        Reply from 1.2.0.1: bytes=56 Sequence=1 ttl=253 time=90 ms
        Reply from 1.2.0.1: bytes=56 Sequence=2 ttl=253 time=70 ms
        Reply from 1.2.0.1: bytes=56 Sequence=3 ttl=253 time=120 ms
        Reply from 1.2.0.1: bytes=56 Sequence=4 ttl=253 time=110 ms
        Reply from 1.2.0.1: bytes=56 Sequence=5 ttl=253 time=100 ms
    
      --- 1.2.0.1 ping statistics ---
        5 packet(s) transmitted
        5 packet(s) received
        0.00% packet loss
        round-trip min/avg/max = 70/98/120 ms
  • Run the display mpls l2vc command on the master to check LDP VPWS PW information.

    [~HUAWEI] display mpls l2vc interface remote-ap 2
     *client interface       : Remote-Ap2 is up
      Administrator PW       : no
      session state          : up
      AC status              : up
      VC state               : up
      Label state            : 0
      Token state            : 0
      VC ID                  : 111
      VC type                : CESoPSN basic mode
      destination            : 2.2.2.2
      local group ID         : 0            remote group ID      : 0
      local VC label         : 32790        remote VC label      : 46
      local TDM Encap Num    : 8            remote TDM Encap Num : 8
      jitter-buffer          : 4
      idle-code              : fa
      local rtp-header       : disable      remote rtp-header    : disable
      local bit-rate         : 31           remote bit-rate      : 31
      local AC OAM State     : up
      local PSN OAM State    : up
      local forwarding state : forwarding
      local status code      : 0x0 (forwarding)
      remote AC OAM state    : up
      remote PSN OAM state   : up
      remote forwarding state: forwarding
      remote status code     : 0x0 (forwarding)
      ignore standby state   : no
      BFD for PW             : unavailable
      VCCV State             : up
      manual fault           : not set
      active state           : active
      forwarding entry       : exist
      OAM Protocol           : --
      OAM Status             : --
      OAM Fault Type         : --
      PW APS ID              : --
      PW APS Status          : --
      TTL Value              : 1
      link state             : up
      local VC MTU           : --           remote VC MTU        : --
      local VCCV             : cw alert ttl lsp-ping bfd
      remote VCCV            : cw alert ttl lsp-ping bfd
      local control word     : enable       remote control word  : enable
      tunnel policy name     : --
      PW template name       : --
      primary or secondary   : primary
      load balance type      : flow
      Access-port            : false
      Switchover Flag        : false
      VC tunnel info         : 1 tunnels
        NO.0  TNL type       : ldp   , TNL ID : 0x0000000001004c4b42
      create time            : 0 days, 16 hours, 34 minutes, 29 seconds
      up time                : 0 days, 16 hours, 34 minutes, 19 seconds
      last change time       : 0 days, 16 hours, 34 minutes, 19 seconds
      VC last up time        : 2015/02/12 17:26:47
      VC total up time       : 0 days, 16 hours, 34 minutes, 19 seconds
      CKey                   : 1
      NKey                   : 1694499019
      PW redundancy mode     : frr
      AdminPw interface      : --
      AdminPw link state     : --
      Forward state          : send inactive, receive inactive 
      Diffserv Mode          : uniform
      Service Class          : --
      Color                  : --
      DomainId               : --
      Domain Name            : --

Follow-up Procedure

After completing this configuration task, configure BFD on the master and RSG to monitor the E2E PWs between APs and the RSG. For configuration details, see Configuring BFD for VPWS PW. Configure a static BFD session because only this type of BFD session is supported for TDM services.

Download
Updated: 2018-07-12

Document ID: EDOC1100028541

Views: 7383

Downloads: 92

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