Re: [j-nsp] LACP hashing algorithm

I am assuming the traffic has MPLS labels, yes?? On 8/9/18, 7:17 AM, "Luis Balbinot" wrote: How many flows are there in total? Is there a test appliance involved? We had many issues with those in the past during service delivery tests. Also I assume you are using MPCs and not

Re: [j-nsp] LACP hashing algorithm

Have you tried load-balance adaptive? set interfaces aeX aggregated-ether-options load-balance adaptive tolerance 10 Regards, 2018-08-08 20:32 GMT-03:00 junos fordummies via juniper-nsp : > Hi all, > > This will sound like a very weird question, but has anyone seen a scenario > whereby an

Re: [j-nsp] Convergence time

Hi, On Thu, Aug 09, 2018 at 09:36:46AM +0200, Melchior Aelmans wrote: > MX5 might not be the ideal platform handling multiple full table BGP > sessions. This is due to it's somewhat slower CPU compared to other MX > routers. "abysmally and close to useless slow" describes the "somewhat slower"

Re: [j-nsp] BGP session - code 6 (Cease) subcode 4 (Administratively Reset)

Hi,The code 6 Notification message in BGP means that the bgp session has been cleared by a user.When you manuallyclear a BGP connection, you generate a Cease (Error Code 6) Notification message on thelocal router.Even a configurationchange that alters the parameters of an existing session will

Re: [j-nsp] LACP hashing algorithm

How many flows are there in total? Is there a test appliance involved? We had many issues with those in the past during service delivery tests. Also I assume you are using MPCs and not DPCs and also that you are talking about IP traffic. Please correct me if not. Luis On Wed, 8 Aug 2018 at

Re: [j-nsp] LACP hashing algorithm

Yes, have seen this, but need to check how we resolved this. Will get back to you. On 8/8/18, 7:32 PM, "junos fordummies" wrote: Hi all, This will sound like a very weird question, but has anyone seen a scenario whereby an MX960 with 4 x 10G links always hashes (uses) a

[j-nsp] BGP session - code 6 (Cease) subcode 4 (Administratively Reset)

Hi all, we have a VC of two EX4200-24T running. We have BGP sessions (each IPv4 and IPv6, default route only) running on each member to different upstreams. Periodically we are seeing in var/log/messages on only one IPv4 session code 6 (Cease) subcode 4 (Administratively Reset) A "show bgp

Re: [j-nsp] Convergence time

MX80 (5-10-40) is a very old platform with a cpu less powerful than your cell phone. 2-3 minutes seems to be a very good performance for this platform :) I had a customer with 2* MX80 with peering and 4 full feed (95% or ram used !), and I have seen more than 8 minutes during a flap.

Re: [j-nsp] Convergence time

Hi Dovid, MX5 might not be the ideal platform handling multiple full table BGP sessions. This is due to it's somewhat slower CPU compared to other MX routers. You might want to limit the amount of full table or flapping sessions or get yourself another platform. For example MX150 or 204 wouldn't