System information

35 of 114Release 7.0VNX™ System Operations
VNX5500 planned powerdown
The VNX5500 is available in one configuration: block, file, and unified. Follow the
instructions for your system configuration.
File/Unified
The VNX5500 for file and VNX5500 for unified can be configured with either one,
two, or three blades and one or two Control Stations.
Step Action
1. When possible, before you power down the VNX5500, be sure to notify all users of the
powerdown.
2. Establish a HyperTerminal session and login to the Control Station at the serial console:
Connect a null modem DB9 serial cable from a Windows-based laptop or workstation to
the serial port on the Control Station
On the Windows client, open a HyperTerminal session
Select the COM port that the cable connects to in the Connect Using box and click OK
Enter the following port settings:
• Bits per second: 19200
• Data bits: 8
• Parity: None
• Flow Control: None
• Emulation: Auto Detect
• Telenet terminal ID: ANSI
From the Hyperterminal session, log into the Control Station as nasadmin and su to
root
3. Verify the system’s health. Type:
# /nas/bin/nas_checkup
The checkup command reports back on the state of the control station, data movers,
and storage system.
Note: This healthcheck ensures that there are no major errors in the system that would
prevent the system from being turned on during the power up process.
This step will take several minutes.
4. To halt the Control Station and all the blades, type the following:
# /nasmcd/sbin/nas_halt now
*************************** WARNING! **************************
You are about to HALT this VNX including all of its Control
Stations and Data Movers. DATA will be UNAVAILABLE when the
system is halted.
Note that this command does *not* halt the storage array.
ARE YOU SURE YOU WANT TO CONTINUE? [ yes or no ] :
5. Type yes.
It can take as long as 20 minutes to halt the server, depending on the configuration of
the VNX system. Wait until the command completes before continuing. If the Control
Station halted successfully, the Hyper Terminal session will be unresponsive.