Andrey Kostin писал(а) 2024-07-23 16:27:
Andrey Kostin via juniper-nsp писал(а) 2024-07-09 10:10:
Correction, rib-group with policy is used to copy received prefixes to
inet6.0 on in-line route-reflectors.
For off-ramp RRs to place prefixes into inet6.3 it's enough to configure
this:
set prot
Andrey Kostin via juniper-nsp писал(а) 2024-07-09 10:10:
[...]
The problem here is that route-reflector selects a path with ipv4
mapped
nexthop and advertises it over ipv6 session. I'm wondering, is
anybody
already encountered this problem and found a solution how to make a
RR
to advertise p
Alexandre Snarskii писал(а) 2024-07-09 07:25:
On Mon, Jul 08, 2024 at 11:33:48AM -0400, Andrey Kostin via juniper-nsp
wrote:
[...]
The problem here is that route-reflector selects a path with ipv4
mapped
nexthop and advertises it over ipv6 session. I'm wondering, is anybody
already encountered
On Mon, Jul 08, 2024 at 11:33:48AM -0400, Andrey Kostin via juniper-nsp wrote:
[...]
> The problem here is that route-reflector selects a path with ipv4 mapped
> nexthop and advertises it over ipv6 session. I'm wondering, is anybody
> already encountered this problem and found a solution how to m
Hi juniper-nsp readers,
Recently we encountered an issue with L3-incompletes counters started
incrementing on internal backbone links. It began after adding new PE,
core routers and route-reflectors.
After quite long investigation with TAC involved the problem was
identified: v6 traffic was
5 matches
Mail list logo
