Hi Andrei, thank you for the message.
Original Message:
Sent: 07-05-2024 05:54
From: Andrei Cebotareanu
Subject: LDP via v6. v4 routes are not learned. Juniper/Nokia
Hi,
Did you see this documents
- https://www.juniper.net/documentation/us/en/software/junos/mpls/topics/topic-map/ldp-overview.html#id-ldp-native-ipv6-support-overview
You can configure the address family as inet for IPv4 or inet6 for IPv6, or both. If the family address is not configured, then the default address of family inet is enabled. When both IPv4 and IPv6 are configured, you can use the transport-preference statement to configure the prefered transport to be either IPv4 or IPv6. Based on the preference, LDP attempts to establish a TCP connection using IPv4 or IPv6. By default, IPv6 is selected. The dual-transport statement allows Junos OS LDP to establish the TCP connection over IPv4 with IPv4 neighbors, and over IPv6 with IPv6 neighbors as a single-stack LSR. The inet-lsr-id and inet6-lsr-id IDs are the two LSR IDs that have to be configured to establish an LDP session over IPv4 and IPv6 TCP transport. These two IDs should be non-zero and must be configured with different values.
- https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/dual-transport-edit-protocols-ldp.html
Configure to allow Junos LDP to establish the TCP connection over IPv4 with IPv4 neighbors, and over IPv6 with IPv6 neighbors as a single-stack LSR. inet-lsr-id and inet6-lsr-id are the two LSR IDs that have to be configured to establish an LDP session over IPv4 and IPv6 TCP transport. These two IDs should be non-zero and must be configured with different values.
BR,
Andrei
------------------------------
Andrei Cebotareanu
Original Message:
Sent: 07-01-2024 14:10
From: TobsA
Subject: LDP via v6. v4 routes are not learned. Juniper/Nokia
Hello Community,
I try at the moment so switch some of our backbone to LDP/MPLS. The problem that I have at the moment is that only the routes of the same IP version as the LDP transport protocol a learned. So if I am using v4 as transport the v4 LDP routes are learned and vice versa.
The LDP session is created between a Juniper and Nokia router. On the Nokia router it does not matter if I use v4 or v6, I have the LDP routes for both continuously.
Has anyone seen anything like this or has a tip?
transport-preference ipv6:
tobsa@mpls-test> show ldp database Input label database, 198.51.100.203:0--203.0.113.210:0Labels received: 3 Label Prefix 3 192.0.2.248/321048560 198.51.100.202/321048563 2001:DB8:0:e0c0::b11b/128 3 2001:DB8:0:e0c0::b12c/128Output label database, 198.51.100.203:0--203.0.113.210:0Labels advertised: 3 Label Prefix 3 198.51.100.203/32 3 2001:DB8:0:e0c0::b11a/128 55 2001:DB8:0:e0c0::b11b/128 56 2001:DB8:0:e0c0::b12c/128{master:0}tobsa@mpls-test> show route protocol ldp inet.0: 738 destinations, 739 routes (738 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both224.0.0.2/32 *[LDP/9] 05:27:39, metric 1 MultiRecvinet.2: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden)inet.3: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden)mpls.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both55 *[LDP/9] 02:07:19, metric 1 > to fe80::9ee0:41ff:fe5c:a169 via ae0.10, Swap 104856356 *[LDP/9] 02:07:19, metric 1 > to fe80::9ee0:41ff:fe5c:a169 via ae0.10, Pop 56(S=0) *[LDP/9] 02:07:19, metric 1 > to fe80::9ee0:41ff:fe5c:a169 via ae0.10, Pop inet6.0: 403 destinations, 405 routes (403 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Bothff02::2/128 [LDP/9] 05:27:39, metric 1 MultiRecvinet6.2: 17 destinations, 17 routes (17 active, 0 holddown, 0 hidden)inet6.3: 19 destinations, 19 routes (19 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both2001:DB8:0:e0c0::b11b/128 *[LDP/9] 02:07:19, metric 16 > to fe80::9ee0:41ff:fe5c:a169 via ae0.10, Push 10485632001:DB8:0:e0c0::b12c/128 *[LDP/9] 02:07:19, metric 1 > to fe80::9ee0:41ff:fe5c:a169 via ae0.10
{master:0}[edit]tobsa@mpls-test# show | compare [edit protocols ldp]- transport-preference ipv6;+ transport-preference ipv4;
transport-preference ipv4:
tobsa@mpls-test> show ldp database Input label database, 198.51.100.203:0--192.0.2.248:0Labels received: 3 Label Prefix 3 192.0.2.248/321048560 198.51.100.202/321048563 2001:DB8:0:e0c0::b11b/128 3 2001:DB8:0:e0c0::b12c/128Output label database, 198.51.100.203:0--192.0.2.248:0Labels advertised: 3 Label Prefix 61 192.0.2.248/32 62 198.51.100.202/32 3 198.51.100.203/32 3 2001:DB8:0:e0c0::b11a/128{master:0}tobsa@mpls-test> show route protocol ldpinet.0: 738 destinations, 739 routes (738 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both224.0.0.2/32 *[LDP/9] 05:30:37, metric 1 MultiRecvinet.2: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden)inet.3: 13 destinations, 13 routes (13 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both192.0.2.248/32 *[LDP/9] 00:02:00, metric 1 > to 203.0.113.210 via ae0.10198.51.100.202/32 *[LDP/9] 00:02:00, metric 16 > to 203.0.113.210 via ae0.10, Push 1048560mpls.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both61 *[LDP/9] 00:02:00, metric 1 > to 203.0.113.210 via ae0.10, Pop 61(S=0) *[LDP/9] 00:02:00, metric 1 > to 203.0.113.210 via ae0.10, Pop 62 *[LDP/9] 00:02:00, metric 1 > to 203.0.113.210 via ae0.10, Swap 1048560inet6.0: 403 destinations, 405 routes (403 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Bothff02::2/128 [LDP/9] 05:30:37, metric 1 MultiRecvinet6.2: 17 destinations, 17 routes (17 active, 0 holddown, 0 hidden)inet6.3: 19 destinations, 19 routes (19 active, 0 holddown, 0 hidden)+ = Active Route, - = Last Active, * = Both::ffff:192.0.2.248/128 *[LDP/9] 00:02:00, metric 1 > to 203.0.113.210 via ae0.10::ffff:198.51.100.202/128 *[LDP/9] 00:02:00, metric 16 > to 203.0.113.210 via ae0.10, Push 1048560
------------------------------
TobsA
------------------------------