Re: [j-nsp] Going Juniper

Hi Mike, An MX104 can certainly give you all those features. Be aware CGNAT needs an MS-MIC and flow exports require a license. You might be able to get the base bundle under $20k but add the extras and it will be over. Mike G On 10 April 2018 at 11:45, wrote: >

Re: [j-nsp] Going Juniper

Hi, On 10/04/2018 9:45 AM, mike+j...@willitsonline.com wrote:     I see there is a terrific amount of used mx104 and mx240 out there and the specs all seem great. What I'm looking to do is have 2x 10g feeds, route bgp, do flow exporting, and do a certain amount of ingress filtering to protect

Re: [j-nsp] Going Juniper

I'm literally up working right now in a maintenance window throwing one of my cable modem cmts communities behind my pair of mx104's... I'm excited to finally start natting my cable modems... Previously I have natted all 6,000 of my dsl customers behind this same pair of mx104's. I do cgnat via

Re: [j-nsp] MX204 and copper SFP?

Quite timely, I saw a tweet around forcing the interface name via a CLI command. https://twitter.com/mohsinulmalik/status/983190461513744385?s=21 Apologies but I have not tested this myself, but may be of interest to those of you on this list. Cheers, Graham On Sat, 7 Apr 2018 at 07:49, Niall

Re: [j-nsp] ssh-key issue / MX 16.1R5

Hi list, Returning to this past thread. We are seeing this issue also with 18.1, at least with MX10k with dual RE, where the $USER/.ssh directory is chown'ed to root during RE switchover. The directory can be chown'ed back to $USER for example by deleting and re-adding [system services ssh].