Hi,
On 26.01.22 00:19, Chris Adams via juniper-nsp wrote:
Still don't see any incoming v6 VRRP from the other router. I also
checked on a host on the VLAN and only see the v4 VRRP, not the v6.
You may have hit the following PR. PR1449014 ([vMX] Different MAC
address used for IPv6 in VRRP[3
Hi Leon,
both MX204 und MX10003/LC2103 use
eagle forwarding ASIC, LC2103 Linecard has 3xASIC,
MX204 has 1xASIC, WAN Output Rate for eagle
pfe is for 100G Interface ~110 MPPS.
Assumption is, that you got the traffic on the
MX10003 over more than one PFE/ASIC incoming.
BR,
.peter
On 20.05.21 11
Hi Alex,
Am 19.04.2018 um 14:48 schrieb Alex D.:
If yes, try to deactivate CNH for family evpn ingress,
I didn't configure chained-composite-nexthop explicitely, because it is
activated by junos-defaults. How can i deactivate it in this case ?
# set routing-option forwarding-table chained-co
Hi Alex,
Am 18.04.2018 um 23:50 schrieb Alex D.:
Here's an example: VRRP master is attached at PE1. PE2 learns this VRRP
IP via an EVPN type-2 route from PE1. Now, an IP packet for a DMZ host
arrives at PE2 which has a static route pointing to the VRRP IP. PE2
doesn't label-switch the IP ipack
Hi,
Am 01.03.2017 um 15:16 schrieb Valentini, Lucio:
Any clue?
EX2300 and EX3400 are not supporting LFM, CFM at FRS.
.peter
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Hi,
Am 13.10.2015 um 14:59 schrieb Adam Vitkovsky:
Reading the SW features
For example “Chained composite next hops” -these are there since ever so
what’s changed
And the rest of the stuff like ”Layer 3 VPN localization” (is going to be the
same fun as SVD on XR) are all of those only avail
Sorry, fat Fingers.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Hi,
On 01.07.2014 08:29, Joerg Staedele wrote:
> Hi there,
>
> it now happened the 2nd time that during a "request system snapshot" the
> whole box (MX80 with JunOS 11.4R6) crashed and rebooted. The log showed:
>
> Jul 1 00:30:52 cr0 /kernel: umass0: at uhub0 port 3 (addr 2) disconnected
> Ju
Hi,
> it now happened the 2nd time that during a "request system snapshot" the
> whole box (MX80 with JunOS 11.4R6) crashed and rebooted. The log showed:
have a look at PR603468,
Title: MX80: System crashed after using system snapshot multiple times
resulting in DA0 corruption and stuck during
Hi,
On 01.07.2014 08:29, Joerg Staedele wrote:
> Anyone else have seen this problem? I guess that I have to RMA the box :/
yes and no, you have to update the box.
Have a look at PR603468,
Title MX80: System crashed after using system snapshot multiple times
resulting in DA0 corruption and stu
10 matches
Mail list logo