[j-nsp] l2circuit between QFX-5110 & MX204 - one way traffic
Alain Hebert
ahebert at pubnix.net
Thu Jul 18 10:17:11 EDT 2019
Here is an production version (thx Phil) but on QFX-5100 and MX960
(and MX104 before).
This works for about 200ish circuits so far...
We had a bunch of issue with those which can lead to unresponsive
interface... So depending on your situation you may have to reboot the
switch :(
xe-<snip> {
description <snip>
flexible-vlan-tagging;
mtu 9216;
encapsulation flexible-ethernet-services;
unit 123 {
description <snip>
encapsulation vlan-ccc;
no-traps;
vlan-id 123;
input-vlan-map pop;
output-vlan-map push;
}
....
interface xe-<snip>.123 {
virtual-circuit-id 123456;
description <snip>
no-control-word;
mtu 9000;
}
-----
Alain Hebertahebert at pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911http://www.pubnix.net Fax: 514-990-9443
On 2019-07-18 10:02, Heng Chai, Tan wrote:
> Try below on QFX5110 terminating l2circuit. Last I remember the
> flexible-vlan-tagging + flexible-ethernet-services behaves oddly on
> the QFX5110.
>
> delete interfaces xe-0/0/9 flexible-vlan-tagging
> set interfaces xe-0/0/9 vlan-tagging
> set interfaces xe-0/0/9 encapsulation vlan-ccc
>
> Heng Chai, Tan
>
> On 18-07-19 9:48 PM, Liam Farr wrote:
>> Hi,
>>
>> Not sure if I'm "doing the dumb" or Junos bug or limitation of the QFX /
>> Trident 2+ chip-set.
>>
>> Trying to do a basic l2circuit as follows
>>
>> VLAN Tagged Interface > MX204 l2circuit / ldp > QFX-5110 / ldp >
>> QFX-5110
>> l2circuit / ldp > VLAN Tagged Interface
>>
>> What I am seeing is traffic going Test Device > QFX-5110 > QFX-5110 >
>> MX204
>>> Test Device arrives fine.
>> Return path from Test Device > MX204 > QFX-5110 > QFX-5110 > Test
>> Device is
>> broken.
>>
>>
>> Config is as follows
>>
>> *MX204 Port facing test device on VLAN tag 123*
>>
>> liam at WN-MX204-1# show interfaces xe-0/1/3
>> description "WN-PVE-1 C0/F3 enp6s0f1";
>> flexible-vlan-tagging;
>> mtu 9216;
>> encapsulation flexible-ethernet-services;
>> unit 123 {
>> encapsulation vlan-ccc;
>> vlan-id 123;
>> family ccc;
>> }
>>
>> MPLS port facing intermediate / transit QFX (MS)
>>
>> liam at WN-MX204-1# show interfaces xe-0/1/1
>> description "OTN MS";
>> mtu 9216;
>> unit 0 {
>> family inet {
>> address 172.16.130.2/30;
>> }
>> family mpls;
>> }
>>
>> liam at WN-MX204-1# show interfaces lo0
>> unit 0 {
>> family inet {
>> address 127.0.0.1/32;
>> address 192.168.68.3/32;
>> }
>> }
>>
>> liam at WN-MX204-1# show protocols l2circuit
>> neighbor 192.168.68.5 {
>> interface xe-0/1/3.123 {
>> virtual-circuit-id 123;
>> control-word;
>> encapsulation-type ethernet-vlan;
>> ignore-mtu-mismatch;
>> pseudowire-status-tlv;
>> }
>> }
>>
>> liam at WN-MX204-1# show protocols ldp
>> interface xe-0/1/1.0;
>> interface lo0.0;
>>
>> liam at WN-MX204-1# show protocols mpls
>> path-mtu {
>> rsvp mtu-signaling;
>> }
>> ipv6-tunneling;
>> icmp-tunneling;
>> optimize-timer 60;
>> label-switched-path wn-mx-to-na-qfx-test {
>> from 192.168.68.3;
>> to 192.168.68.5;
>> adaptive;
>> fast-reroute;
>> primary anypath;
>> }
>> path anypath;
>> interface xe-0/1/1.0;
>>
>> liam at WN-MX204-1# show protocols ospf
>> traffic-engineering;
>> area 0.0.0.0 {
>> interface lo0.0 {
>> passive;
>> }
>> interface fxp0.0 {
>> disable;
>> }
>> interface xe-0/1/0.549 {
>> interface-type p2p;
>> }
>> interface xe-0/1/1.0 {
>> interface-type p2p;
>> }
>> }
>>
>>
>> *Intermediate / transit QFX*, MPLS interface facing MX204
>>
>> liam at MS-QFX5110-1# show interfaces xe-0/0/1
>> description "OTN MS-WN";
>> mtu 9216;
>> unit 0 {
>> family inet {
>> address 172.16.130.1/30;
>> }
>> family mpls;
>> }
>>
>> Interface facing destination QFX
>>
>> liam at MS-QFX5110-1# show interfaces xe-0/0/0
>> description "OTN MS-NA";
>> mtu 9216;
>> unit 0 {
>> family inet {
>> address 172.16.130.5/30;
>> }
>> family mpls;
>> }
>>
>> liam at MS-QFX5110-1# show interfaces lo0
>> unit 0 {
>> family inet {
>> address 127.0.0.1/32;
>> address 192.168.68.6/32;
>> }
>> }
>>
>> liam at MS-QFX5110-1# show protocols ldp
>> interface xe-0/0/0.0;
>> interface xe-0/0/1.0;
>> interface lo0.0;
>>
>> liam at MS-QFX5110-1# show protocols mpls
>> path-mtu {
>> rsvp mtu-signaling;
>> }
>> ipv6-tunneling;
>> icmp-tunneling;
>> optimize-timer 60;
>> path anypath;
>> interface xe-0/0/0.0;
>> interface xe-0/0/1.0;
>>
>> liam at MS-QFX5110-1# show protocols ospf
>> traffic-engineering;
>> area 0.0.0.0 {
>> interface lo0.0 {
>> passive;
>> }
>> interface vme.0 {
>> disable;
>> }
>> interface xe-0/0/0.0 {
>> interface-type p2p;
>> }
>> interface xe-0/0/1.0 {
>> interface-type p2p;
>> }
>> }
>>
>>
>> *Destination QFX / other end of l2circuit*, interfacing test
>> equipment on
>> vlan 123
>>
>> liam at NA-QFX5110-1# show interfaces xe-0/0/9
>> description "Temp Link to Arista";
>> flexible-vlan-tagging;
>> mtu 9216;
>> encapsulation flexible-ethernet-services;
>> unit 123 {
>> encapsulation vlan-ccc;
>> vlan-id 123;
>> family ccc;
>> }
>>
>> Interface facing intermediate / transit QFX
>>
>> liam at NA-QFX5110-1# show interfaces xe-0/0/1
>> description "OTN NA-MS";
>> mtu 9216;
>> unit 0 {
>> family inet {
>> address 172.16.130.6/30;
>> }
>> family mpls;
>> }
>>
>> liam at NA-QFX5110-1# show interfaces lo0
>> unit 0 {
>> family inet {
>> address 127.0.0.1/32;
>> address 192.168.68.5/32;
>> }
>> }
>>
>> liam at NA-QFX5110-1# show protocols l2circuit
>> neighbor 192.168.68.3 {
>> interface xe-0/0/9.123 {
>> virtual-circuit-id 123;
>> control-word;
>> encapsulation-type ethernet-vlan;
>> ignore-mtu-mismatch;
>> pseudowire-status-tlv;
>> }
>> }
>>
>> liam at NA-QFX5110-1# show protocols ldp
>> interface xe-0/0/1.0;
>> interface lo0.0;
>>
>> liam at NA-QFX5110-1# show protocols mpls
>> path-mtu {
>> rsvp mtu-signaling;
>> }
>> ipv6-tunneling;
>> icmp-tunneling;
>> optimize-timer 60;
>> label-switched-path na-qfx-to-wn-mx-test {
>> from 192.168.68.5;
>> to 192.168.68.3;
>> adaptive;
>> fast-reroute;
>> primary anypath;
>> }
>> path anypath;
>> interface xe-0/0/1.0;
>>
>> liam at NA-QFX5110-1# show protocols ospf
>> traffic-engineering;
>> area 0.0.0.0 {
>> interface lo0.0 {
>> passive;
>> }
>> interface vme.0 {
>> disable;
>> }
>> interface xe-0/0/0.554 {
>> interface-type p2p;
>> }
>> interface xe-0/0/1.0 {
>> interface-type p2p;
>> }
>> }
>>
>>
>> L2 Circuit is up on the QFX
>>
>> liam at NA-QFX5110-1> show l2circuit connections
>> Layer-2 Circuit Connections:
>>
>> Legend for connection status (St)
>> EI -- encapsulation invalid NP -- interface h/w not present
>> MM -- mtu mismatch Dn -- down
>> EM -- encapsulation mismatch VC-Dn -- Virtual circuit Down
>> CM -- control-word mismatch Up -- operational
>> VM -- vlan id mismatch CF -- Call admission control failure
>> OL -- no outgoing label IB -- TDM incompatible bitrate
>> NC -- intf encaps not CCC/TCC TM -- TDM misconfiguration
>> BK -- Backup Connection ST -- Standby Connection
>> CB -- rcvd cell-bundle size bad SP -- Static Pseudowire
>> LD -- local site signaled down RS -- remote site standby
>> RD -- remote site signaled down HS -- Hot-standby Connection
>> XX -- unknown
>>
>> Legend for interface status
>> Up -- operational
>> Dn -- down
>> Neighbor: 192.168.68.3
>> Interface Type St Time last up #
>> Up trans
>> xe-0/0/9.123(vc 123) rmt Up Jul 18 21:05:02
>> 2019 1
>> Remote PE: 192.168.68.3, Negotiated control-word: Yes (Null)
>> Incoming label: 73, Outgoing label: 95
>> Negotiated PW status TLV: Yes
>> local PW status code: 0x00000000, Neighbor PW status code:
>> 0x00000000
>> Local interface: xe-0/0/9.123, Status: Up, Encapsulation: VLAN
>> Flow Label Transmit: No, Flow Label Receive: No
>>
>> L2 Circuit is up on the MX
>>
>> liam at WN-MX204-1> show l2circuit connections
>> Layer-2 Circuit Connections:
>>
>> Legend for connection status (St)
>> EI -- encapsulation invalid NP -- interface h/w not present
>> MM -- mtu mismatch Dn -- down
>> EM -- encapsulation mismatch VC-Dn -- Virtual circuit Down
>> CM -- control-word mismatch Up -- operational
>> VM -- vlan id mismatch CF -- Call admission control failure
>> OL -- no outgoing label IB -- TDM incompatible bitrate
>> NC -- intf encaps not CCC/TCC TM -- TDM misconfiguration
>> BK -- Backup Connection ST -- Standby Connection
>> CB -- rcvd cell-bundle size bad SP -- Static Pseudowire
>> LD -- local site signaled down RS -- remote site standby
>> RD -- remote site signaled down HS -- Hot-standby Connection
>> XX -- unknown
>>
>> Legend for interface status
>> Up -- operational
>> Dn -- down
>> Neighbor: 192.168.68.5
>> Interface Type St Time last up #
>> Up trans
>> xe-0/1/3.123(vc 123) rmt Up Jul 19 01:03:21
>> 2019 1
>> Remote PE: 192.168.68.5, Negotiated control-word: Yes (Null)
>> Incoming label: 95, Outgoing label: 73
>> Negotiated PW status TLV: Yes
>> local PW status code: 0x00000000, Neighbor PW status code:
>> 0x00000000
>> Local interface: xe-0/1/3.123, Status: Up, Encapsulation: VLAN
>> Flow Label Transmit: No, Flow Label Receive: No
>>
>>
>> On the* MX end test equipment *I can see the MAC address learned from
>> the *QFX
>> end test equipment*, however on the *QFX end test equipment* I cannot
>> see
>> the MAC address of the* MX end test equipment*.
>>
>> The MX's and QFX's are running Junos: 18.4R1-S3.1
>>
>> Not sure if I just have this configured wrong, or a QFX chippie
>> limitation
>> or a Junos bug.
>>
>> Any help / pointers would be appreciated :)
>>
>>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list