Got it

MPLS L2VPN in eNSP

Created: Nov 14, 2018 12:11:44Latest reply: Nov 20, 2018 08:00:25 2659 7 1 0 0
  Rewarded HiCoins: 1 (problem resolved)

Hello!

I'm trying to configure MPLS L2VPN in eNSP, tunnel goes up state:
<r3>dis mpls l2vc
 Total LDP VC : 1     1 up       0 down 
*client interface     : GigabitEthernet0/0/1 is up
  Administrator PW     : no
  session state        : up
  AC status            : up
  VC state             : up
  Label state          : 0
  Token state          : 0
  VC ID                : 100
  VC type              : Ethernet
  destination          : 10.0.0.1
  local VC label       : 1024         remote VC label      : 1024
  control word         : disable
  forwarding entry     : exist
  local group ID       : 0
  manual fault         : not set
  active state         : active
  OAM Protocol         : --
  OAM Status           : --
  OAM Fault Type       : --
  PW APS ID            : 0
  PW APS Status        : --
  TTL Value            : 1
  link state           : up
  local VC MTU         : 1500         remote VC MTU        : 1500
  tunnel policy name   : --
  PW template name     : --
  primary or secondary : primary
  load balance type    : flow
  Access-port          : false
  create time          : 0 days, 0 hours, 16 minutes, 0 seconds
  up time              : 0 days, 0 hours, 15 minutes, 0 seconds
  last change time     : 0 days, 0 hours, 15 minutes, 0 seconds
  VC last up time      : 2018/11/15 01:07:26
  VC total up time     : 0 days, 0 hours, 15 minutes, 0 seconds
  CKey                 : 2
  NKey                 : 1
  AdminPw interface    : --
  AdminPw link state   : --
  Diffserv Mode        : uniform
  Service Class        : --
  Color                : --
  DomainId             : --
  Domain Name          : --

But "customer's" gateways still does not have connectivity.

 

Ready to use topology for eNSP attached.

R1 .. R5 - provider's routers, also R1 and R3 are PE.

gw1 and gw2 - CE.

 

I tried to apply on interface "static" configuration:

mpls static-l2vc destination 10.0.0.3 transmit-vpn-label 100 receive-vpn-label 200

and "dynamic" configuration:

mpls l2vc 10.0.0.3 100

But tunnel does not work in both cases.

 

What is wrong?

Attachment: You need to log in to download or view. No account? Register
  • x
  • convention:

Featured Answers
No.9527
Created Nov 15, 2018 03:59:24

Hi there!


In fact, you better create a ticket to support you solve this problem. Currently, we can only provide you with some suggestion.

 

Under What Conditions Can a VSI Be Up in a VPLS Network?


In the case that the configurations are correct, VPLS can be up when one of the following conditions is met:


  • mVSI: requires an Up PW or an Up AC in the VSI;


  • Service VSI: requires two or more Up AC interfaces, or an Up AC interface and an Up PW.

 

How to Locate the Cause of the Problem that the Martini or PWE3 VLL Connection Fails to Go Up?


Take the VLL on GE 1/0/0.1 as an example. Perform the following operations:

Check whether the VC IDs, encapsulation types, MTUs, and control words on both ends of a VSI are the same, and whether the VLL or VPLS on both ends are configured in Martini mode.

Solution


If not, set the same parameters on both ends. If the peer is configured with the Martini VPLS, the control word must be Disable.

Check whether the AC interface (GE 1/0/0.1 in this example) bound to a VLL is Up.

Check whether an LDP session is Up.

Solution


If not, run the display mpls ldp session command to check whether the LDP session is in the Operational state. If the LDP session is not in the Operational state, check the public network links and LDP configurations according to FAQs of MPLS LDP.

Check whether the PW has selected a tunnel.

Run the display mpls l2vc vc-id command.

Check the VC tunnel/token info field in the command output. If VC tunnel/token info is displayed as 0 tunnels/tokens, it indicates that no tunnel is selected by a PW.


Check the tunnel policy name field in the command output.


If tunnel policy name is displayed as "-", it indicates that an LDP LSP is used as the tunnel for a PW or no tunnel policy is configured. An MPLS TE tunnel can be used for a PW only after a tunnel policy is configured.


If tunnel policy name is not displayed as "-", it indicates that a tunnel policy is adopted. In this case, you can run the display this command in the tunnel policy view to view the tunnel policy configuration.

[HUAWEI-tunnel-policy-p1] display this
#
tunnel-policy p1
tunnel select-seq cr-lsp load-balance-number 1
#


NOTE:

 
If the tunnel binding destination dest-ip-address te { tunnel interface-number } command is configured in the tunnel policy view, you also need to run the mpls te reserved-for-binding command on the tunnel interface.

Check whether the remote label exists.

Solution


If the remote label is 0, check the peer device according to the preceding p***edure.

In PWE3 mode, check and ensure that the forwarding status on the local and remote ends is 'forwarding'.

display mpls l2vc interface gigabitethernet 1/0/0.1
*client interface        : GigabitEthernet1/0/0.1 is up
  session state          : up
  AC state               : up
  VC state               : up
  VC ID                  : 100
  VC type                : VLAN
  destination            : 192.3.3.3
  local group ID         : 0       remote group ID      : 0
  local VC label         : 21504   remote VC label      : 21504
  local AC OAM State     : up
  local PSN State        : up
  local forwarding state : forwarding
  remote AC OAM state    : up
  remote PSN state       : up
  remote forwarding state: forwarding
  BFD for PW             : unavailable
  manual fault           : not set
  active state           : active
  forwarding entry       : exist
  link state             : up
  local VC MTU           : 1500     remote VC MTU        : 1500
  local VCCV             : Disable
  remote VCCV            : Disable
  local control word     : disable  remote control word  : disable
  tunnel policy          : --
  traffic behavior       : --
  PW template name       : --
  primary or secondary   : primary
  VC tunnel/token info   : 1 tunnels/tokens
    NO.0  TNL type : lsp   , TNL ID : 0x2002003
  create time            : 0 days, 0 hours, 7 minutes, 16 seconds
  up time                : 0 days, 0 hours, 5 minutes, 6 seconds
  last change time       : 0 days, 0 hours, 5 minutes, 6 seconds

View more
  • x
  • convention:

MATPOCKuH
MATPOCKuH Created Nov 20, 2018 07:46:12 (0) (0)
I'm sorry, but:
1. There are NO display mpls l2vc vc-id:
<r3>display mpls l2vc vc-id
^
Error: Wrong parameter found at '^' position.

2. I'm does not want to establish MPLS TE. I want to have a clean MPLS L2VPN.  
No.9527
No.9527 Reply MATPOCKuH  Created Nov 22, 2018 03:46:07 (0) (0)
I have checked your configuration seems fine.
sometimes eNSP has a litter strange, maybe reboot devices then will be fine. also eNSP has a lot of limit to excute command for troubleshooting.
you can refer to Huawei officical document for some configurat 
All Answers
Fernandoizsa
Fernandoizsa Created Nov 14, 2018 17:20:03

I suggest verify the routing configuration, 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.

Also please confirm the eNSP version, please be sure that you are using the latest version.
View more
  • x
  • convention:

MATPOCKuH
MATPOCKuH Created Nov 20, 2018 07:53:05 (0) (0)
Please check my topology - all loopback addresses on all PE and P routers are available.
And i'm not mix L2 and L3 interfaces.
I'm using eNSP 1.2.00.510 V100R002C00B510.
As I know, this is latest version.  
No.9527
No.9527 Created Nov 15, 2018 03:59:24

Hi there!


In fact, you better create a ticket to support you solve this problem. Currently, we can only provide you with some suggestion.

 

Under What Conditions Can a VSI Be Up in a VPLS Network?


In the case that the configurations are correct, VPLS can be up when one of the following conditions is met:


  • mVSI: requires an Up PW or an Up AC in the VSI;


  • Service VSI: requires two or more Up AC interfaces, or an Up AC interface and an Up PW.

 

How to Locate the Cause of the Problem that the Martini or PWE3 VLL Connection Fails to Go Up?


Take the VLL on GE 1/0/0.1 as an example. Perform the following operations:

Check whether the VC IDs, encapsulation types, MTUs, and control words on both ends of a VSI are the same, and whether the VLL or VPLS on both ends are configured in Martini mode.

Solution


If not, set the same parameters on both ends. If the peer is configured with the Martini VPLS, the control word must be Disable.

Check whether the AC interface (GE 1/0/0.1 in this example) bound to a VLL is Up.

Check whether an LDP session is Up.

Solution


If not, run the display mpls ldp session command to check whether the LDP session is in the Operational state. If the LDP session is not in the Operational state, check the public network links and LDP configurations according to FAQs of MPLS LDP.

Check whether the PW has selected a tunnel.

Run the display mpls l2vc vc-id command.

Check the VC tunnel/token info field in the command output. If VC tunnel/token info is displayed as 0 tunnels/tokens, it indicates that no tunnel is selected by a PW.


Check the tunnel policy name field in the command output.


If tunnel policy name is displayed as "-", it indicates that an LDP LSP is used as the tunnel for a PW or no tunnel policy is configured. An MPLS TE tunnel can be used for a PW only after a tunnel policy is configured.


If tunnel policy name is not displayed as "-", it indicates that a tunnel policy is adopted. In this case, you can run the display this command in the tunnel policy view to view the tunnel policy configuration.

[HUAWEI-tunnel-policy-p1] display this
#
tunnel-policy p1
tunnel select-seq cr-lsp load-balance-number 1
#


NOTE:

 
If the tunnel binding destination dest-ip-address te { tunnel interface-number } command is configured in the tunnel policy view, you also need to run the mpls te reserved-for-binding command on the tunnel interface.

Check whether the remote label exists.

Solution


If the remote label is 0, check the peer device according to the preceding p***edure.

In PWE3 mode, check and ensure that the forwarding status on the local and remote ends is 'forwarding'.

display mpls l2vc interface gigabitethernet 1/0/0.1
*client interface        : GigabitEthernet1/0/0.1 is up
  session state          : up
  AC state               : up
  VC state               : up
  VC ID                  : 100
  VC type                : VLAN
  destination            : 192.3.3.3
  local group ID         : 0       remote group ID      : 0
  local VC label         : 21504   remote VC label      : 21504
  local AC OAM State     : up
  local PSN State        : up
  local forwarding state : forwarding
  remote AC OAM state    : up
  remote PSN state       : up
  remote forwarding state: forwarding
  BFD for PW             : unavailable
  manual fault           : not set
  active state           : active
  forwarding entry       : exist
  link state             : up
  local VC MTU           : 1500     remote VC MTU        : 1500
  local VCCV             : Disable
  remote VCCV            : Disable
  local control word     : disable  remote control word  : disable
  tunnel policy          : --
  traffic behavior       : --
  PW template name       : --
  primary or secondary   : primary
  VC tunnel/token info   : 1 tunnels/tokens
    NO.0  TNL type : lsp   , TNL ID : 0x2002003
  create time            : 0 days, 0 hours, 7 minutes, 16 seconds
  up time                : 0 days, 0 hours, 5 minutes, 6 seconds
  last change time       : 0 days, 0 hours, 5 minutes, 6 seconds

View more
  • x
  • convention:

MATPOCKuH
MATPOCKuH Created Nov 20, 2018 07:46:12 (0) (0)
I'm sorry, but:
1. There are NO display mpls l2vc vc-id:
<r3>display mpls l2vc vc-id
^
Error: Wrong parameter found at '^' position.

2. I'm does not want to establish MPLS TE. I want to have a clean MPLS L2VPN.  
No.9527
No.9527 Reply MATPOCKuH  Created Nov 22, 2018 03:46:07 (0) (0)
I have checked your configuration seems fine.
sometimes eNSP has a litter strange, maybe reboot devices then will be fine. also eNSP has a lot of limit to excute command for troubleshooting.
you can refer to Huawei officical document for some configurat 
No.9527
No.9527 Created Nov 15, 2018 03:59:46

MPLS L2VPN in eNSP-2801265-1
View more
  • x
  • convention:

MATPOCKuH
MATPOCKuH Created Nov 20, 2018 08:00:25

Who marked my question as solved?
My problem does NOT solved.
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

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 " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.