Aight, so my colleague that has the stack on his table (different site) has performed a test with following results: DHCP reservation was created for active (stack-master) stack member Active stack member was forcibly disconnected from power New switch became active This resulted in lack of connectivity to Meraki cloud for 30 minutes After 30 minutes, the stack sent DHCP request resulting in having random dhcp-pool address, connectivity with Meraki cloud was renewed After re-connecting the switch disconnected in step #2 , that newly-booted switch acquired random dhcp-pool address which was changed to stack active switch' address soon after After reload of the whole stack, it took whopping 30 minutes for the stack to become visible in Meraki portal The switch that was originally active is active again and has DHCP-reservation address To me this seems that assigning the stack a static IP and calling it a day will be the best we can do.
... View more