Re: [j-nsp] rate limiting per-user prefix lists

2019-01-14 Thread mike+j...@willitsonline.com
On 1/9/19 6:14 AM, Niall Donaghy wrote: > Hi Mike, > > I can give you a few hints: > > DPCE will perform poorly, depending on how many policers you > instantiate. > (hint: 10K will kill it, and hint: policers will not be accurate). > MPCs will perform better but don't burden more than

Re: [j-nsp] rate limiting per-user prefix lists

2019-01-14 Thread mike+jnsp
On 1/9/19 7:37 AM, Alexander Arseniev via juniper-nsp wrote: > Hello, > > Well, the prefix-action policers would likely relieve congestion on > Your backhaul MW links but the 100Mbps "last mile" will still be > congested, with a mix of good and bad packets. > > And I would say more bad than good be

Re: [j-nsp] Change in host-name / domain-name behaviour - LLDP System Name / SNMP sysName

2019-01-14 Thread James Stapley
A dirty hack to move behaviour back to expected is to put the host-name in as a FQDN and delete domain-name. Seems not to affect anything else (domain-search helps resolution of naked hostnames in commands), and both LLDP and SNMP report the same value. On Mon, 14 Jan 2019 at 12:56, James Stapley

[j-nsp] Change in host-name / domain-name behaviour - LLDP System Name / SNMP sysName

2019-01-14 Thread James Stapley
Not sure if we're the first people to notice this, but there seems to be a change in the way Junos deals with FQDN, host-name and domain-name with our latest kit. tl;dr: On MX204, running 18.1R3-S2.5, LLDP System Name and SNMP sysName are not consistent, with LLDP System name having the domain-nam