2) The method used is winbox, paste in the update file, reboot and then update firmware and reboot again. change package wireless for wireless-fp

This still one incomplete way how to describe the upgrade.
(wait and I write what method I'm using)

Wait ... rextended I have normal work of devices about 12-13 hours ...
I'm was upgraded 10 points ...
At all this points I have power suggestor and UPS ... From electricity it's not depend ...
951g - it's home router for testing ... and he has a normal electricity ...
I also work with this equipment and do upgrade Not for the first time ...

My point is simple: why you have write this detail only now?
Still missing the description of upgrade procedure used.
Are existent more than 8 way to upgrade/update the device...

The only common item I notice till now is one:

IPsec block the upgraded devices.

This "deduction" are based on all post I have read till now about blocked RouterBOARD after update/upgrade.

My point is simple: why you have write this detail only now?
Still missing the description of upgrade procedure used.
Are existent more than 8 way to upgrade/update the device...[/quote]

1. I respect you ... and many of your topics help me ...
2. I think up to this point that only I have this problem and this is only my problem
3. I do update standart way - copy the update configuration to the router and do a restart
4. All of SXT work at only bridge mode ... no routing ... only bridge ... (but only one of 10 be are brocken)
5. 951G have very copmplexity configuration ... worka as ipsec and EoIP concentrator ... OSPF routing ...
6. You are very very brave man if can upgrade for new software more 1000+ devices

Another piece of puzle than make me think the real problem on upgrade is IPsec config....

About the 1000+ device, i'm not so intrepid.

First I upgrade the device on near tower (500mt) from my office and all the client linked directly here, after some week of perfect works, now I do mass upgrade from 5.25/5.26 to 6.17/6.18 (upgraded to 6.17 still on 6.17 for now), but all infrastructure are 6.17 or 6.18.

After regular update (from internal web update )from 6.17 to 6.18
dhcp static leases disappear each time after restart RB951G-2HnD

try to netinstall and see if do the same, because if it work correctly after netisntall, probably some setting from 6.17 to 6.18 are corrupted.

read the topic from top to bottom and mine is the latest issue.

my SXT-2 gets reset to default config. the ROS version is 6.18.

i vouch by mikrotik for performance and stability.... but now my reputation is at stake.

maybe we all received the same batch of hardware??? what say?

i request normis to please look into this and get things solved before they get bad.

The only common denominator I found in all of this was the fact that those routers that crashed were ones where I had used bridge mode. The routers that continued working even after the upgrade were those that I had NOT implemented bridges on. So if anyone has experienced similar problems and used bridge mode then I suspect that this is where the problem lies. It would be nice to hear from those of you that have been affected by this whether you were also using bridge mode so we can put this to rest.

I would like to add observation, that might help pinpoint the problem.
I start getting sudden reboots on RouterBoard 951HnD when I tried to add bridge filter rules to drop some packets basing on interface packet was received or transmitted.
Similar rules added into bridge NAT table did not lead to reboots.