I recommend opening a ticket so MT gets a better idea that there is something that they need to investigate, even if they can't get a supout.
On Sun, Mar 8, 2020 at 6:16 PM Jesse DuPont <jesse.dup...@celeritycorp.net> wrote: > So, I have had this happen, too. In fact, it's happened to every 4011 I > have out there at some point. Starts out by no longer responding to > SNMP/Winbox/SSH. If you leave it in this state long enough, it will > eventually stop responding to ping and stop passing traffic, too. > Ultimately, had to hard boot them. The first one it happened to had no > subscriber traffic on it and had only been up for a couple of weeks. Since > the hard boot, it's been up for 144 days and has been on 6.44.3 since it > was installed. I probably shouldn't have just said how long it's been up > (oh well). I think it's a 4011 hardware issue. I have not opened a ticket > about it because there is no way to get Mikrotik a supout. It's not > crashing in such a way as to auto-create one and after the boot is no good. > I do have mine syslogging to a syslog server and I was able to see that > every time I tried to poll it with SNMP, I'd get something like "program xx > stopped responding" and the number (xx) was different every time. > > > *Jesse DuPont* > > Owner / Network Architect > email: jesse.dup...@celeritycorp.net > Celerity Networks LLC / Celerity Broadband LLC > Like us! facebook.com/celeritynetworksllc > > Like us! facebook.com/celeritybroadband > > > On 3/7/20 6:28 PM, Steve Jones wrote: > > If you have a baicells enb plugged into one, they will sometimes cause a > broadcast storm, like a single port loop, if that makes sense, this causes > a kernel panic and reboot. Things are really weird until you do a clean > reboot. Mikrotik support can verify if this is the issue from the supout > file. > > On Sat, Mar 7, 2020, 1:46 PM Colin Stanners <cstann...@gmail.com> wrote: > >> Are they on the same customer data "path"? I saw a note that an >> occasional CCR freeze with recent firmware was possibly due to the h232 NAT >> translator. >> >> On Sat, Mar 7, 2020, 12:33 PM Nate Burke <n...@blastcomm.com> wrote: >> >>> It's just strange that these have been deployed for Months, but 2 locked >>> up in the same week. And 5 days apart, with different firmware, both in >>> temperature controlled indoor racks. I don't think it was triggered by >>> some rogue WAN Packets. If that was the case, I'd expect they both >>> would have locked up at the same time. MRTG showed no change in RAM >>> usage, or CPU prior to the lockup. >>> >>> On 3/7/2020 12:04 PM, Ken Hohhof wrote: >>> > I don't have very many RB4011's. One RB4011iGS+ at a tower site in an >>> > outdoor NEMA box running 6.43.16 and no problems. One >>> RB4011iGS+5HacQ2HnD >>> > running 6.45.5 at a customer site with 84 days uptime. That one used >>> to >>> > reboot occasionally with a log message about having to reboot due to >>> some >>> > kernel problem. It seems to have stopped that since the FW upgrade >>> but hard >>> > to tell since it happened maybe once every 2 weeks. >>> > >>> > I have some RB1100AHx4's which is a very similar architecture and I've >>> seen >>> > occasional unexplained reboots on 2 of them. No lockups though. The >>> ones >>> > that have rebooted are still on 6.40.8, a more recent one is on >>> 6.43.16 and >>> > AFAIK has not rebooted but it did stop once responding to Winbox and >>> had to >>> > be manually rebooted. Everything else seemed to be running fine >>> including >>> > PPPoE server, RADIUS, and Mikrotik API. >>> > >>> > >>> > -----Original Message----- >>> > From: AF <af-boun...@af.afmug.com> On Behalf Of Nate Burke >>> > Sent: Saturday, March 7, 2020 11:24 AM >>> > To: Animal Farm <af@af.afmug.com> >>> > Subject: [AFMUG] RB4011 Lockups >>> > >>> > This week I've had 2 RB4011 Routers lockup requiring a power cycle. >>> They >>> > were still passing some traffic, but stopped doing things like handing >>> out >>> > DHCP, or responding to SNMP. And you couldn't log into them via >>> Winbox or >>> > MACNeighbor. >>> > >>> > One was on ROS6.44.3, the other on ROS6.45. Both of them were doing >>> NAT, >>> > whereas most of my Mikrotiks are only routing. Both of these >>> locations have >>> > multiple RB4011s, and only the one doing NAT locked up. >>> > Nothing is recorded in the log other than the reboot. These were both >>> > routers that have been installed for months. One router lockup I can >>> > attribute to a fluke, but 2 in the same week is worrysome. Has any >>> one else >>> > noticed anything? >>> > >>> > -- >>> > 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 >> > > > -- > 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
