Re: [j-nsp] IPv4 BFD flaps on MX204

If you have many uncontrolled directly connected L2 domains like IX-es or customers, check policer __default_arp_policer__. If there are drops, you need to apply interface-specific arp policers to interfaces with protocols and/or to source of arp bursts. 18.08.2020 02:35, Mihai пишет: Hi,

Re: [j-nsp] source address selection for RE generated traffic addresses to direct neighbors

Look at default-address-selection option description: https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/junos-software-system-management-source-address-local-tcp-ip-packets-configuring.html For IPv4: If this option is not enabled, and destination is directly connected

Re: [j-nsp] Mpls down qfx 5100

Remember that on QFX platform some protocols shares same queue and policers. When you got routing loops and TTL=0 packets excceeds its ddos detection limits, also l3mtu-fail will be false triggered. PR1211911 Some DDOS protocols shares same hardware policer The following control packets share

Re: [j-nsp] "set routing-options protect core" breaks local-preference

Hi. We also find something wrong with "protect core". Seems like Junos 18.1 and 18.2 (running on MX204 in our case) makes one #Multipath equal-cost group with ALL paths except one worst AND one with worst path - as backup. I think it must create #Multipath forwarding-only route with one best

[j-nsp] EX3300, redundant-trunk-group and SNMP

Hi, I use feature "redundant-trunk-group" on EX3300 stack. It is working OK, and i can check status of Active/Backup interfaces in CLI with show redundant-trunk-group : > show redundant-trunk-group Group name Interface State Time of last flap Flap count uplink xe-0/1/1.0