Once we get CBRS going, we are waiting on commsearch, I have no intention of doing workarounds like returning to part 90. I think its best we operate SAS once we start and learn to deal with the consequences. Im assuming 2.0 will be delayed over the end of the world, but thats what this period is for, working the bugs out. no one is forcing us to use CBRS. There will be occasional outages. there is nothing on the planet that doesnt have outages. The problem with reverting to part 90 every time theres an issue is that we are still growing our networks, and at one point that wont be an option anymore, only there are a huge number of customers and we cant change. This is the time to see how well we can train our customers to deal with the inevitable. Customers will shed, but the more that do, the more likely the SAS administrators will respond with resiliency. matt hoppes bitching at them about the cloud doesnt achieve much, thats what matt does. but now matt hoppes bitching at them because hes shedding customers and is going to take his revenue away from them, that carries a little more weight. This is also the time to point customers to the FCC complaint channel since its not the operator.
On Thu, Apr 30, 2020 at 10:36 AM Ken Hohhof <af...@kwisp.com> wrote: > I am a little fuzzy on this part, but I think cnMaestro does all the > tricks it can to keep from withdrawing a grant once issued. I suspect if > the SAS is unreachable or not responding, cnMaestro may do some kind of > holdover like you mentioned. The problem is if the SAS responds but with > garbage or something that looks like it is withdrawing the authorization. > > As far as using more than one SAS, I think that is a firm no, unless you > used one for part of your network and another for the rest of your network. > > When the heartbeats fail, the SMs will keep registering for a few seconds > at a time so they can still communicate with the AP. And yes you can go > back to Part 90 operation, but I don't think you will be able to use > 3550-3650. If an extended outage happened, you could probably get > customers back online that way, albeit with reduced performance. > > > -----Original Message----- > From: AF <af-boun...@af.afmug.com> On Behalf Of Adam Moffett > Sent: Thursday, April 30, 2020 10:24 AM > To: af@af.afmug.com > Subject: Re: [AFMUG] anybody else having SAS problems this morning? > > I don't know who assured you that outages wouldn't happen, but that seems > like an irresponsible claim. Was it the vendor sales channel? > > On the other hand there are clearly ways to make a service bullet proof. > When was the last time Google DNS was down? > > Is SAS Redundnacy possible? Like could Cambium set you up with both > Federated and Google and fallback if one fails? > > Would the FCC be amenable to a 1 hour holdover if the SAS is unreachable? > > I'm just throwing ideas out there. I'm not asking if we can sanitize the > bugs out of the SAS with disinfectant or anything as dumb as that I hope. > > > On 4/30/2020 10:59 AM, Matt Hoppes wrote: > > I screamed this would happen -- I was assured not. > > > > On 4/30/20 9:49 AM, Josh Luthman wrote: > >> Yop... > >> > >> Josh Luthman > >> Office: 937-552-2340 > >> Direct: 937-552-2343 > >> 1100 Wayne St > >> Suite 1337 > >> Troy, OH 45373 > >> > >> > >> On Thu, Apr 30, 2020 at 9:48 AM Tushar Patel <tpa...@ecpi.com > >> <mailto:tpa...@ecpi.com>> wrote: > >> > >> Ken, > >> > >> Does this means your customers are not getting any service when > >> such > >> things happens? > >> > >> > >> > >> Tushar > >> > >> > >>> On Apr 30, 2020, at 8:33 AM, Ken Hohhof <af...@kwisp.com > >>> <mailto:af...@kwisp.com>> wrote: > >>> > >>> > >>> > >>> Cambium 450 using cnMaestro Cloud and Federated Wireless SAS. > >>> Anybody else having Domain Proxy HTTP failures or heartbeat > >>> timeouts this morning?____ > >>> > >>> -- AF mailing list > >>> AF@af.afmug.com <mailto:AF@af.afmug.com> > >>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com > >> -- AF mailing list > >> AF@af.afmug.com <mailto:AF@af.afmug.com> > >> http://af.afmug.com/mailman/listinfo/af_af.afmug.com > >> > >> > > > > -- > AF mailing list > AF@af.afmug.com > http://af.afmug.com/mailman/listinfo/af_af.afmug.com > > > > -- > AF mailing list > AF@af.afmug.com > http://af.afmug.com/mailman/listinfo/af_af.afmug.com >
-- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com
