VPLS configuration(unable to ping)

[sachin30720041]

Hello,

I have configured VPLS on following setup.

ios12----CSR1----CSR2---ios13

But I can not ping from ios12 to ios13.

ios12#ping 100.10.10.13
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 100.10.10.13, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

pseudowire100003 between CSR1 and CSR2 is up.

Router#show l2vpn vfi
Pseudo-port interface: pseudowire100001
Interface                  Peer Address   VE-ID   Local Label   Remote Label   S
pseudowire100003   2.2.2.2              124       20               29               Y

ios12
------------------
int gi0/2
ip address 100.10.10.12 255.255.255.0
no sh

csr1
---------------
int gi2
no sh
service instance 100 ethernet
encap untagged
exit

int gi1
ip address 100.10.20.1 255.255.255.0
no sh
ip ospf 1 area 0

int lo0
ip address 1.1.1.1 255.255.255.255
ip ospf 1 area 0

router ospf 1
router-id 1.1.1.1
exit

l2vpn
router-id 1.1.1.1

l2vpn vfi context ctx1
vpn id 123
l2protocol forward cdp
autodiscovery bgp signaling bgp
ve id 123
rd 2000:9

router bgp 12
no bgp default ipv4-unicast
neighbor 2.2.2.2 remote-as 12
neighbor 2.2.2.2 update-source lo0
address-family l2vpn vpls
neighbor 2.2.2.2 activate
neighbor 2.2.2.2 suppress-singaling-protocol ldp

CSR2
--------------------
int gi2
no sh
service instance 100 ethernet
encap untagged
exit

int gi1
ip address 100.10.20.2 255.255.255.0
no sh
ip ospf 1 area 0

int lo0
ip address 2.2.2.2 255.255.255.255
ip ospf 1 area 0

router ospf 1
router-id 2.2.2.2
exit

l2vpn
router-id 2.2.2.2

l2vpn vfi context ctx1
vpn id 123
l2protocol forward cdp
autodiscovery bgp signaling bgp
ve id 124
rd 2000:9

router bgp 12
no bgp default ipv4-unicast
neighbor 1.1.1.1 remote-as 12
neighbor 1.1.1.1 update-source lo0
address-family l2vpn vpls
neighbor 1.1.1.1 activate
neighbor 1.1.1.1 suppress-signaling-protocol ldp

ios12
------------------
int gi0/2
ip address 100.10.10.13 255.255.255.0
no sh

Thanks,

Sachin

[MHM Cisco World]

I don't know if you run GNS3 but if you use GNS3 
can you wireshark the ICMP between both CSR1 and CSR2 please share the ICMP capture here 

[balaji.bandi · Accepted solution]

Got some time to boot my old Lab which was test long back - simple topology like yours

P42#show l2vpn vfi
Legend: RT=Route-target, S=Split-horizon, Y=Yes, N=No

VFI name: ctx1, state: up, type: multipoint, signaling: BGP
  VPN ID: 20009, VE-ID: 123, VE-SIZE: 10 
  RD: 2000:9, RT: 12:20009, 
  Bridge-Domain 100 attachment circuits:
  Pseudo-port interface: pseudowire100003
  Interface          Peer Address    VE-ID  Local Label  Remote Label    S
  pseudowire100004   2.2.2.2         124    20           19              Y
  pseudowire100002   2.2.2.2         124    20           19              Y

The instance should be up.

I used below config to test :

CSR 1:
=====

l2vpn
router-id 1.1.1.1
!
l2vpn vfi context ctx1
vpn id 20009
l2protocol forward cdp
autodiscovery bgp signaling bgp
ve id 123
rd 2000:9
!
bridge-domain 100
member GigabitEthernet2 service-instance 100
member vfi ctx1
!
!
cdp run
!
!
interface Loopback0
ip address 1.1.1.1 255.255.255.255
ip ospf 1 area 0
!
interface GigabitEthernet1
ip address 100.10.20.1 255.255.255.0
ip ospf 1 area 0
negotiation auto
cdp enable
no mop enabled
no mop sysid
!
interface GigabitEthernet2
no ip address
negotiation auto
cdp enable
no mop enabled
no mop sysid
service instance 100 ethernet
encapsulation untagged
l2protocol forward cdp
!
!
router ospf 1
router-id 1.1.1.1
passive-interface Loopback0
mpls ldp autoconfig
!
router bgp 12
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor 2.2.2.2 remote-as 12
neighbor 2.2.2.2 update-source Loopback0
!
address-family l2vpn vpls
neighbor 2.2.2.2 activate
neighbor 2.2.2.2 send-community extended
neighbor 2.2.2.2 suppress-signaling-protocol ldp
exit-address-family
!

CSR 2 :

l2vpn
router-id 1.1.1.1
!
l2vpn vfi context ctx1
vpn id 20009
l2protocol forward cdp
autodiscovery bgp signaling bgp
ve id 123
rd 2000:9
!
bridge-domain 100
member GigabitEthernet2 service-instance 100
member vfi ctx1
!
cdp run
!
!
interface Loopback0
ip address 1.1.1.1 255.255.255.255
ip ospf 1 area 0
!
interface GigabitEthernet1
ip address 100.10.20.1 255.255.255.0
ip ospf 1 area 0
negotiation auto
cdp enable
no mop enabled
no mop sysid
!
interface GigabitEthernet2
no ip address
negotiation auto
cdp enable
no mop enabled
no mop sysid
service instance 100 ethernet
encapsulation untagged
l2protocol forward cdp
!
!
router ospf 1
router-id 1.1.1.1
passive-interface Loopback0
mpls ldp autoconfig
!
router bgp 12
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor 2.2.2.2 remote-as 12
neighbor 2.2.2.2 update-source Loopback0
!
address-family l2vpn vpls
neighbor 2.2.2.2 activate
neighbor 2.2.2.2 send-community extended
neighbor 2.2.2.2 suppress-signaling-protocol ldp
exit-address-family
!

here is ping :

#ping 100.10.10.13 repeat 10
Type escape sequence to abort.
Sending 10, 100-byte ICMP Echos to 100.10.10.13, timeout is 2 seconds:
!!!!!!!!!!
Success rate is 100 percent (10/10), round-trip min/avg/max = 3/13/20 ms

There is a good reference :

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/mp_l2_vpns/configuration/xe-16/mp-l2-vpns-xe-16-book/vpls-bgp-signaling-l2vpn-inter-as-option-a.html

[MHM Cisco World]

@balaji.bandi 

You Right 100% he need bridge domain to bridge traffic from service instance to vfi.