Got it

VSI is UP but no communication

Created: Jun 4, 2019 20:14:19Latest reply: Jun 8, 2019 07:52:19 1208 5 0 0 0
  Rewarded HiCoins: 1 (problem resolved)

Hello all,


I'm trying to setup a VPN like this, VSI is UP but peers (PC's) can't communicate.

That ERPS setup is a adapted real world scenario, everything is working, all routers can communicate with each other.

OSPF routing is working and also ERPS is working.

When I try to ping from 192.168.0.1 to 192.168.0.2, i got "timed out", but with "arp" command I can see the MAC address of 192.168.0.2 machine and vice-versa.

I want to find out what I am doing wrong...


040010hlcscanzqnsz2s8a.png?ensp_forum.pn


### ROUTER1 ###

#

mpls lsr-id 1.29.1.47

mpls

#

mpls l2vpn

#

vsi 2019 static

 pwsignal ldp

  vsi-id 2019

  peer 1.29.1.59

#

mpls ldp

#

mpls ldp remote-peer 1.29.1.59

 remote-ip 1.29.1.59

#

interface Vlanif2019

l2 binding vsi 2019

 mpls

 mpls ldp

#

interface Vlanif4052

 ip address 2.15.47.2 255.255.255.252

 mpls

 mpls ldp

#

interface Ethernet0/0/0

 portswitch

 port link-type trunk

 port trunk allow-pass vlan 4052

#

interface Ethernet0/0/1

 portswitch

 port link-type trunk

 port trunk allow-pass vlan 2019

#


### ROUTER 6 ###

#

mpls lsr-id 1.29.1.59

mpls

#

mpls l2vpn

#

vsi 2019 static

 pwsignal ldp

  vsi-id 2019

  peer 1.29.1.47

#

mpls ldp

#

mpls ldp remote-peer 1.29.1.47

 remote-ip 1.29.1.47

#

interface Ethernet0/0/0

 ip address 2.15.59.2 255.255.255.252

 mpls

 mpls ldp

#

interface Ethernet0/0/1

 ip address 2.44.59.2 255.255.255.252

 mpls

 mpls ldp

#

interface GigabitEthernet0/0/0

 l2 binding vsi 2019

#


<ROUTER 1>dis vsi name 2019 verbose 

 

 ***VSI Name               : 2019

    Administrator VSI      : no

    Isolate Spoken         : disable

    VSI Index              : 0

    PW Signaling           : ldp

    Member Discovery Style : static

    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, 57 minutes, 58 seconds

    VSI State              : up

 

    VSI ID                 : 2019

   *Peer Router ID         : 1.29.1.59

    primary or secondary   : primary

    ignore-standby-state   : no

    VC Label               : 1030

    Peer Type              : dynamic

    Session                : up

    Tunnel ID              : 0x22 

    Broadcast Tunnel ID    : 0x22 

    Broad BackupTunnel ID  : 0x0 

    CKey                   : 4

    NKey                   : 3

    Stp Enable             : 0

    PwIndex                : 0


    Interface Name         : Vlanif2019

    State                  : up

    Access Port            : false

    Last Up Time           : 2019/06/04 16:24:04

    Total Up Time          : 0 days, 0 hours, 44 minutes, 55 seconds


  **PW Information:


   *Peer Ip Address        : 1.29.1.59

    PW State               : up

    Local VC Label         : 1030

    Remote VC Label        : 1024

    PW Type                : label 

    Tunnel ID              : 0x22 

    Broadcast Tunnel ID    : 0x22 

    Broad BackupTunnel ID  : 0x0 

    Ckey                   : 0x4

    Nkey                   : 0x3

    Main PW Token          : 0x22 

    Slave PW Token         : 0x0 

    Tnl Type               : LSP 

    OutInterface           : Vlanif4052 

    Backup OutInterface    :  

    Stp Enable             : 0 

    PW Last Up Time        : 2019/06/04 17:07:57

    PW Total Up Time       : 0 days, 0 hours, 36 minutes, 4 seconds

<ROUTER 1>



Featured Answers

Recommended answer

chenhui
Admin Created Jun 5, 2019 01:36:22

@broonu hi!


Please modify the connection between ROUTER 1 and ROUTER 2. 

Please don't bind the VSI interface to the VPLS on eNSP. This is a BUG, so when trying to do that, it wouldn't work, even though the VSI state is up.
View more
  • x
  • convention:

All Answers

@broonu hi!


Please modify the connection between ROUTER 1 and ROUTER 2. 

Please don't bind the VSI interface to the VPLS on eNSP. This is a BUG, so when trying to do that, it wouldn't work, even though the VSI state is up.
View more
  • x
  • convention:

Posted by chenhui at 2019-06-05 01:36 @broonu hi, please modify the connection between ROUTER 1 and ROUTER 2, please don't bind VSI interf ...
Hi @chenhui , what is wrong between ROUTER 1 and ROUTER 2?
View more
  • x
  • convention:

Posted by broonu at 2019-06-05 19:22 Hi @chenhui , what is wrong between ROUTER 1 and ROUTER 2?
you could get this problem resolved by modifying the connection between ROUTER 1 and ROUTER 2, modifying the connection with ip address configured on the physical interface, rather than the vlanif interface, in another word, you should cancel the vlanif 4052, and configure the ip address to the interface Ethernet0/0/0 on ROUTER 1 and GE0/0/1 on ROUTER 2.
View more
  • x
  • convention:

Posted by chenhui at 2019-06-06 00:34 you could get this problem resolved by modifying the connection between ROUTER 1 and ROUTER 2, mod ...
OK @chenhui , changing the R1/R2 interconnection from L2 to L3 dit the work, now PC1 and PC2 can communicate, but this is a eNSP bug or my setuo was wrong? Because I aready have this network in production (actually they are S6720 swiches connected in layer2, with MPLS in VLANs), just trying to setup now VPN between those two "PCs".
View more
  • x
  • convention:

Posted by broonu at 2019-06-06 17:04 OK @chenhui , changing the R1/R2 interconnection from L2 to L3 dit the work, now PC1 and PC2 can c ...
I think this is a BUG in ensp,
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.