Original Message:
Sent: 10-10-2023 13:39
From: derek.summitt
Subject: l2circuit one way traffic
Can you do a show route for your loopback addresses of your neighbors and provide the different route tables it shows up in? You should see it in the inet.0, inet.3 . Can you do that on both sides? Can you ping your loopbacks without doing the MPLS ping?
Can you provide the configuration on the ge-0/0/47.0 interface?
I think your latest commands were coming from the other side opposed to the earlier post with the route tables because it looks like the Labels aren't lining up with your ping "detail" output. which makes sense if it's coming from the other side of the connection.
> show route 10.224.1.7 (Loopback Address )
inet.0: XXX destinations, XXX routes (XXX active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.224.1.7/32 *[IS-IS/18] 7w6d 13:01:43, metric 110
> to 172.X.X.X via ge-0/0/23.0
inet.3: XXX destinations, XXX routes (XXX active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.224.1.7/32 *[LDP/9] 7w6d 13:01:43, metric 110
> to 172.X.X.X via ge-0/0/23.0, Push 68171
> show route table mpls protocol l2circuit
mpls.0: XXX destinations, XXX routes (XXX active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
17 *[L2CKT/7] 11w5d 11:40:48
> via ge-0/0/0.0, Pop
ge-0/0/0.0 *[L2CKT/7] 7w6d 13:04:31, metric2 110
> to 172.XX.X.X via ge-0/0/23.0, Push 19, Push 68171(top)
When we look at the L2circuit connection we need to make sure all the labels are lining up properly and associating with the right interfaces.
Neighbor: 10.224.1.7
Interface Type St Time last up # Up trans
ge-0/0/0.0(vc 114) rmt Up Jul 20 01:42:33 2023 1
Remote PE: 10.224.1.7, Negotiated control-word: No
Incoming label: 17, Outgoing label: 19
Negotiated PW status TLV: No
Local interface: ge-0/0/0.0, Status: Up, Encapsulation: ETHERNET
Flow Label Transmit: No, Flow Label Receive: No
This Interface ID here should the logical interface that has MPLS on it in your configuration and it should
> ping mpls l2circuit virtual-circuit XXX neighbor 10.224.1.7 detail
Request for seq 1, to interface 560, labels <19, 1, 68171>, packet size 88
Reply for seq 1, return code: Egress-ok, time: 24.557 ms
Local transmit time: 2023-10-10 13:16:15 EDT 457.192 ms
Remote receive time: 2023-10-10 13:16:15 EDT 481.749 ms
Do you have active support with Juniper to have them look at this with ya through a JTAC case?
------------------------------
Derek Summitt
Original Message:
Sent: 10-09-2023 09:55
From: Grzegorz Dacka
Subject: l2circuit one way traffic
Hello
Thx for replay
# run ping mpls l2circuit virtual-circuit 200 neighbor 100.100.12.4 source 100.100.12.1
.....
--- lsping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
#run ping mpls l2circuit virtual-circuit 200 neighbor 100.100.12.4 source 100.100.12.1 detail
Request for seq 1, to interface 572, labels <28, 1>, packet size 88
Request for seq 2, to interface 572, labels <28, 1>, packet size 88
Request for seq 3, to interface 572, labels <28, 1>, packet size 88
Timeout for seq 1
Request for seq 4, to interface 572, labels <28, 1>, packet size 88
Timeout for seq 2
Request for seq 5, to interface 572, labels <28, 1>, packet size 88
Timeout for seq 3
Timeout for seq 4
Timeout for seq 5
--- lsping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
#run show configuration system |match default
default-address-selection;
{master:0}[edit]
So this is not this
One curiosity on hosts connected to ports on one side and on the other side and in fact on one host I can see the mac address of the other side but it is only visible on one host on the other not anymore ;(
------------------------------
--
Grzegorz Dacka
Original Message:
Sent: 10-09-2023 09:46
From: derek.summitt
Subject: l2circuit one way traffic
Try to add a "source address" to your ping statement.
If you don't have the configuration set to source all traffic from the control plane/loopback it could be using a different Interface IP address.
so run ping mpls l2circuit virtual-circuit 200 neighbor 100.100.12.1 source 100.100.12.4
If this works then I would guess that you might be missing this configuration line on your devices.
set system default-address-selection
Original Message:
Sent: 10/9/2023 2:56:00 AM
From: Grzegorz Dacka
Subject: RE: l2circuit one way traffic
Hello
Anyone is able to help ? Suggest where to look for the problem ?
------------------------------
--
Grzegorz Dacka
Original Message:
Sent: 10-06-2023 15:17
From: Grzegorz Dacka
Subject: l2circuit one way traffic
Hello
My config is very simple
#show configuration interfaces xe-0/0/0
description "LINK SQD";
flexible-vlan-tagging;
mtu 9216;
encapsulation flexible-ethernet-services;
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members MGMT;
}
}
}
unit 194 {
vlan-id 194;
family inet {
address 172.16.17.238/30;
}
family mpls;
}
run show configuration protocols ospf
area 0.0.0.0 {
interface lo0.0 {
passive;
}
interface xe-0/0/0.194;
}
export export-ospf;
import import-ospf;
# run show configuration protocols bgp
inactive: group eVPN {
type internal;
local-address 100.100.12.4;
family evpn {
signaling;
}
local-as 65300;
multipath;
bfd-liveness-detection {
minimum-interval 1500;
minimum-receive-interval 1500;
multiplier 3;
}
neighbor 100.100.12.1;
}
# run show configuration interfaces lo0
unit 0 {
family inet {
address 100.100.12.4/32;
}
}
#show protocols l2circuit
neighbor 100.100.12.1 {
interface ge-0/0/47.0 {
virtual-circuit-id 200;
description "SQD";
no-control-word;
ignore-mtu-mismatch;
}
}
#run show ospf neighbor
Address Interface State ID Pri Dead
172.16.17.237 xe-0/0/0.194 Full 100.100.12.1 128 36
# run show ldp neighbor
Address Interface Label space ID Hold time
100.100.12.1 lo0.0 100.100.12.1:0 34
172.16.17.237 xe-0/0/0.194 100.100.12.1:0 12
# run show mpls interface
Interface State Administrative groups (x: extended)
xe-0/0/0.194 Up <none>
# run show route table l2circuit.0
l2circuit.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
100.100.12.1:NoCtrlWord:5:200:Local/96
*[L2CKT/7] 05:14:20, metric2 1
> to 172.16.17.237 via xe-0/0/0.194
100.100.12.1:NoCtrlWord:5:200:Remote/96
*[LDP/9] 05:21:07
Discard
# run show route table mpls.0
mpls.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
0 *[MPLS/0] 12:56:18, metric 1
Receive
1 *[MPLS/0] 12:56:18, metric 1
Receive
2 *[MPLS/0] 12:56:18, metric 1
Receive
13 *[MPLS/0] 12:56:18, metric 1
Receive
26 *[LDP/9] 05:22:40, metric 1
> to 172.16.17.237 via xe-0/0/0.194, Pop
26(S=0) *[LDP/9] 05:22:40, metric 1
> to 172.16.17.237 via xe-0/0/0.194, Pop
27 *[LDP/9] 05:22:40, metric 1
> to 172.16.17.237 via xe-0/0/0.194, Swap 18
28 *[L2CKT/7] 05:15:53
> via ge-0/0/47.0, Pop
ge-0/0/47.0 *[L2CKT/7] 05:15:53, metric2 1
> to 172.16.17.237 via xe-0/0/0.194, Push 17
# run show l2circuit connections extensive
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: 100.100.12.1
Interface Type St Time last up # Up trans
ge-0/0/47.0(vc 200) rmt Up Oct 6 15:58:22 2023 1
Remote PE: 100.100.12.1, Negotiated control-word: No
Incoming label: 28, Outgoing label: 17
Negotiated PW status TLV: No
Local interface: ge-0/0/47.0, Status: Up, Encapsulation: ETHERNET
Description: SQD
Flow Label Transmit: No, Flow Label Receive: No
Connection History:
Oct 6 15:58:22 2023 PE route changed
Oct 6 15:58:22 2023 Out lbl Update 17
Oct 6 15:58:22 2023 In lbl Update 28
Oct 6 15:58:22 2023 loc intf up ge-0/0/47.0
# run ping mpls l2circuit virtual-circuit 200 neighbor 100.100.12.1
.....
--- lsping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
Like U see nothing special in configuartion
Any idea ?
Can you share You full config (can be in private message)
------------------------------
--
Grzegorz Dacka
Original Message:
Sent: 10-06-2023 11:14
From: derek.summitt
Subject: l2circuit one way traffic
What does your configuration look like? I had these problems on our EX4600 devices and we noticed that our packets were getting "corrupted" after certain time periods and even though it had no "control word" setup it started shoving parts of the packet into the Control Word header and then it made the packet malformed and the other end didn't know how to process it once the packet had all the labels popped.
We fixed this by actually configuring no-control-word specifically in our configuration and we have never seen the issue arise again.
show configuration protocols l2circuit
neighbor 10.1.1.1 {
interface ge-0/0/1.0 {
virtual-circuit-id 118;
no-control-word;
mtu 1950;
}
}
------------------------------
Derek Summitt
Original Message:
Sent: 10-05-2023 17:17
From: Grzegorz Dacka
Subject: l2circuit one way traffic
Hello
I have some problem with l2circuit on QFX5100 one way traffic maybe some can help me
In general, the problem is that the lack of traffic in the tunnel itself, that is, devices connected to ports 0/47 are not able to ping
Both switch Junos: 19.1R3.9
Switcha A
run ping mpls l2circuit virtual-circuit 200 neighbor 100.100.12.4
!!!!!
--- lsping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
Neighbor: 100.100.12.4
Interface Type St Time last up # Up trans
ge-0/0/47.0(vc 200) rmt Up Oct 5 22:45:31 2023 1
Remote PE: 100.100.12.4, Negotiated control-word: No
Incoming label: 19, Outgoing label: 18
Negotiated PW status TLV: No
Local interface: ge-0/0/47.0, Status: Up, Encapsulation: ETHERNET
Description: SQD
Flow Label Transmit: No, Flow Label Receive: No
Switch B
run ping mpls l2circuit virtual-circuit 200 neighbor 100.100.12.1
.....
--- lsping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
Neighbor: 100.100.12.1
Interface Type St Time last up # Up trans
ge-0/0/47.0(vc 200) rmt Up Oct 5 23:04:06 2023 1
Remote PE: 100.100.12.1, Negotiated control-word: No
Incoming label: 18, Outgoing label: 19
Negotiated PW status TLV: No
Local interface: ge-0/0/47.0, Status: Up, Encapsulation: ETHERNET
Description: SQD
Flow Label Transmit: No, Flow Label Receive: No
If you need more information ask
------------------------------
--
Grzegorz Dacka
------------------------------