EMC® VNX™ Series Release 7.0 VNX™ System Operations P/N 300-011-798 REV A01 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.EMC.
of 114 Release 7.
Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 Cautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 User interface choices . . . . . . . . . . . . . . . . . . . . . . .
Change Control Station time zone using the CLI . . . . . . . . . . . . . . .62 Configure NTP service using the CLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 Set the date and time of the VNX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Set Control Station date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Set Data Mover or blade date and time. . . . . . . . . . . . . . . . . . . . . . . .66 Audit the VNX . . . . . . . . . . . . . . . . . . . . . . .
Introduction System operations are common operation tasks that include powering up or powering down a server, halting or restarting a Control Station, a Data Mover, or blade, or setting the server time, date, and time zone. This document is part of the EMC® VNX™ Series documentation set and is intended for use by system administrators responsible for performing day-to-day operations of a VNX for file and for monitoring the server or resolving simple operation problems.
Cautions ! ! CAUTION ◆ The power sockets at the rear of each uninterruptible power supply (UPS) provide the blade enclosures, the automatic transfer switches (ATSs), and the Control Stations with power for a predetermined time period during an AC power outage. This backup power gives the server enough time to shut down gracefully. To prevent premature discharge of the UPS batteries during a power outage and improper shutdown, do not connect any other devices (power loads) to these sockets.
Related information Specific information related to the features and functionality described in this document is included in: ◆ EMC VNX Command Line Interface Reference for File ◆ Parameters Guide for VNX for File ◆ Online VNX for File man pages EMC VNX Documentation on the EMC Online Support website The complete set of EMC VNX series customer publications is available on the EMC Online Support website. To search for technical documentation, go to http://Support.EMC.com.
Managing the VNX The tasks to manage the VNX are: 8 of 114 Release 7.
Power up the VNX The tasks to power up the VNX after a planned power down or after an emergency shutdown are: VNX™ System Operations ◆ "VNX VG2 and VG8 powerup" on page 10 ◆ "VNX5100 powerup" on page 12 ◆ "VNX5300 powerup" on page 14 ◆ "VNX5500 powerup" on page 17 ◆ "VNX5700 powerup" on page 20 ◆ "VNX7500 powerup" on page 23 Release 7.
VNX VG2 and VG8 powerup The VG2 can be configured with either one or two blades and one or two Control Stations. The VG8 has either two to eight blades and one or two Control Stations. These instructions cover all configurations. Step Action 1. If the VG2/VG8 is in a cabinet by itself (that is, the storage array is not in the same cabinet), then turn off the cabinet circuit-breakers to remove all power from the VG2/VG8 cabinet. 2.
Step Action 7. Connect the power cables for the Control Station(s) to the PDP. In the example illustration provided in step 6, these are power cables 1 and 2. 8. If the system power LED (D in the following figure) on the front of the Control Station indicates that the Control Station is off, turn on the Control Station by pressing the Power button (B) on the front. Ensure that the Control Station is powered up before continuing.
VNX5100 powerup The VNX5100 is the only available configuration: block. Block Follow the instructions below for your VNX5100 for block: Step Action 1. Verify that the master switch/circuit breakers for each cabinet power strip are OFF. 2. Ensure that the power cable for SP A is plugged into the SPS and power cord retention bails are in place. 3.
Power supply Power supply fault 8Gb 6Gb fibre SAS 2 3 4 3 3 3 2 2 2 1 1 1 0 0 8Gb 6Gb fibre SAS 1 X4 5 2 3 4 5 Figure 1 VNX™ System Operations A 1 X4 6Gb SAS 0 X4 SAS port status 0 3 2 0 B 1 Disk processor rear 6Gb SAS 0 X4 SP power SP fault/status SAS port status Location of Storage Processor power and status LEDs Release 7.
VNX5300 powerup The VNX5300 is available in three configurations: block, file, and unified. Follow the instructions for your system configuration. File/Unified The VNX for file and VNX for unified can be configured with either one or two blades and one or two Control Stations. Step Action 1. Verify that the master switch/circuit breakers for each cabinet power strip are ON. If you are powering up the VNX5300 in a cabinet that contains other components, do not turn off the cabinet circuit breakers.
Step Action 10. Check the system and hardware status as follows: a. From a browser, type the IP address of the primary Control Station. b. Log in to the Unisphere software as sysadmin and define the scope as Global. c. Use the drop-down list at the topleft Dashboard to select the system name and view its System Information page. d. On this page, verify that the Status fields for the VNX display OK. 11.
Step Action 6. Turn the SPS power switches ON.. SPS power switch B SPS power switch A CIP-001115 7. Ensure that any other devices in the cabinet are correctly installed and ready for power up. 8. Turn on the master switch/circuit breakers for each cabinet power strip. In a 40U EMC cabinet, the master switches are on the power distribution panels (PDPs). The storage system can take 10-12 minutes to complete a typical power up.
VNX5500 powerup The VNX5500 is available in three configurations: 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. Verify that the master switch/circuit breakers for each cabinet power strip are ON.
Step Action 10. Check the system and hardware status as follows: a. From a browser, type the IP address of the primary Control Station. b. Log in to the Unisphere software as sysadmin and define the scope as Global. c. Use the drop-down list at the topleft Dashboard to select the system name and view its System Information page. d. On this page, verify that the Status fields for the VNX display OK. 11.
Step Action 6. Turn the SPS power switches ON.. SPS power switch B SPS power switch A CIP-001115 7. Ensure that any other devices in the cabinet are correctly installed and ready for power up. 8. Turn on the master switch/circuit breakers for each cabinet power strip. In a 40U EMC cabinet, the master switches are on the power distribution panels (PDPs). The storage system can take 10-12 minutes to complete a typical power up.
VNX5700 powerup The VNX5700 is available in three configurations: block, file, and unified. Follow the instructions for your system configuration. File/Unified The VNX5700 for file and VNX5700 for unified can be configured with either two to four blades and one or two Control Stations. Step Action 1. Verify that the master switch/circuit breakers for each cabinet power strip are ON.
Step Action 10. Check the system and hardware status as follows: a. From a browser, type the IP address of the primary Control Station. b. Log in to the Unisphere software as sysadmin and define the scope as Global. c. Use the drop-down list at the topleft Dashboard to select the system name and view its System Information page. d. On this page, verify that the Status fields for the VNX display OK. 11.
Step Action 8. Turn the SPS power switches ON.. SPS power switch B SPS power switch A CIP-001115 9. Ensure that any other devices in the cabinet are correctly installed and ready for power up. 10. Turn on the master switch/circuit breakers for each cabinet power strip. In a 40U EMC cabinet, the master switches are on the power distribution panels (PDPs). The storage system can take 10-12 minutes to complete a typical power up.
VNX7500 powerup The VNX7500 is available in three configurations: block, file, and unified. Follow the instructions for your system configuration. File/Unified The VNX7500 for file and VNX7500 for unified can be configured with either two to eight blades and one or two Control Stations. Step Action 1. Verify that the master switch/circuit breakers for each cabinet power strip are ON.
Step Action 10. Check the system and hardware status as follows: a. From a browser, type the IP address of the primary Control Station. b. Log in to the Unisphere software as sysadmin and define the scope as Global. c. Use the drop-down list at the topleft Dashboard to select the system name and view its System Information page. d. On this page, verify that the Status fields for the VNX display OK. 11.
Step Action 8. Turn the SPS power switches ON.. SPS power switch B SPS power switch A CIP-001115 9. Ensure that any other devices in the cabinet are correctly installed and ready for power up. 10. Turn on the master switch/circuit breakers for each cabinet power strip. In a 40U EMC cabinet, the master switches are on the power distribution panels (PDPs). The storage system can take 10-12 minutes to complete a typical power up.
Power down the VNX Remove power from the VNX in an orderly way to protect data. Incorrectly powering down the VNX can cause data loss or service disruption. The tasks to power down the VNX Network Server after a planned power down or after an emergency shutdown are: 26 of 114 Release 7.
VNX VG2 and VG8 planned powerdown Step 1. Action Do the following before you power down the server: a. Notify all users of the planned powerdown several days in advance when possible. b. Prevent all logins and notify all users several minutes in advance of the impending powerdown. c. Log out all users. 2. To perform a planned powerdown, you should be within close proximity of the server.
Step 5. Action Restart the Control Station. Restart the Control Station by pressing the Power button in the front of the Control Station. To reach the Power button on the Control Station, you have to remove the front bezel. Control Station (front) Power button CNS-000876 Once the Control Station restarts, go on to the next step. 6. Verify the shutdown of the blades: Wait for 5 minutes, and then log in as root at the login prompt.
Step 9. Action Disconnect the blade enclosure power cords from the power distribution units (PDPs). The blade enclosure power cables are labeled 3, 4, 5, and 6 in the following image. Power distribution panel (PDP) Power distribution panel (PDP) 2 CS 1 1 CS 0 6 2 3 3 2 1 2 2 1 0 # # 3 2 2 1 2 0 10. VNX™ System Operations 1 SP A 0 0 # 4 1 2 0 1 3 SP A 3 5 0 0 1 1 0 # Disconnect each Control Station power cord from the power distribution units (PDPs).
Step 11. Action Does the VG2 or VG8 server cabinet contain other equipment that is connected to the cabinet PDPs and shared with other systems (such as Fibre Channel switches, storage arrays, and so forth)? If yes, stop here. The VG2 or VG8 server is powered down. If no, go to the next step. 12. Turn off (0 position) the left and right cabinet circuit-breaker switches located at the back of the cabinet near the bottom to complete the powerdown of the VG2 or VG8 server.
VNX5100 planned powerdown The VNX5100 is available in one configuration: block. Follow the instructions for your system configuration. Block The tasks to power down the VNX5100 include stopping I/O, halting the storage processors, and powering down the system by using the SPS power switches. Step Action 1. When possible, before you power down the VNX5100, notify all users of the powerdown. 2. Stop all I/O activity to the Storage Processors in the DPE.
VNX5300 planned powerdown The VNX5300 is available in one configuration: block, file, and unified. Follow the instructions for your system configuration. File/Unified The VNX5300 for file and VNX5300 for unified can be configured with either one or two blades and one or two Control Stations. Step Action 1. When possible, before you power down the VNX5300, be sure to notify all users of the powerdown. 2.
Step Action 6. Unplug the power cables from the Control Station(s) and the blade enclosure’s power supplies to the PDU. 6. If you are powering down the system completely, shutdown the storage array: Note: This step involves safely shutting down the SPs to preserve the write cache and can be skipped if only the blade(s) and Control Station are to be powered down a. Stop all I/O activity and wait five minutes before continuing.
Step Action 3. Wait 5 minutes. 4. Use the SPS power switches to power off the storage system. . SPS power switch B SPS power switch A CIP-001115 Wait two minutes to allow the storage system to write its cache to disk. Make sure that the SPS power indicators are off before continuing.The storage system will power down within 2 minutes. For systems with a single SPS, after waiting two minutes, unplug the SP B and DAE 0 LCC B power cables from the PDU. 5.
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.
Step Action 6. Unplug the power cables from the Control Station(s) and the blade enclosure’s power supplies to the PDU. 6. If you are powering down the system completely, shutdown the storage array: Note: This step involves safely shutting down the SPs to preserve the write cache and can be skipped if only the blade(s) and Control Station are to be powered down a. Stop all I/O activity and wait five minutes before continuing.
Step Action 3. Wait 5 minutes. 4. Use the SPS power switches to power off the storage system. . SPS power switch B SPS power switch A CIP-001115 Wait two minutes to allow the storage system to write its cache to disk. Make sure that the SPS power indicators are off before continuing.The storage system will power down within 2 minutes. For systems with a single SPS, after waiting two minutes, unplug the SP B and DAE 0 LCC B power cables from the PDU. 5.
VNX5700 planned powerdown The VNX5700 is available in one configuration: block, file, and unified. Follow the instructions for your system configuration. File/Unified The VNX5700 for file and VNX5700 for unified can be configured with either two to four blades and one or two Control Stations. Step Action 1. When possible, before you power down the VNX5700, be sure to notify all users of the powerdown. 2.
Step Action 6. If you are powering down the system completely, shutdown the storage array: Note: This step involves safely shutting down the SPs to preserve the write cache and can be skipped if only the blade(s) and Control Station are to be powered down a. Stop all I/O activity and wait five minutes before continuing. Note: All I/O activity flowing from the blades was stopped when the blades were shutdown in step 4.
Step Action 4. Use the SPS power switches to power off the storage system. SPS power switch B SPS power switch A CIP-001115 Wait two minutes to allow the storage system to write its cache to disk. Make sure that the SPS power indicators are off before continuing. The storage system will power down within 2 minutes. ! CAUTION Never unplug the power supplies to shut down an SPE.
VNX7500 planned powerdown The VNX7500 is available in one configuration: block, file, and unified. Follow the instructions for your system configuration. File/Unified The VNX7500 for file and VNX7500 for unified can be configured with either two to eight blades and one or two Control Stations. Step Action 1. When possible, before you power down the VNX7500, be sure to notify all users of the powerdown. 2.
Step Action 6. If you are powering down the system completely, shutdown the storage array: Note: This step involves safely shutting down the SPs to preserve the write cache and can be skipped if only the blade(s) and Control Station are to be powered down a. Stop all I/O activity and wait five minutes before continuing. Note: All I/O activity flowing from the blades was stopped when the blades were shutdown in step 4.
Step Action 4. Use the SPS power switches to power off the storage system. SPS power switch B SPS power switch A CIP-001115 Wait two minutes to allow the storage system to write its cache to disk. Make sure that the SPS power indicators are off before continuing. The storage system will power down within 2 minutes. ! CAUTION Never unplug the power supplies to shut down an SPE.
Shut down the VNX in an emergency This section explains how to shut down the VNX in case of an emergency. "Power down the VNX" on page 26 provides more specifics on normal (planned) powerdown procedures. Perform the following tasks to shut down the VNX in an emergency: ! ! CAUTION These procedures can cause data loss or disrupt service to other clients. Use these procedures only when faced with personal hazard or possible property damage.
Power up after an emergency shutdown After you use the emergency shutdown procedure, you might encounter errors or problems when you try to restart the VNX server. If this occurs, record any error messages and contact the EMC Customer Service immediately. To power up a server after an emergency shutdown, follow the "Power up the VNX" on page 9. VNX™ System Operations Release 7.
Halt the Control Station This section explains how to perform an orderly halt of Control Stations in Unified, Integrated, and Gateway servers. You can halt a Control Station either locally or remotely.
Step 6. Action Halt the primary Control Station by typing: # /sbin/halt The primary Control Station halts. Remotely halt one Control Station This procedure applies to all VNX unified and VNX for file systems single Control Station. After locally or remotely halting the Control Station, use the VNX cabinet console to restart the Control Station. Step Action 1. Use a secure, encrypted, remote login application to log in to the server as root. 2.
Restart the Control Station This section explains how to perform an orderly restart of Control Station(s) in a VNX unified and VNX for file systems. Control Stations restart either locally or remotely.
Step 5. Action Restart the primary Control Station by typing: # reboot The primary Control Station restarts and fails over to the secondary Control Station (making it the new primary Control Station). Do not go to the next step until the Control Station has finished restarting. 6. Log in to the new primary Control Station. 7. Change to root and type the root password. 8.
Step 3. Action Restart the primary Control Station by typing: # reboot After a while, the primary Control Station restarts and fails over to the secondary Control Station (making it the new primary Control Station). 4. Establish another remote connection and log in to the new primary Control Station as root. 5. Restart the new primary Control Station by typing: # reboot The new primary Control Station restarts and fails over to the original primary Control Station.
Halt the Data Movers The following procedure explains how to perform an orderly, timed, or immediate halt of a network server’s Data Mover or blade. This procedure applies to all VNX unified and VNX for file systems. Note: A Data Mover for a VNX for file server is also called a blade. There is no functional difference between a Data Mover and a blade. They both serve the same purpose in a VNX for file server.
Restart a Data Mover The following procedure explains how to perform an orderly, timed or immediate restart of the network server’s Data Movers or blades. The procedure applies to all VNX unified and VNX for file systems. Action To immediately restart and monitor a Data Mover or blade, use this command syntax: $ server_cpu -reboot [cold|warm] -monitor
Check the system status Use the nas_checkup command to perform a health checkup for the VNX. nas_checkup runs scheduled and unscheduled health checks on the VNX and reports problems that are found, and the actions needed to fix the problem and acts as a system health monitor. The scheduled run time for the nas_checkup command is every 2 weeks by default. If a warning or error is discovered during this time, an alert is posted on the Unisphere software.
Output Check Version:6.0.36.0 Check Command:/nas/bin/nas_checkup Check Log :/nas/log/checkup-run.100527-135002.log ---------------------------------Checks--------------------------------Control Station: Checking statistics groups database............... Pass Control Station: Checking if file system usage is under limit....... Pass Control Station: Checking if NAS Storage API is installed correctly. Pass Control Station: Checking if NBS service is started................
Back up the VNX database VNX database created by the VNX software during installation is stored on disk in the Control Station. The VNX database maintains vital information required for each Data Mover or blade. The VNX for file software automatically creates a VNX database backup file 1 minute after each hour. You can manually create a VNX database backup file at any time.
Manual VNX database backup Use this procedure to back up and save a copy of the VNX database without waiting for an hourly automatic backup. Step Action 1. Log in to the network server. 2. List the VNX database backup files by typing: $ ls –l nasdb* A display similar to the following appears: -rw-r--r-1 nasadmin nasadmin nasdb_backup.1.tar.gz -rw-r--r-1 nasadmin root nasdb_backup.b.tar.gz 1920308 May 4 12:03 1022219 Mar 23 19:32 Ensure that a version of nasdb_backup.1.
Step 5. Action Examine the date and time to verify that a new version of nasdb_backup..tar.gz was created by typing: $ ls -l celerra/backup* A display similar to the following appears: total 46208 -rw-r--r-- 1 nasadmin nasadmin 2700 Feb 5 13:01 _dbms_backup.01.tar.gz -rw-r--r-- 1 nasadmin nasadmin 2702 Feb 5 14:01 _dbms_backup.02.tar.gz -rw-r--r-- 1 nasadmin nasadmin 2702 Feb 5 14:01 _dbms_backup.OK.tar.
Verify the daemons After installation, daemons begin running on the Control Station at all times. If for some reason the daemons become disabled, certain server facilities might fail.
Discover SCSI devices The Control Station database maintains a list of all SCSI devices. When required, you can probe the storage system to discover and save the present SCSI devices for a specific Data Mover.
Save SCSI devices You can save SCSI devices to the device table. Before using the -create option, ensure that you back up the existing camdisk file located in the /nas/server/slot_# directory.
Identify the software versions To determine the software versions on the Control Station, Data Mover, or blade, use the following: ◆ "Control Station command" on page 61 ◆ "Data Mover or blade command" on page 61 Control Station command Command To view the software version running on the Control Station, type: $ nas_version -l Output Name : emcnas Version : 6.0.36 Release : 0 05:47:35 PM EDT Size : 618458184 Signature : (none) Packager : EMC Corporation URL : http://www.emc.
Set the time zone of the VNX You can update the time zone information on the Data Mover by using simple and decipherable strings that correspond to the time zones available in the Control Station. You can also update the daylight savings time on the Data Mover for the specified time zone.
Step 4. Action Set the hardware clock to the current time zone of the Control Station by typing: # vi /etc/sysconfig/clock When the file opens, type: ZONE="America/New_York" UTC=false ARC=false 5. Save the file and exit. 6. Change the current time zone, New York, to Denver, by typing: # /usr/bin/perl /nas/http/webui/bin/timezone.pl -s America/Denver Note: A list of valid Linux time zones is located in the /usr/share/zoneinfo directory. 7.
Configure NTP service using the CLI Step Action 1. Log in to the Control Station as root. 2. Check the status of the NTP daemon by typing: # ps -ef |grep ntpd Output: root 3. 17682 11902 0 11:26 pts/0 00:00:00 grep ntpd Display information about the ntpd status by typing: # /sbin/service ntpd status Output: ntpd is stopped 4. Display information about the ntpd configuration by typing: # /sbin/chkconfig ntpd --list Output: ntpd 0:off 1:off 2:off 3:off 5. Open the /etc/ntp.
Step 13. Action Start or restart the NTP daemon by typing: # /sbin/service ntpd start Output: ntpd: Synchronizing with time server: Starting ntpd: [ [ OK OK ] ] [ [ [ OK OK OK ] ] ] # /sbin/service ntpd restart Output: Shutting down ntpd: ntpd: Synchronizing with time server: Starting ntpd: Note: If the response for synchronizing with the time server is positive, the NTP client was able to communicate with the NTP server. 14.
Set the date and time of the VNX To set the date and time of a Control Station or a Data Mover or blade: ◆ "Set Control Station date and time" on page 66 ◆ "Set Data Mover or blade date and time" on page 66 Set Control Station date and time You must log in as root to perform this operation. Action To set the date and time for a Control Station, use this command syntax: # date -s “” where: = time and date format Example: To set the date and time to 2:40 P.M.
Audit the VNX Starting with version 6.0 of teh software, the Control Station provides greater system auditing capabilities than were previously available. VNX auditing now provides a method to audit/detect access to the Data Mover file systems from the Control Station. Auditing is enabled by default on the Control Station after a fresh install, a Control Station recovery, and an upgrade from 5.5 to 6.0. When upgrading from 5.
Configure IPv6 on the Control Station Starting with version 6.0 of the software, the Control Station supports IPv6 through a dual-stacking of IPv4 and IPv6 network addresses. To implement and manage this feature, a new CLI command, nas_cs, has been introduced to manage the configuration properties of the Control Station. Note: For more information about nas_cs and configuring IPv6 on the Control Station, refer to EMC VNX Command Line Interface Reference for File.
Configure IP aliasing IP aliasing allows different IP addresses to point to the same network device. The VNX allows you to configure IP aliasing for a Control Station. This enables communication with the primary Control Station by using a single IP address regardless of whether the primary Control Station is running in slot 0 or slot 1.
Step 70 of 114 Release 7.0 Action Result 2. Type yes to delete the IP alias. All current sessions using alias eth2:0 will terminate Do you want to continue [yes or no]: yes done 3.
Configure SNMP The SNMP collects and processes valuable network information. It gathers data by polling the devices on the network from a management station at fixed or random intervals. When the network is operating ideally, SNMP establishes a state that is called a baseline, which lists all of the operational parameters. The SNMP protocol acts as a network safeguard against irregularities that might hamper the functioning of the network. As of version 6.
Change the ConnectHome settings The VNX ConnectHome function automatically notifies the EMC service center or other service provider if the VNX system detects a serious problem. ConnectHome sends messages by using email, FTP server, or the VNX modem and a customersupplied analog telephone line. EMC recommends that Email transport be configured as the primary transport and that you keep the default EMC recipient address, mailto:emailalert@emc.
Step Action 6. Set the values for the Email transfer ConnectHome option: a. Use the Email Priority drop-down list to set or modify email as a primary, secondary, or tertiary transport mechanism. Specifying disabled removes email as a transport mechanism. b. In the Email-SMTP field, type the fully qualified domain name or IP address primary of the email server. You cannot enter more than 63 characters. c. In the Subject field, set or modify the subject of the email message.
Step 10. 74 of 114 Release 7.0 Action Test the configured ConnectHome options, by: a. Select a delivery method from the Test Type drop-down box and click Test. This sends a test ConnectHome message to the service provider by using the delivery message. b. If you receive a message that the test was successful, contact EMC or your thirdparty service provider and verify that they have received the message.
Set the country code on the MT5634ZBA modem If the customer has a MT5634ZBA modem (check the label on the bottom of the modem or on the box that the modem shipped in) you might need to run a special utility to set the correct country or regional code. The modem ships with a default value for the country or regional code. The default value might not be appropriate for the location of the system.
Step 76 of 114 Release 7.0 Action 4. Type EMC (case-sensitive) and click OK when prompted for the decryption password. The Global Wizard application appears, as displayed. 5. Click Next to begin the wizard. The wizard will now try to contact the modem. Wait for modem detection. If this does not occur, verify that the modem is powered on and the serial cable is securely connected at both ends. 6. Click Next when the modem is found. 7.
Step VNX™ System Operations Action 8. Select or verify that the correct country or region is selected, as displayed. Click Next. A confirmation screen appears with your selection. 9. Click Next on the confirmation screen. 10. Click Finish to exit the wizard. This completes the procedure. Release 7.
Manual instructions for setting the country code Procedure to manually set the country or region code without ZBAWizard.exe: Step 1. Action Connect the serial cable from the modem to your service laptop. Note: Ensure that the modem is powered on. 2. Open a HyperTerminal session by using the following settings: 19200 bits per second, 8 data bits, parity None, 1 stop bit, flow control None. Set terminal emulation to ANSI. Typically this is done by using COM 1. 3.
Table 2 VNX™ System Operations MT5634ZBA modem country/region codes (page 1 of 3) Country Region config command (Hex) ATI9 result code (Decimal) Australia AT%T19,0,1 1 Hong Kong, Hungary, India, Indonesia, Israel, Korea, Malaysia, Republic of Korea, Philippines, Poland, Singapore, Slovenia, Vietnam AT%T19,0,30 48 Japan AT%T19,0,10 16 New Zealand AT%T19,0,9 9 South Africa AT%T19,0,35 53 Release 7.
Table 2 MT5634ZBA modem country/region codes (page 2 of 3) Country Afghanistan, Albania, Algeria, American Samoa, Andorra, Angola, Anguilla, Antigua and Barbuda, Argentina, Armenia, Aruba, Austria, Azerbaijan, Bahamas, Bahrain, Bangladesh, Barbados, Belarus, Belgium, Belize, Benin, Bermuda, Bhutan, Bolivia, Bosnia and Herzegovina, Botswana, Brazil, Brunei Darussalam, Bulgaria, Burkina Faso, Burundi, Cambodia, Cameroon, Canada, Canary Islands, Cape Verde, Cayman Islands, Central African Republic, Chad, Chi
Table 2 MT5634ZBA modem country/region codes (page 3 of 3) Country Region config command (Hex) ATI9 result code (Decimal) Moldova, Republic of Monaco, Mongolia, Montserrat, Morocco, Mozambique, Namibia, Nauru, Nepal, Netherlands, Netherlands Antilles, New Caledonia, Nicaragua, Niger, Nigeria, Norway, Oman, Pakistan, Palestine Territory, Occupied, Panama, Papua New Guinea, Paraguay, Peru, Portugal, Puerto Rico, Qatar, Reunion, Romania, Russian Federation, Rwanda, Saint Kitts and Nevis, Saint Lucia, Sain
Change the Control Station hostname You can change a VNX server’s Control Station hostname. The following procedure uses the CLI. However, if you use the Unisphere software to manage the server, use it to make the hostname change instead. In the following procedure, the Control Station hostname was changed from Eng_1 to cs100. ! ! CAUTION If you use the CLI to change the Control Station hostname and use the Unisphere software to manage the server, ensure that you follow this procedure carefully.
Step 6. Action To ping both the new and the old Control Station hostnames, type: # ping cs100 PING cs100.nasdocs.emc.com (172.24.101.100) from 172.24.101.100 : 56(84) bytes of data. 64 bytes from Eng_1.nasdocs.emc.com (172.24.101.100): icmp_seq=0 ttl=255 time=436 usec # ping Eng_1 PING Eng_1.nasdocs.emc.com (172.24.101.100) from 172.24.101.100 : 56(84) bytes of data. 64 bytes from Eng_1.nasdocs.emc.com (172.24.101.100): icmp_seq=0 ttl=255 time=220 usec 7.
Step 14. Action To confirm the hostname of the Control Station, type: # nas_cel -list Output: id 0 15. name cs100 owner 0 mount_dev channel net_path CMU 172.24.101.100 APM04490091900 To change the SSL certificate for Apache, type: # /nas/sbin/nas_config -ssl Installing a new SSL certificate requires restarting the Apache web server. Do you want to proceed? [y/n]: y New SSL certificate has been generated and installed successfully. 16. 84 of 114 Release 7.
Install Control Station Linux security alerts EMC monitors Linux security alerts and carefully evaluates how the associated errata apply to Control Station Linux. Be sure to install only EMC-approved security updates on the VNX. You can have them installed anytime either during the installation of a new VNX software release or between the installation of new software releases.
Avoid private LAN IP address conflicts VNX servers use a private LAN for communication between the Control Stations and Data Movers or blades. This LAN is sometimes also called a local or internal LAN. By default, this private LAN uses IP addresses in the following three subnets: ◆ 128.221.252.nnn — This subnet is the primary private LAN. For the NS series servers, this LAN connects to the LAN switch on the Control Station 0 tray assembly. ◆ 128.221.253.
Change VNX for block SP management port IP addresses NS and V series gateway servers that use a VNX for block storage array communicate with the array over the public LAN. The IP addresses of the VNX for block storage processor (SP) management ports are stored as part of the VNX for file configuration. If you need to change the IP addresses of the SP management ports, you must reconfigure the server to use the new addresses.
Interpret log files Log files contain messages to assist you in determining what is happening with the VNX. Some logs have information about the state of the VNX, while others have information about errors. As of version 5.6, the system log (sys_log) must be viewed using the nas_logviewer command when viewing the log from the CLI. Table 3 on page 88 provides a complete list of VNX for file logs.
Table 3 VNX for file logs (page 2 of 2) Command line or log location Log Description EMC Symmetrix™ API $ /nas/log/symapi.log Lists events from the SYMAPI layer generated as the VNX for file interacts with an attached Symmetrix system. The Symmetrix documentation provides more information about these messages. Installation and upgrade $ /nas/log/instcli.log $ /nas/log/install. .log $ /nas/log/upgrade. .log Stores log SYMCLI installation.
Table 4 Server log components (page 2 of 2) Log component Description Example Message text The log message. Command succeeded: logsys add output> disk=root_log_2 bufsz=256 Table 5 Server log and system log severity levels Severity level Meaning Severity level Meaning 0 Emergency 4 Warning 1 Alert 5 Notice 2 Critical 6 Info 3 Error 7 Debug Table 6 90 of 114 Release 7.
Table 6 VNX™ System Operations Server log message category (page 2 of 2) Category Explanation LIB Library-related messages LOCK Lock manager messages (for example, statd for NFS) MGFS MiGration File System NDMP Network Data Management Protocol information NFS NFS information (for example, exports and cache activity) PAX Portable Archive Exchange for backup RPC Remote Procedure Call SECURITY Security messages SHADOW Shadow directory messages SMB CIFS services STORAGE and CHAMII Simi
System log Table 7 on page 92 provides a complete list of System log components. Example: Jun 24 10:39:46 2005 BoxMonitor:2:101 Slot 1 reason code of 0 is stale Table 7 System log components Log component Description Example Date and time Displays the date and time. March 15 10:39:46 2005 Facility Identifies the part of the system generating the message text. BoxMonitor Severity level Indicates the importance of the message.
Command log and command error log Example: 2005-03-15 09:52:36.075 db:0:9558:S: /nas/bin/nas_acl -n nasadmin -c -u 201 level=2 2005-03-15 10:46:31.469 server_2:0:26007:E: /nas/bin/server_file server_2 -get group /nas/server/slot_2/group.nbk: No such file or directory Table 9 on page 93 lists the command log components. Table 9 Command log components Log component Description Example Date Displays the date. 2005-03-15 Time Displays the time. 09:52:36.
NAS or SAN environment rules When you connect a SAN configuration to the VNX for file, you create a NAS or SAN configuration. A NAS or SAN configuration has rules for RAID types, LUN allocation, and array read or write cache settings that you must consider. Table 10 on page 94 lists these considerations. If needed, contact the EMC Customer Support or your service provider for help with template selection.
Table 10 VNX for file/VNX for block NAS and SAN environment considerations (page 2 of 3) Category Considerations Allocation of LUNs • The RAID group containing the VNX for file control LUNs must be dedicated to NAS. No SAN LUNs might reside on this RAID group. LUN numbers 0 to 15 are dedicated to VNX for file control LUNs. Note: Any attempt to allocate storage in a LUN number between 0-15 will result in Error 3147: volume resides on a reserved disk.
Table 10 VNX for file/VNX for block NAS and SAN environment considerations (page 3 of 3) Category Considerations Standard parameters and settings when binding LUNs These parameters or settings must be enabled or disabled as follows: • Enable write cache • Enable read cache • Disable auto-assign for each LUN • Disable clariion no_tresspass • Disable failovermode • Disable arraycommpath ! ! CAUTION To prevent file system corruption, the arraycommpath setting should not be changed while the server is o
Collect problem information For problems with Unisphere software or the VNX system, EMC recommends that before contacting the service provider or EMC for help, run log collection promptly. The sooner the collection script is run, the more likely you are to collect command output, logs, and dump files that can be helpful when investigating the problem.
The system logs contain entries each time a dump is transferred by FTP to EMC Customer Service. If the tool is invoked manually, the command output and any other important messages are logged in /nas/log/sys_log. Note: If the configuration file has used the entire serial number string to identify dumps, the location of the dump transfer might be truncated in sys_log.
Run log collection and automatic transfer The Unisphere software can run the Log Collection and Automatic Transfer tool, a support feature found in VNX version 5.5.27 or later. The Log Collection feature is enabled by default. However, automatic transfer is disabled by default. Support materials, logs, and dumps are automatically collected and saved locally on the Control Station.
where is the serial number of the VNX for file and is the time the script was run. After creating the support materials file, contact the service provider or the EMC Customer Service Center for directions on how to deliver the file for analysis."Use CLI options to perform script operations" on page 102 describes how to use the CLI options to perform several script operations. 100 of 114 Release 7.
Disable Automatic Collection and Transfer tool To completely disable the Automatic Collection and Transfer tool, type: $ /nas/tools/automaticcollection -disable -all An alternative method of disabling the entire tool is to edit the configuration file /nas/site/automaticcollection.cfg by using a text editor such as vi, and uncomment the line containing the word OFF. Example of a configuration file output. Output [nasadmin@bulls-cs ~]$ cat /nas/site/automaticcollection.
Use CLI options to perform script operations Table 11 on page 102 lists the Automatic Collection and Transfer tool’s command options and descriptions. You must have root or VNX administrator privileges to use this tool. As a result, be sure to log in to the Control Station as root or nasadmin before using this tool.
User examples The following describe the functions you are most likely to perform with the Automatic Collection and Transfer tool: ◆ To enable automatic transfer of file logs and dumps to EMC Customer Service, at the command prompt, type: $ /nas/tools/automaticcollection -enable ◆ To disable automatic transfer of log files and dumps if they have been previously enabled, at the command prompt, type: $ /nas/tools/automaticcollection -disable ◆ To completely turn off the Automatic Collection and Transfer
Troubleshooting As part of an effort to continuously improve and enhance the performance and capabilities of its product lines, EMC periodically releases new versions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.
• Type nas_message -info , where MessageID is the message identification number. ◆ Celerra Network Server Error Messages Guide: • Use this guide to locate information about messages that are in the earlierrelease message format. ◆ EMC Online Support: • Use the text from the error message’s brief description or the message’s ID to search the Knowledgebase on the EMC Online Support website. After logging in to EMC Online Support, click either Search or Support by Product.
Recovery after an VNX SP failure If a storage processor (SP) panics (software failure) or must be removed and replaced (hardware failure), perform the following to get the SP back online after it restarts: 1. Determine if an SP failed over by using the following CLI command: nas_storage -info -id= If an SP failed over, its disk volumes were transferred to the other SP. 2. Transfer the disk volumes back to the default (owning) SP by using the command: nas_storage -failback -id= 3.
to system-defined statistics groups that can be used as arguments with the new monitor option: Table 14 Sample of Statistics Group names System-defined Statistics Group name server_stats collection name basic-std -summary basic caches-std -summary caches cifs-std -summary cifs nfs-std -summary nfs cifsOps-std -table cifs diskVolumes-std -table dvol Statistics Groups are managed by the newly available nas_stats command.
nas_stats nas_stats allows the user to manage Statistics Groups. There are two types of Statistics Groups: System and User-defined groups. These groups are the same groups that server_stats will display with –monitor, -list, and –info. nas_stats can be used to modify existing System-defined Statistic Groups or it can be used to create new Userdefined Statistics groups. For more information about the syntax and usage of the nas_stats command, refer to the EMC VNX Command Line Interface Reference for File.
260908 messages received 260917 messages sent tcp: **** 123708 packets sent 23 data packets retransmitted 0 resets 118192 packets received 7 connection requests 14 connections lingered udp: **** 0 incomplete headers 249390 bad ports 345047 input packets delivered 98126 packets sent You can also retrieve routing table and interface information, as displayed in the next two commands: $ server_netstat server_2 -r Destination ************** 0.0.0.0 172.24.170.0 172.24.150.0 172.24.130.0 192.1.1.0 172.24.110.
EMC Professional Services can help you implement your VNX series efficiently. Consultants evaluate your business, IT processes, and technology and recommend ways you can leverage your information for the most benefit. From business plan to implementation, you get the experience and expertise you need, without straining your IT staff or hiring and training new personnel. Contact your EMC representative for more information. 110 of 114 Release 7.
Index A Audit audit the Control Station 67 Automatic Collection and Transfer tool command options 102 configuring 98 described 97 disabling 101 running from the CLI 102 user command examples 103 using for problem reporting 97 C command error log 93 command log 93 Control Station enabling daemons 58 halting locally 46 halting remotely 47 locally rebooting 48 primary 46, 47, 48, 49 remotely rebooting 49 secondary 46, 47, 48, 49 D daemon Control Station 58 HTTPD 58 Data Mover time zone setting 62 Data Movers
Control Station locally 48 remotely 49 Data Movers 52 VNX7500 23 VNXcabinet emergency shutdown 44 Z S zone, time, setting 62 SCSI devices discovering 59 saving 53, 60 secondary Control Station 46, 47, 48, 49 server log 89 server_cpu halt Data Movers 51 reboot Data Movers 52 server_date setting time zone 62 setting date and time 66, 71, 107 server_devconfig, discovering SCSI devices 59 server_netstat 108 server_stats 106 server_sysstat 108 server_version, verifying Data Mover software version 61 setting
Notes VNX™ System Operations Release 7.
About this document As part of its effort to continuously improve and enhance the performance and capabilities of the VNX product line, EMC periodically releases new versions of VNX hardware and software. Therefore, some functions described in this document may not be supported by all versions of VNX software or hardware presently in use. For the most up-to-date information on product features, see your product release notes.
