Rebooting a Storage Processor (SP) can safely resolve minor problems with the SP, its components, or the system software on the SP. You also reboot a healthy SP that is in Service Mode to return it to Normal Mode.
CAUTION
When an SP reboots, it stops servicing I/O to hosts. In virtual deployments, data is unavailable during an SP reboot. In physical deployments, all NAS servers on the SP fail over to the other SP, if it is healthy. By default, when the SP has finished rebooting, the NAS servers fail back to it. If the Failback Policy is disabled, all NAS servers on it will not fail back automatically and will remain on a single SP. Performance can degrade significantly when all NAS servers reside on a single SP. You can fail back the NAS servers manually.
Procedure
1.Execute the Reboot task and confirm.
2.Wait while the SP reboots.
3.You will know the SP has rebooted when the Mode field displays Normal.
Note that the Unisphere UI may not refresh automatically. If prompted, reload the Unisphere UI. Or reload the UI manually.
In virtual deployments, you can monitor the reboot by using the VMware console. For information, see the VMware documentation.
4.If rebooting the SP does not correct the problem, reimaging the SP is the next action you can take to safely service it.