[c-nsp] Cisco Juniper Xconnect

Alireza Soltanian soltanian at gmail.com
Sun Apr 24 08:07:49 EDT 2016 

This is a data plane issue not control plane issue

On Sunday, April 24, 2016, Alireza Soltanian <soltanian at gmail.com> wrote:

> No unfortunately but CSR1000v use same configuration as IOS.
> For Juniper I did not use Olive for this. I use M320 series. I must
> mention L2VPN is really hardware dependent in Juniper and features is very
> different with different types of modules and Chassis.
> Normally this issue of your happens when PE wants to remove VPN label and
> add VLAN TAG
>
> On Sunday, April 24, 2016, Mohammad Khalil <eng_mssk at hotmail.com
> <javascript:_e(%7B%7D,'cvml','eng_mssk at hotmail.com');>> wrote:
>
>> U mean this line : set interfaces em1 unit 23 family ccc ?
>> I have removed it
>> The VLAN-ID already match on both ends which is 23 the same as the VCID ,
>> I have changed to 520
>>
>> I will try to use CSR1000v and check what will happen
>> Can you please post the template you are following?
>>
>> Thanks a lot
>>
>> ------------------------------
>> Date: Sun, 24 Apr 2016 16:26:52 +0430
>> Subject: Re: [c-nsp] Cisco Juniper Xconnect
>> From: soltanian at gmail.com
>> To: eng_mssk at hotmail.com
>> CC: cisco-nsp at puck.nether.net
>>
>> Hi
>> I am not sure but the last line is not required. Also please try same
>> VLAN-ID on both side. Also choose VLAN-ID higher than 512. If this does not
>> work then Olive does not support L2VPN. At least with GNS3.
>> If you can please do the test with CSR1000v and JunOS olive and over
>> VMWare instead of VirtualBOX
>>
>> Regards
>> Alireza
>>
>> On Sunday, April 24, 2016, Mohammad Khalil <eng_mssk at hotmail.com> wrote:
>>
>> root# show interfaces em0 | display set
>> set interfaces em0 mtu 1514
>> set interfaces em0 unit 0 family inet address 192.168.101.10/24
>> set interfaces em0 unit 0 family mpls
>>
>> [edit]
>> root# show interfaces em1 | display set
>> set interfaces em1 vlan-tagging
>> set interfaces em1 unit 23 encapsulation vlan-ccc
>> set interfaces em1 unit 23 vlan-id 23
>> set interfaces em1 unit 23 family ccc
>>
>>
>>
>>
>> No not at all. If there is an MTU issue then your L2VPN will be down.
>> Would you please resend interface configuration on JunOs?
>>
>> On Sunday, April 24, 2016, Mohammad Khalil <eng_mssk at hotmail.com> wrote:
>>
>> Thanks dear
>> I have removed the below lines
>>
>> R2 (CE connected to Cisco)
>> R2#sh ip arp
>> Protocol  Address          Age (min)  Hardware Addr   Type   Interface
>> Internet  192.168.23.2            -   c202.1a7c.0000  ARPA
>> FastEthernet0/0.23
>> Internet  192.168.23.3            0   Incomplete      ARPA
>>
>> R3#sh ip arp
>> Protocol  Address          Age (min)  Hardware Addr   Type   Interface
>> Internet  192.168.23.2            0   c202.1a7c.0000  ARPA
>> FastEthernet0/0.23
>> Internet  192.168.23.3            -   c203.247c.0000  ARPA
>> FastEthernet0/0.23
>>
>> Could that be MTU related?
>>
>> ------------------------------
>> From: soltanian at gmail.com
>> To: eng_mssk at hotmail.com; cisco-nsp at puck.nether.net
>> Subject: RE: [c-nsp] Cisco Juniper Xconnect
>> Date: Sun, 24 Apr 2016 16:05:50 +0430
>>
>> I did this for about 1200 Nodes and had no issue But on an actual
>> box(M20). Anyway this may be related to GNS3 and emulation. Also we don’t
>> use following line:
>>
>> set protocols l2circuit neighbor 1.1.1.1 interface em1.23
>> encapsulation-type ethernet-vlan
>> set protocols l2circuit neighbor 1.1.1.1 interface em1.23
>> ignore-encapsulation-mismatch
>> set protocols l2circuit neighbor 1.1.1.1 interface em1.23
>> ignore-mtu-mismatch
>>
>>
>> The first three line is enough.
>> This also can be related to VLAN rewrite section. Do you have traffic in
>> one direction? I mean for example do you have ARP entry from Source IP
>> address on destination device?
>> Getting a PCAP file is also useful.
>>
>>
>>
>> *From:* Mohammad Khalil [mailto:eng_mssk at hotmail.com]
>> *Sent:* Sunday, April 24, 2016 3:59 PM
>> *To:* Alireza Soltanian <soltanian at gmail.com>; cisco-nsp at puck.nether.net
>> *Subject:* RE: [c-nsp] Cisco Juniper Xconnect
>>
>> set protocols l2circuit neighbor 1.1.1.1 interface em1.23
>> virtual-circuit-id 23
>> set protocols l2circuit neighbor 1.1.1.1 interface em1.23 no-control-word
>> set protocols l2circuit neighbor 1.1.1.1 interface em1.23 mtu 1500
>> set protocols l2circuit neighbor 1.1.1.1 interface em1.23
>> encapsulation-type ethernet-vlan
>> set protocols l2circuit neighbor 1.1.1.1 interface em1.23
>> ignore-encapsulation-mismatch
>> set protocols l2circuit neighbor 1.1.1.1 interface em1.23
>> ignore-mtu-mismatch
>>
>> I have added the no-control-word on Juniper and changed the xconnect on
>> Cisco (i was already doing that , but I made the pseduwire to manipulate
>> the parameters)
>>
>> Still no luck
>> > From: soltanian at gmail.com
>> > To: eng_mssk at hotmail.com; cisco-nsp at puck.nether.net
>> > Subject: RE: [c-nsp] Cisco Juniper Xconnect
>> > Date: Sun, 24 Apr 2016 15:41:17 +0430
>> >
>> > Hi
>> > I cannot read JunOS configuration part properly, But it seems you did
>> not
>> > disable Control-word on Juniper side. Did you check this?
>> >
>> >
>> >
>> > -----Original Message-----
>> > From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
>> > Mohammad Khalil
>> > Sent: Sunday, April 24, 2016 3:22 PM
>> > To: cisco-nsp at puck.nether.net
>> > Subject: [c-nsp] Cisco Juniper Xconnect
>> >
>> > Hi all
>> > Am trying to simulate xconnect between Cisco and Juniper using GNS3
>> will it
>> > work in the first manner on GNS3? if so , please check my conf below
>> >
>> > R2 - R1 - J1 - R3
>> >
>> > R2
>> > interface FastEthernet0/0
>> > no ip address
>> > speed 100
>> > full-duplex
>> >
>> > interface FastEthernet0/0.23
>> > encapsulation dot1Q 23
>> > ip address 192.168.23.2 255.255.255.0
>> >
>> > R3
>> > interface FastEthernet0/0
>> > no ip address
>> > speed 100
>> > full-duplex
>> >
>> > interface FastEthernet0/0.23
>> > encapsulation dot1Q 23
>> > ip address 192.168.23.3 255.255.255.0
>> >
>> > R1
>> > router ospf 1
>> > router-id 1.1.1.1
>> > network 1.1.1.1 0.0.0.0 area 0
>> > network 192.168.101.1 0.0.0.0 area 0
>> >
>> > interface FastEthernet1/0
>> > ip address 192.168.101.1 255.255.255.0
>> > speed 100
>> > duplex full
>> > mpls ip
>> > mpls mtu 1514
>> >
>> > interface FastEthernet1/1
>> > no ip address
>> > speed 100
>> > duplex full
>> >
>> > interface FastEthernet1/1.23
>> > encapsulation dot1Q 23
>> > xconnect 10.10.10.10 23 encapsulation mpls pw-class MSSK
>> >
>> > pseudowire-class MSSK
>> > encapsulation mpls
>> > interworking vlan
>> > no control-word
>> >
>> > J1
>> > set version 12.1R1.9
>> > set system root-authentication encrypted-password cisco123 set system
>> syslog
>> > user * any emergency set system syslog file messages any notice set
>> system
>> > syslog file messages authorization info set system syslog file
>> > interactive-commands interactive-commands any set interfaces em0 mtu
>> 1514
>> > set interfaces em0 unit 0 family inet address 192.168.101.10/24 set
>> > interfaces em0 unit 0 family mpls mtu 1500 set interfaces em1
>> vlan-tagging
>> > set interfaces em1 unit 23 encapsulation vlan-ccc set interfaces em1
>> unit 23
>> > vlan-id 23 set interfaces em1 unit 23 family ccc set interfaces lo0
>> unit 0
>> > family inet address 10.10.10.10/32 set protocols mpls interface em0.0
>> set
>> > protocols mpls interface lo0.0 set protocols ospf area 0.0.0.0 interface
>> > em0.0 set protocols ospf area 0.0.0.0 interface lo0.0 set protocols ldp
>> > interface em0.0 set protocols ldp interface lo0.0 set protocols
>> l2circuit
>> > neighbor 1.1.1.1 interface em1.23 virtual-circuit-id 23 set protocols
>> > l2circuit neighbor 1.1.1.1 interface em1.23 mtu 1500 set protocols
>> l2circuit
>> > neighbor 1.1.1.1 interface em1.23 encapsulation-type ethernet-vlan set
>> > protocols l2circuit neighbor 1.1.1.1 interface em1.23
>> > ignore-encapsulation-mismatch set protocols l2circuit neighbor 1.1.1.1
>> > interface em1.23 ignore-mtu-mismatch
>> >
>> > R1#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 pri ac Fa1/1.23:23(Eth VLAN) UP mpls 10.10.10.10:23
>> > UP
>> >
>> > R1#sh mpls l2transport vc 23 detail
>> > Local interface: Fa1/1.23 up, line protocol up, Eth VLAN 23 up
>> > Destination address: 10.10.10.10, VC ID: 23, VC status: up
>> > Output interface: Fa1/0, imposed label stack {299776}
>> > Preferred path: not configured
>> > Default path: active
>> > Next hop: 192.168.101.10
>> > Create time: 00:09:08, last status change time: 00:09:08
>> > Last label FSM state change time: 00:09:08
>> > Signaling protocol: LDP, peer 10.10.10.10:0 up
>> > Targeted Hello: 1.1.1.1(LDP Id) -> 10.10.10.10, 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 BFD dataplane status rcvd: Not sent
>> > Last BFD peer monitor status rcvd: No fault
>> > Last local AC circuit status rcvd: No fault
>> > Last local AC circuit status sent: No fault
>> > Last local PW i/f circ status rcvd: 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 19, remote 299776
>> > Group ID: local 0, remote 0
>> > MTU: local 1500, remote 1500
>> > Remote interface description:
>> > Remote VLAN id: 23
>> > Sequencing: receive disabled, send disabled
>> > Control Word: Off
>> > Dataplane:
>> > SSM segment/switch IDs: 4112/4109 (used), PWID: 1
>> > VC statistics:
>> > transit packet totals: receive 0, send 5
>> > transit byte totals: receive 0, send 410
>> > transit packet drops: receive 0, seq error 0, send 0
>> >
>> > R2#ping 192.168.23.3
>> >
>> > Type escape sequence to abort.
>> > Sending 5, 100-byte ICMP Echos to 192.168.23.3, timeout is 2 seconds:
>> > .....
>> > Success rate is 0 percent (0/5)
>> >
>> > Thanks
>> >
>> > BR,
>> > Mohammad
>> >
>> >
>> >
>> > _______________________________________________
>> > cisco-nsp mailing list cisco-nsp at puck.nether.net
>> > https://puck.nether.net/mailman/listinfo/cisco-nsp
>> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>> >
>>
>>

More information about the cisco-nsp mailing list