Hi, I’m not sure this can be Mikrotik-related, but I’m investigating to exclude things 
I have a rb2011 and a Zyxel nas, NSA310S, in a rack shelf, adsl is still not connected and nobody had physically accessed stuff.
I’m sure nas was powered off, everything connected and ready, but not used yet.
Yesterday I found it powered on (uptime 5 days)…
This is not power-fault related, I have an UPS, and mikrotik clock is still fine (without ntp, so there had not been power outages). Mik uptime is 13 days.
ether2 is the master port of ether 3,4,5 , and also the port the nas is connected to.
When nas was powered off, it was probably just someway “sleeping”, since mik led was blinking periodically…
In fact, during my first tests I had
mar/03 17:54:32 interface,info ether2 link down
mar/03 17:56:10 interface,info ether2 link up (speed 1000M, full duplex)
mar/03 17:56:42 interface,info ether2 link down
mar/03 17:57:26 interface,info ether2 link up (speed 1000M, full duplex)Then I checked when nas started (in the meanwhile, I changed interface name) … It was Sunday at 7am, so I’m sure I wasn’t there testing stuff
Relevant log entries:
mar/09 07:08:27 interface,info ether02-master-local link down
mar/09 07:08:29 interface,info ether02-master-local link up (speed 1000M, full duplex)
mar/09 07:08:58 interface,info ether02-master-local link down
mar/09 07:09:01 interface,info ether02-master-local link up (speed 1000M, full duplex)
mar/09 07:09:10 dhcp,info default assigned AAA.AAA.AAA.AAA to XX:XX:XX:XX:XX:XXSo NAS not only “accepted” ethernet link, but started and asked a dhcp address, its default startup behaviour…
NAS logs doesn’t report useful things, I checked and it had WOL active, but nothing should have waked it …
The only thing I may think is, since nas support power scheduling, some “bug or feature” like a default setting to reboot/start every X days, who knows…
I’ve not found anything related in NAS default setup…
This seems me quite weird, maybe someone can help me understand things…