Solved: VPLS autodiscovery between cisco and juniper

bangladesh · ‎09-10-2015

Hi Guys,

This is my first post here , so excuse me if i am posting this in the wrong section.

I am trying to setup up VPLS between a cisco 7604 and a juniper MX router. I work for a big enterprise in Bangladesh and i need to have this up and running soon :)

I configured auto vpls discovery and it doesn't seem to be working. VPLS is still down.

IGP is IS-IS and LDP neighbor is up and running. The 2 boxes are connected via a port channel.(2x1gig)

Can someone please have a look at the below config:

-----------------------------------------------------------------------------------

sh run ( unnecessary output has been removed)

no ip source-route

mpls ldp graceful-restart
mpls label protocol ldp
mls flow ip interface-full
no mls flow ipv6
mls cef error action reset
multilink bundle-name authenticated

bridge-domain 1406

vlan internal allocation policy ascending
vlan access-log ratelimit 2000

vlan 1406

pseudowire-class mpls
encapsulation mpls
no control-word

l2 router-id 172.18.0.46
l2 vfi vpls1 autodiscovery
vpn id 1406

interface Loopback0
ip address 172.18.0.46 255.255.255.255
ip router isis

interface Port-channel9
ip address 172.18.2.18 255.255.255.252
ip router isis
mpls ip
mpls label protocol ldp

interface GigabitEthernet1/1
no ip address
channel-group 9 mode active

interface GigabitEthernet1/2
no ip address
channel-group 9 mode active

interface GigabitEthernet2/48
switchport
switchport access vlan 1406
switchport mode access

interface Vlan1406
ip address 172.30.16.133 255.255.255.252
xconnect vfi vpls1

router isis
net 49.0001.1720.1800.0046.00
is-type level-2-only
metric-style wide
log-adjacency-changes

router bgp 66xxx
bgp router-id 172.18.0.46
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 172.18.0.3 remote-as 66xxx
neighbor 172.18.0.3 update-source Loopback0
neighbor 172.18.0.3 timers 30 90

address-family ipv4
no synchronization
no auto-summary
exit-address-family

address-family vpnv4
neighbor 172.18.0.3 activate
neighbor 172.18.0.3 send-community both
exit-address-family

address-family l2vpn vpls
neighbor 172.18.0.3 activate
neighbor 172.18.0.3 send-community both
neighbor 172.18.0.3 prefix-length-size 2
exit-address-family

ip bgp-community new-format

mpls ldp router-id Loopback0 force

--------------------------------------------
7604# sh interfaces vlan 1406
Vlan1406 is up, line protocol is up
-------------------------------------------

7604#show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware

XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP ac Vl1406:1406(Eth VLAN) UP vfi vpls1 UP

7604#show vfi

Legend: RT=Route-target, S=Split-horizon, Y=Yes, N=No

VFI name: vpls1, state: up, type: multipoint
VPN ID: 1406, VPLS-ID: 30999:1406
RD: 30999:1406, RT: 30999:1406
Local attachment circuits:
Vlan1406
Neighbors connected via pseudowires:
Peer Address VC ID Discovered Router ID S

------------------------------------------------------------------------------------------

show mpls ldp neighbor
Peer LDP Ident: 172.18.0.3:0; Local LDP Ident 172.18.0.46:0
TCP connection: 172.18.0.3.646 - 172.18.0.46.17356
State: Oper; Msgs sent/rcvd: 983/794; Downstream
Up time: 02:07:05
LDP discovery sources:
Port-channel9, Src IP addr: 172.18.2.17
Addresses bound to peer LDP Ident:
172.18.0.3 x.x.x.x

Vinit Jain · ‎09-12-2015

If you look at the output there, the signaling is LDP. Also, the linecard being used is ES+. Thats the reason why its working for them.

Hope this clarifies.

Thanks
--Vinit

View solution in original post

bangladesh · ‎09-10-2015

which debug could i use to troubleshoot this issue?

Vinit Jain · ‎09-10-2015

Hello,

Could you please refer to the below post to configure VPLS audo-discovery:

http://blog.codergenie.com/blog/post/2013/01/01/BGP-based-VPLS-Autodiscovery.aspx

Please let know what linecards are you running on Core and the CE facing. Please share the show module.

Regards

Vinit

Thanks
--Vinit

bangladesh · ‎09-10-2015

Hi vinit,

i am using DESCR: "RSP720-3C-GE 2 ports Route Switch Processor 720 Rev. 5.12

Thanks for the link. I will check it.

below is a show inventory:

NAME: "CISCO7604", DESCR: "Cisco Systems Cisco 7600 4-slot Chassis System"

NAME: "CLK-7600 1", DESCR: "OSR-7600 Clock FRU 1"

NAME: "CLK-7600 2", DESCR: "OSR-7600 Clock FRU 2"

NAME: "module 1", DESCR: "RSP720-3C-GE 2 ports Route Switch Processor 720 Rev. 5.12"

NAME: "msfc sub-module of 1", DESCR: "7600-MSFC4 C7600 MSFC4 Daughterboard Rev. 1.6"

NAME: "switching engine sub-module of 1", DESCR: "7600-PFC3C Policy Feature Card 3 Rev. 1.2"

NAME: "module 2", DESCR: "WS-X6748-GE-TX CEF720 48 port 10/100/1000mb Ethernet Rev. 4.1"

NAME: "switching engine sub-module of 2", DESCR: "WS-F6700-CFC Centralized Forwarding Card Rev. 4.1"

bangladesh · ‎09-10-2015

Please find below requested output:

7604#sh module
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 2 Route Switch Processor 720 (Active) RSP720-3C-GE
2 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX

Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
1 68ef.bdd3.69f4 to 68ef.bdd3.69f7 5.12 12.2(33r)SRD 12.2(33)SRE4 Ok
2 0007.7d04.0000 to 0007.7d04.002f 4.1 12.2(18r)S1 12.2(33)SRE4 Ok

Mod Sub-Module Model Serial Hw Status
---- --------------------------- ------------------ ----------- ------- -------
1 Policy Feature Card 3 7600-PFC3C JAE1451013O 1.2 Ok
1 C7600 MSFC4 Daughterboard 7600-MSFC4 JAE144906UB 1.6 Ok
2 Centralized Forwarding Card WS-F6700-CFC SAL1535NSN9 4.1 Ok

Mod Online Diag Status
---- -------------------
1 Pass
2 Pass

Vinit Jain · ‎09-10-2015

Hello

67XX cards are lan cards and might not have support for EVC (Service instance). Its supported on cards like ES20 or ES+.

I see your xconnect is up. Are you able to pass traffic across it?

Can you share the output of a pseudowire ping from PE to PE and please share the below output:

- show mpls l2 vc <vcid> det

Thanks,

Vinit

Thanks
--Vinit

bangladesh · ‎09-10-2015

7604#show mpls l2 vc 1406 detail

7604#

vc seems to be down. Same is down at juniper end too. Is there some specific features that should be configured? are you used to junos ?

7604#show mpls l2 vc 1406

Local intf Local circuit Dest address VC ID Status
------------- -------------------------- --------------- ---------- ----------
7604#

Vinit Jain · ‎09-10-2015

Sorry, I am not used to Junos. The only other thing i can ask you to try try ES20 or ES+ linecard as your Core link rather than having RSP or any LAN card as Core.

If you are using xconnect under SVI, then i think you should use one of the WAN cards like SIP-400, SIP-600 or ES20/ES+ cards as your Core link. This applies for EoMPLS, so possibly shud be applicable for VPLS.

Can you try your Core facing linecard as any of the above WAN cards.

http://www.cisco.com/c/en/us/td/docs/ios/mpls/configuration/guide/15_0s/mp_15_0s_book/mp_vpls_auto_bgp.pdf

Regards

Vinit

Thanks
--Vinit

bangladesh · ‎09-10-2015

Thanks for the input.

Unfortunately we don't have other linecards.

Will static VPLS work?

bangladesh · ‎09-11-2015

Hi the xconnect is now up. the juniper had to be configured with multihoming vpls option.

M7604#sh xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware

XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP vfi vpls1 UP mpls 172.18.0.3:1406 UP
UP ac Vl1406:1406(Eth VLAN) UP vfi vpls1 UP

M7604#sh vfi

Legend: RT=Route-target, S=Split-horizon, Y=Yes, N=No

VFI name: vpls1, state: up, type: multipoint
VPN ID: 1406, VPLS-ID: 30999:1406
RD: 30999:1406, RT: 30999:1406
Local attachment circuits:
Vlan1406
Neighbors connected via pseudowires:
Peer Address VC ID Discovered Router ID S
172.18.0.3 1406 172.18.0.3 Y

Setup:

7604---MX--Test Switch

The 7604 has an ip address assigned to the interface vlan 1406.

I also assigned an IP to the interface vlan 1406 on the test switch. Unfortunately i am not able to ping both ends.

any ideas?

Vinit Jain · ‎09-11-2015

Are you able to perform a psedowire ping between 7600 and Juniper.

Also, If you perform the ping, in the show mpls l2 vc <vcid> det output, do you see the packet counters incrementing? If yes, are you seeing both send and receive counters incrementing?

Thanks
--Vinit

bangladesh · ‎09-11-2015

can do give me the correct syntax for pseudowire ping?

MPLS_7604_ASN#ping mpls pseudowire 172.30.16.134 1406
% Pseudowire Target Not Supported

From below output i can see : TLV not supported on remote. Is this important for the VPLS session? because i enabled same on junos and the status remained the same.

The sent counters are zero.

MPLS_7604_ASN#show mpls l2 vc 1406 detail
Local interface: VFI vpls1 VFI up
Interworking type is Ethernet
Destination address: 172.18.0.3, VC ID: 1406, VC status: up
Output interface: Po9, imposed label stack {458767}
Preferred path: not configured
Default path: active
Next hop: 172.18.2.17
Create time: 08:07:54, last status change time: 00:10:34
Signaling protocol: LDP, peer 172.18.0.3:0 up
Targeted Hello: 172.18.0.46(LDP Id) -> 172.18.0.3, LDP is UP
Status TLV support (local/remote) : enabled/not supported
LDP route watch : enabled
Label/status state machine : established, LruRru
Last local dataplane status rcvd: No fault
Last local SSS circuit status rcvd: No fault
Last local SSS circuit status sent: No fault
Last local LDP TLV status sent: No fault
Last remote LDP TLV status rcvd: Not sent
Last remote LDP ADJ status rcvd: No fault
MPLS VC labels: local 165, remote 458767
AGI: type 1, len 8, 000A 7917 0000 057E
Local AII: type 1, len 4, AC12 002E (172.18.0.46)
Remote AII: type 1, len 4, AC12 0003 (172.18.0.3)
Group ID: local n/a, remote n/a
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
Control Word: Off (configured: autosense)
VC statistics:
transit packet totals: receive 1648, send 0
transit byte totals: receive 98820, send 0
transit packet drops: receive 0, seq error 0, send 0

Vinit Jain · ‎09-11-2015

Thanks for the output. The syntax for psedowire ping is below:

ping mpls pseudowire <remote_PE_loopback> <vcid>

Also, from the above output, i see that the send counters is not incrementing. Like i said before, this is possible due to the LC limitation. I might have to further research a bit on it.

Regards

Vinit

Thanks
--Vinit

bangladesh · ‎09-11-2015

Thanks. i tried the command

MPLS_7604_ASN#ping mpls pseudowire 172.30.16.134 1406
% Pseudowire Target Not Supported

Don't know where to go from here. We've got thousands of VPLS sessions running on our juniper boxes and this cisco box is bugging me.

Thanks for your help. I really appreciate it :)

Vinit Jain · ‎09-11-2015

Your destination is wrong. it should be 172.18.0.3.

Can you try with this.

Thanks
--Vinit