-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Thomas Jackson Sent: Friday, 26 July 2019 11:28 AM To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: [MT-AU Public] SXTLTE dropouts after upgrade
Good morning all,
Just hoping for a sanity check... we have a fleet of RBSXTLTE3-7 units out in the field which have proven to be quite reliable.
Since upgrading one of the units which was previously working fine from 6.39.2 to 6.45.2 for the security fixes (and doing associated firmware upgrade) - the unit is locking up even with no traffic after about 4 hours of uptime. I'm still able to SSH into it and do some tasks (eg issuing "/system reboot" works, albeit takes quite a while to actually do the reboot), but other tasks don't work (eg if I type in "/ping 1" it will reliably and totally lock the SSH session before I can even enter the full IP address).
I've tried a full factory reset of configuration and rebuilding from scratch, as well as going back to 6.44.5 and up to 6.46beta16, the only idea I haven't tried yet is to netinstall it (which is a bit of a challenge as it isn't something I can easily access physically so I'm hoping to avoid that!). I'm not game to upgrade another one of our units to see if it is the unit or the upgrade
Thanks Mike The firmware was updated after the RouterOS update - and yes, the upgrade firmware is matching the current firmware in "/system routerboard print" I think I'll have to do the remote netinstall - I was hoping there might have been a better way around it but not to be! -----Original Message----- From: Public <public-bounces@talk.mikrotik.com.au> On Behalf Of Mike Everest Sent: Friday, 26 July 2019 12:19 PM To: 'MikroTik Australia Public List' <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] SXTLTE dropouts after upgrade Hi Thomas, Two thoughts that may be worth considering in such circumstances: 1. did you update the routerboot before or after the routeros update? Does the current firmware shown by '/system routerbard print' match the 'upgrade firmware' value? 2. if you do need to netinstall, you can enter netinstall mode without physical access to the device (but still need direct L2 access - which could be over tunnel such as EoIP bridged to other device on same broadcast domain) by use of routeros command: /system routerboard bios set boot-device=try-etherboot-once etherboot-timeout=30 /system reboot Cheers, Mike. that is
the problem quite yet.
Is there anything obvious with the upgrade path that I've missed perhaps?
Kind regards,
Thomas
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au