S6720 MPLS L2VC on subinterface with VLAN tag

Created: Aug 16, 2018 03:35:17Latest reply: Aug 20, 2018 17:26:24 1236 3 0 0
  Rewarded Hi-coins: 0 (problem resolved)
Hello all,

I'm having some trouble to work with MPLS L2VC using a subinterface from a S6720 Switch, the VC is UP and running, but the problem I'm having is with VLAN tags, it seems that the only way the VC works is without VLAN tags, ortherwise the I can't reach the orther end.. am I missing something?

The scenario is: CE1 > PE1-CISCO (beginning of the tunnel) > MPLS Cloud > PE2-Huawei S6720 (end of the tunnel) > CE2

** Follow the current configuration from the PE2 (S6720) below:

interface XGigabitEthernet0/0/35
 port link-type trunk
interface XGigabitEthernet0/0/35.222
 mtu 1546
 dot1q termination vid 222
 mpls l2vc 222 raw

** Current VC status:

 Total LDP VC : 1     1 up       0 down

 *client interface       : XGigabitEthernet0/0/35.222 is up
  Administrator PW       : no
  session state          : up
  AC status              : up
  Ignore AC state        : disable
  VC state               : up
  Label state            : 0
  Token state            : 0
  VC ID                  : 222
  VC type                : Ethernet
  destination            :
  local VC label         : 1330         remote VC label      : 16262
  control word           : disable
  remote control word    : disable
  forwarding entry       : exist
  local group ID         : 0
  remote group ID        : 67109376
  local AC OAM State     : up
  local PSN OAM State    : up
  local forwarding state : forwarding
  local status code      : 0x0
  remote AC OAM state    : up
  remote PSN OAM state   : up
  remote forwarding state: forwarding
  remote status code     : 0x0
  ignore standby state   : no
  BFD for PW             : unavailable
  VCCV State             : up
  manual fault           : not set
  active state           : active
  link state             : up
  local VC MTU           : 1546         remote VC MTU        : 1546
  local VCCV             : alert ttl lsp-ping bfd
  remote VCCV            : alert ttl lsp-ping
  tunnel policy name     : --
  PW template name       : --
  primary or secondary   : primary
  load balance type      : flow
  Access-port            : false
  Switchover Flag        : false
  VC tunnel/token info   : 1 tunnels/tokens
    NO.0  TNL type       : lsp   , TNL ID : 0x48000b41
    Backup TNL type      : lsp   , TNL ID : 0x0
  create time            : 0 days, 23 hours, 49 minutes, 31 seconds
  up time                : 0 days, 23 hours, 48 minutes, 20 seconds
  last change time       : 0 days, 23 hours, 48 minutes, 20 seconds
  VC last up time        : 2018/08/15 03:38:00
  VC total up time       : 0 days, 23 hours, 48 minutes, 55 seconds
  CKey                   : 37
  NKey                   : 36
  PW redundancy mode     : frr
  AdminPw interface      : --
  AdminPw link state     : --
  Diffserv Mode          : uniform
  Service Class          : be
  Color                  : --
  DomainId               : --
  Domain Name            : --

** Follow below the configuration from the PE1 (Cisco):

interface GigabitEthernet0/0/0/1.222 l2transport
 encapsulation dot1q 222
 rewrite ingress tag pop 1 symmetric
 mtu 1560
 xconnect group CORP
  p2p teste-limeira-l2vc
   interface GigabitEthernet0/0/0/1.222
   neighbor ipv4 pw-id 222
   pw-class Ethernet
  • x
  • convention:

Featured Answers
Created Aug 20, 2018 17:26:24 Helpful(0) Helpful(0)

  • x
  • convention:

All Answers
Fernandoizsa Created Aug 16, 2018 04:00:58 Helpful(0) Helpful(0)

An interface cannot function as an L2VPN AC interface and L3VPN AC interface at the same time. After an interface is bound to an L2VPN, Layer 3 features such as the IP address and routing protocol on this interface become invalid.

Please verify this action.

  • x
  • convention:

user_3122563 Created Aug 16, 2018 20:10:22 Helpful(0) Helpful(0)

Hi Fernandoizsa,

Thank you for your reply, sorry if I wasn't very clear before but I'm not trying to create an L2VPN and L3VPN at the same time, I'm actually trying to create an L2VPN with VLAN tag 222 inside. In the example above is the current configuration that is working, which is without the VLAN tag.. If I change the configuration to tag the VLAN, then I can't reach each end, even with the VC up.
  • x
  • convention:

WheatGrass Created Aug 20, 2018 17:26:24 Helpful(0) Helpful(0)

  • x
  • convention:


You need to log in to reply to the post Login | Register

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."
If the attachment button is not available, update the Adobe Flash Player to the latest version!

Login and enjoy all the member benefits

Fast reply Scroll to top