Solved: VPLS autodiscovery between cisco and juniper - Page 2

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

bangladesh · ‎09-11-2015

man , you're a legend :)

the ping works.

7604#ping mpls pseudowire 172.18.0.3 1406
%Total number of MS-PW segments is less than segment number; Adjusting the segment number to 1
Sending 5, 100-byte MPLS Echos to 172.18.0.3,
timeout is 2 seconds, send interval is 0 msec:

Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' - unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch,
'M' - malformed request, 'm' - unsupported tlvs, 'N' - no label entry,
'P' - no rx intf label prot, 'p' - premature termination of LSP,
'R' - transit router, 'I' - unknown upstream index,
'X' - unknown return code, 'x' - return code 0

Type escape sequence to abort.
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
7604#

Vinit Jain · ‎09-11-2015

ok.. so now can you share the show mpls l2 vc <vcid> det output again to see if the send counters incremented.

I still think my suspect is correct on the support on VPLS with Core facing card as RSP.

Let me see if i can setup something at my end to check this out.

Regards

Vinit

Thanks
--Vinit

bangladesh · ‎09-11-2015

nope....still zero

MPLS_7604_ASN#sh 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: 11:55:24, last status change time: 03:58:03
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

bangladesh · ‎09-11-2015

In the output above , it says that the signalling protocol is LDP. Shouldn't it be BGP according to the config?

Thanks for your help

Vinit Jain · ‎09-11-2015

7600 doesn't support BGP signaling. It only supports LDP signaling. VPLS AD can happen using BGP but signaling will be LDP.

Thanks
--Vinit

Vinit Jain · ‎09-11-2015

Can you run the below command on SP of RSP720.

remote login switch

show platform atom ether-vc vlan <> all

I was researching a bit on this and found that RSP cannot be a core facing interface for VPLS. It has to be one of the linecards that i mentioned before.

Hope this answers why you are facing the problem.

Regards

Vinit

Thanks
--Vinit

bangladesh · ‎09-11-2015

Command does not seem to be supported:

7604#show platform atom ?
% Unrecognized command
7604#show platform ?
bridge Distributed/Hardware-based bridging information
buffers Show buffer allocation
cfm Show CFM Commands
copp CWAN Control Plane Policing
dma Show DMA channel information
eeprom Show CPU eeprom
eobc Statistics Information for eobc between RP/SP and Linecards
fault Show fault data
fifo Statistics for eobc-fifo between RP and SP
hardware Show platform hardware information
ibc Statistics for IBC
interrupts Show m8500 interrupt counters
isg CWAN iEdge RP
ivrf status platform ivrf status
lowq Display X40g low queue information
ltl-mgr Display CWAN LTL manager info
mplsomgre CWAN Multipoint GRE RP
mtp Mac Tunneling Protocol info
netint Show platform net interrupt information
redundancy Display bias and CWAN platform redundancy
software Show platform software information
stats Display CWAN statistics
supervisor Show supervisor info
tech-support Show system information for Tech-Support
tlb Show processor TLB registers
vfi Display CWAN VFI commands
vlans Display hidden VLAN to WAN interface mapping
| Output modifiers

Vinit Jain · ‎09-11-2015

That kind of answers. This command is used to check the hardware programming for the vpls on core facing LC.

Thus now, the only solution, would be to use ES20 or ES+ linecards if possible or some other router that supports this feature.

Please let me know if you have any further questions.

Regards

Vinit

PS: Please mark the question as answered if all your queries have been answered

Thanks
--Vinit

bangladesh · ‎09-11-2015

Hi thanks for the input. But in the example you provided (http://blog.codergenie.com/blog/post/2013/01/01/BGP-based-VPLS-Autodiscovery.aspx) , the guy is using the same linecard as me for vpls autodiscovery via bgp signalling.

Could it be an IOS issue?

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

bangladesh · ‎09-10-2015

Hi ,

in the case scenarion in the link , the created a service instance. I currently don't have the same options.( encapsulation dot1q,rewrite ingress tag pop 1 symmetric,l2protocol forward, etc...)

7604(config)#interface GigabitEthernet2/47
7604(config-if)#service instance 1406 ethernet
7604(config-if-srv)#?
Ethernet EFP configuration commands:
default Set a command to its defaults
ethernet Configure ether lmi parameters
exit Exit from ETHER EFP configuration mode
no Negate a command or set its defaults

any ideas?

bangladesh · ‎09-10-2015

has anyone ever make this kind of setup between juniper and cisco?

bangladesh · ‎09-10-2015

MPLS_7604_ASN#sh version
Cisco IOS Software, c7600rsp72043_rp Software (c7600rsp72043_rp-ADVIPSERVICESK9-M), Version 12.2(33)SRE4, RELEASE SOFTWARE (fc2)

for your info.

thanks