If they are smart enough to reboot a router or just keep trying for a few seconds and then can continue, that is non-service affecting. If our call center lights up with 200 calls, that is service affecting.
From: Dennis Burgess Sent: Monday, January 15, 2018 2:44 PM To: af@afmug.com Subject: Re: [AFMUG] IPv4 exhaust again That really depends on what you consider “non-service affecting” .. I would argue that as long as customers can get out and customers can get into their public IPs, a 10-30 seconds of them not getting out, is fine. Finding products that store connections etc, and continues a download during the failure, gets real costly. Just my two cents, but I do understand your point of view. Dennis Burgess – Network Solution Engineer – Consultant MikroTik Certified Trainer/Consultant – MTCNA, MTCRE, MTCWE, MTCTCE, MTCINE For Wireless Hardware/Routers visit www.linktechs.net Radio Frequency Coverages: www.towercoverage.com Office: 314-735-0270 E-Mail: dmburg...@linktechs.net From: Af [mailto:af-boun...@afmug.com] On Behalf Of Chuck McCown Sent: Monday, January 15, 2018 3:38 PM To: af@afmug.com Subject: Re: [AFMUG] IPv4 exhaust again Just need it to be: Totally automatic failover Non service affecting We will soon have either 100 Gig or 40 Gig to the world. So I am thinking whatever we use needs to be multiple units all running in parallel. From: Dennis Burgess Sent: Monday, January 15, 2018 2:33 PM To: af@afmug.com Subject: Re: [AFMUG] IPv4 exhaust again You can engineer around that as well. There are many things you can do with multiples of those types of units. Simple to do and failover can be easy if setup correctly. Dennis Burgess – Network Solution Engineer – Consultant MikroTik Certified Trainer/Consultant – MTCNA, MTCRE, MTCWE, MTCTCE, MTCINE For Wireless Hardware/Routers visit www.linktechs.net Radio Frequency Coverages: www.towercoverage.com Office: 314-735-0270 E-Mail: dmburg...@linktechs.net From: Af [mailto:af-boun...@afmug.com] On Behalf Of Mathew Howard Sent: Monday, January 15, 2018 3:15 PM To: af <af@afmug.com> Subject: Re: [AFMUG] IPv4 exhaust again Yeah, personally, I'd split it between multiple boxes and do something like one /21 per box. It makes things a bit more complex, but it also means that if one of those boxes does happen to croak, you're only have to deal with a quarter of the subscribers going down instead of the whole works. On Mon, Jan 15, 2018 at 3:02 PM, Adam Moffett <dmmoff...@gmail.com> wrote: Thanks for the tip. I don't know why I didn't think to use the filter. I guess 1,000 or so subscribers equals 26,000 or so connections. That's good to know. In this instance I have a private /21 NAT'd onto a public /28 with the ccr 1036 and have plenty of spare room on the CPU. Just an idea for Chuck's case, but the 1036 with 4 10G ports and 12 1G ports is only about $800 from Baltic. You could get 4 of those for your 8,000 user load and have 4 hot spares in the rack. Assign a private /21 to each unit. You could create a LAG for the 4 10G ports to get a 40G uplink.
