HP VMA-series Memory Array Installation and Service Guide Abstract This document describes the installation and service procedures for the HP VMA-series Memory Array. This document is intended for experienced service technicians. HP assumes that you are qualified in the servicing of computer equipment, are trained in recognizing hazards in products with hazardous energy levels, and are familiar with weight and stability precautions for rack installations.
LEGAL NOTICES © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Copyright © 2010-2011 Violin Memory, Inc. All rights reserved.
COMPLIANCE INFORMATION Notice Description FCC Class A “This device complies with Part 15 of the FCC Rules. Operation is subject to the following Compliance two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.” This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules.
VMA-series Memory Array Installation and Service Guide HP-AM456-9002A Rev 01
Table of Contents List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 PART I. Product Overview CHAPTER 1. VMA-series Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Features . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Connecting the PCIe Cable to the Memory Array. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 Connecting Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying the System Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Setting the System Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Displaying the System Clock Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Loading Linux Drivers Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Loading Linux Drivers as Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Unloading the Linux Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Connected Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Electrostatic Discharge (ESD) Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lithium Battery Caution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents context controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 context fan-tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Board 0 Context Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Context Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 cancel reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . clear log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents show path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Uptime Context Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 show. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Figures Figure 1.1 Figure 1.2 Figure 1.3 Figure 1.4 Figure 1.5 Figure 1.6 Figure 2.1 Figure 2.2 Figure 3.1 Figure 3.2 Figure 3.3 Figure 3.4 Figure 3.5 Figure 3.6 Figure 3.7 Figure 3.8 Figure 3.9 Figure 3.10 Figure 6.1 Figure 6.2 Figure 6.3 Figure 7.1 Figure B.1 Figure C.1 Figure D.1 Figure D.2 Figure D.3 Figure D.4 Figure D.5 Figure D.6 Figure D.7 Memory Array - Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Figures Figure D.8 Figure D.9 Figure D.10 Figure D.11 Figure D.12 Figure D.13 Figure D.14 Figure D.15 Figure D.16 Figure D.17 Figure D.18 Figure D.19 Figure D.20 Figure D.21 Figure D.22 Figure D.23 Figure D.24 Figure D.25 Figure D.26 14 Chassis>Controller>Ethernet Context Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chassis>Fan Tray Context Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Tables Table 1.1 Table 1.2 Table 1.3 Table 1.4 Table 2.1 Table 2.2 Table 2.3 Table 3.1 Table 3.2 Table 3.3 Table 3.4 Table 3.5 Table 4.1 Table 4.2 Table 4.3 Table 5.1 Table 5.2 Table 5.3 Table 7.1 Table 8.1 Table 9.1 Table 9.2 Table A.1 Table D.1 Table D.2 Table D.3 Table D.4 Table D.5 Table D.6 Table D.7 Table D.8 Front LED Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Rear LED Descriptions . .
List of Tables Table D.9 Table D.10 Table D.11 Table D.12 Table D.13 Table D.14 Table D.15 Table D.16 Table D.17 Table D.18 Table D.19 Table D.20 Table D.21 Table D.22 Table D.23 Table D.24 Table D.25 Table D.26 Table D.27 Table D.28 Table D.29 16 Controller Context Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fan-tray Context Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface This document describes how to install and service the Memory Array. • Document Organization on page 17 • Security on page 19 • Document Conventions on page 18 • Reference Documents on page 19 • Contacting HP on page 19 Document Organization This guide is organized into the following sections: • PART I: Product Overview – • Chapter 1, VMA-series Overview—Introduces the Memory Array and its features, components, and specifications.
Preface – • Chapter 7, Linux Drivers—Describes how to install, use, and remove the Linux drivers on a host computer directly attached to the Memory Array. – Chapter 8, Windows Drivers—Describes how to install, use, and remove the Windows drivers on a host computer directly attached to the Memory Array. – Chapter 9, Violin Utilities—Describes the Memory Array utility commands and how to use them.
Security Typographical Conventions The table below summarizes the typographical conventions used in this guide. Typographical Conventions Format Meaning Bold User Interface text. Italic Provides emphasis and identifies variables and document titles. Courier Command names, examples, and output. Courier bold Input you must type exactly as shown. Information for which you must supply a value. [ ] Optional command parameters are enclosed within square brackets.
Preface • Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored. • If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more information about Care Packs, refer to the HP website (http:// www.hp.com/hps). • In other locations, see the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/en/wwcontact.html).
PART I Product Overview Chapter 1 VMA-series Overview Chapter 2 Violin Intelligent Memory Modules
CHAPTER 1 VMA-series Overview This chapter introduces the VMA-series Memory Array, The VMA-series Memory Array is the result of a partnership with Violin Memory, Inc. and is based on the Violin 3000 Series Memory Array. HP and Violin have jointly tested and certified the system with Linux, Windows, and HP-UX servers.
Chapter 1 - VMA-series Overview Features The Memory Array: • Combines standard memory technology and Violin intelligence to create a high-bandwidth, high IOPS, low latency, cost-effective memory array. • Operates as a direct-attached or SAN-attached (vSHARE) storage system that can be used for swap space, file systems, or exported as raw Logical Unit Numbers (LUNs) or devices. Supports fast random or sequential access operations as there are no mechanical heads to move or spindles to spin.
Physical Components The power button on the front of the array can be used to cause the array to enter into a shutdown mode similar to executing the shutdown CLI command. With a shutdown the media is taken offline and I/O stopped to the connected hosts, but the array is left powered on and able to be managed via the CLI. Use the reboot CLI command to bring the array media back online and allow I/O to the connected hosts. To shut down the system from the front panel, depress the power button for 4 seconds.
Chapter 1 - VMA-series Overview Front LEDs O K ST AT U S AL AR M DC AC O K The front LEDs are illustrated in the figure below. A RAID B ADMIN Figure 1.3 Front System Status LEDs The front LEDs are described in the following table. Table 1.1 Front LED Descriptions System A/B RAID/ADMIN LED Label Color When Lit Description AC OK Indicates that the AC power feed to Power Supplies A and B are connected correctly.
Physical Components Rear LEDs The rear LEDs are illustrated in the figure below: A RAID O K B AC LOC C Figure 1.4 Rear System LEDs The Rear LEDs are described in the following table. Table 1.2 Rear LED Descriptions LED Label Status Description Indicates the system status. When lit, the LED could be: Color When Lit Green • Flashing slowly—Indicates that the system monitor is booting up.
Chapter 1 - VMA-series Overview The power supplies convert the incoming AC power from individual AC feeds to DC power used by the system. These 1200 W power supplies are redundant in their configuration. The power supplies are hot-swappable at any time. See Connecting the AC Power Cords to the System on page 47 for more information. The power requirements for the Memory Array are based on the VIMM configuration used.
Connectivity and Interfaces Overview Refer to Figure 1.2 for interface locations. Management Interfaces Access to the system command line interface (CLI) is available through the following interfaces: • DB-9 Serial Debug Interface—Opens the CLI on the system. • Ethernet Interface—Opens the CLI on the system via Telnet or Secure Shell (SSH). See Connecting the Serial Cable on page 50 and Connecting the Ethernet Cable on page 51 for information.
Chapter 1 - VMA-series Overview Once a Memory Array is connected to a host computer it can be partitioned into multiple volumes or virtual disks. Both Windows and Linux drivers are supplied for the specific operating system used on the host. For data transfers, there are two PCIe x8 interface ports on the rear of the Memory Array. These interfaces support either single x8 or dual x4 PCIe connections. The port configuration is determined by the firmware image loaded on the system.
System Specifications System Specifications The table below lists the Memory Array system specifications. Table 1.
Chapter 1 - VMA-series Overview Table 1.4 Direct-attached Host Computer Requirements Minimum Requirements Supported Operating Systems: • Red Hat Enterprise Linux 5.6 • SUSE Linux Enterprise Server 11 SP1 • Windows Server 2008 R2 Serial communications application, such as vtkermit, tip, minicom, kermit, hyperterm, teraterm, and PuTTY See Connecting the PCIe Cable to a Host Computer or Memory Gateway on page 53 for more information.
CHAPTER 2 Violin Intelligent Memory Modules This chapter describes the Violin Intelligent Memory Module (VIMM) technology, types, configurations, and slot locations in the following sections: HP-AM456-9002A Rev 01 • Violin Intelligent Memory Modules (VIMMs) on page 34 • VIMM Types on page 34 • VIMM Configurations on page 35 • VIMM Slot Locations on page 35 VMA-series Memory Array Installation and Service Guide 33
Chapter 2 - Violin Intelligent Memory Modules Violin Intelligent Memory Modules (VIMMs) A VIMM, illustrated in Figure 2.1: • Contains memory and interconnect diagnostics and error correction for data reliability. • Offers data protection via a flash RAID (4+1Parity) function that provides fault tolerance and low latency access to flash. A fully populated system contains up to sixteen Parity VIMMs and four spare VIMMs for failure protection.
VIMM Configurations Memory arrays store up to 64, 128, 256, or 512 GB of data per memory module providing up to 43 TB of raw flash storage per system. The amount of usable memory in a system is the number of VIMMs used for data storage, which is four per redundant array of independent disks (RAID) group (up to 64 VIMMs), multiplied by the amount of memory per module, multiplied by the usable percentage the system is formatted for.
Chapter 2 - Violin Intelligent Memory Modules 42–Module Configuration For this configuration VIMMs must be placed in the slot locations illustrated in the following figure. 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 Fans Fans Fans Figure 2.
PART II Operation Chapter 3 Installing the Array Chapter 4 Configuring the Array Chapter 5 Operating the System via the CLI Chapter 6 Servicing the Array
CHAPTER 3 Installing the Array This chapter describes how to install the Memory Array in the following sections.
Chapter 3 - Installing the Array Installation and Configuration Overview Memory Array installation and configuration occurs in five distinct phases: • Phase 1: Hardware Installation • Phase 2: Memory Array Configuration • Phase 3: Storage Configuration • Phase 4: Performance Testing and Tuning • Phase 5: Monitoring and Troubleshooting PHASE 1: Hardware Installation 1 Unpacking Components 3 Connecting 2 Rack-Mounting PHASE 2: Memory Array Configuration 4 Connecting PCIe Cables the Chassis
Installation and Configuration Overview Chapter 9, Violin Utilities. Phase 5, monitoring and troubleshooting is described in Chapter 6, Servicing the Array and Chapter 9, Violin Utilities. Required Installation Tools and Equipment The table below lists the tools and equipment required during the installation process. Table 3.1 Required Installation Tools and Equipment Item # HP-AM456-9002A Rev 01 Item Description Quantity 1 Laptop for console access. DB-9 serial connector or USB-to-DB-9 cable/dongle.
Chapter 3 - Installing the Array Rack-Mounting the Chassis Installing the Memory Array in a 19" Equipment Rack The Memory Array fits into a standard 19" (482.6 mm) wide, four-post rack with sliding rails as specified by EIA-310-D, IEC 60297, and DIN 41494 SC48D. Square hole racks are supported. Since there are a variety of 19" equipment racks available, the rack mounting brackets can be configured in several ways to accommodate a range of frontrear post spacings–from 24" to 32".
Rack-Mounting the Chassis Figure 3.2 Installing the Memory Array into a Rack To install the Memory Array into a 19" equipment rack: 1. Remove the Memory Array from the shipping packaging and remove all packing materials. Visually inspect the system for any shipping damage and, if any damage is detected, contact HP Customer Support for replacement parts. 2. Install the toolless mounting rails at the appropriate height in your equipment rack. Orient the rails so they slide out to the front of the rack.
Chapter 3 - Installing the Array To install the cable management arm: 1. At the rear of the chassis, remove the shoulder screws and shims from the rear equipment frame mounting bracket and set aside. Orient the cable management arm mounting bracket on the right, as illustrated in the figure below. Figure 3.3 Installing the Cable Management Arm Mounting Bracket 44 2. Align the thumb screws on the cable management arm mounting bracket with the installation holes on the right rear of the chassis.
Rack-Mounting the Chassis Figure 3.
Chapter 3 - Installing the Array Connecting the PCIe Cable to the Memory Array The Memory Array communicates with the host computer via the PCIe (Peripheral Component Interconnect Express) connection. The PCIe cable must be connected to the PCIe port with the flashing LED. The software image on the system dictates which interface port is used. The image names are listed in the table below. Table 3.2 Image Names Image Name PCIe Interface Interface ID v3000_Series_x8_p1_df-.
Connecting Power Connecting Power Powering down the system processor interrupts traffic and causes loss of system logs and diagnostic data. To preserve this diagnostic data it is recommended that the vincident and/or save log commands be used prior to powering down the system. WARNING! It is recommended to reboot the system rather than powering down then up. Using a syslog server also ensures logs are stored prior to any reboot or power down.
Chapter 3 - Installing the Array The AC power cords are not a standard configuration. Use only the AC power cords supplied with your system. Note: To connect the AC power cords to the system: Locate the AC power receptacles at the rear of the system, as shown in the figure below. RAID ADMIN AC O K A B DC O K STA TU S ALA RM 1. Power Supply A LOC Power Supply B Figure 3.6 AC Power Receptacle Locations 2.
Connecting Power 2. Route the equipment ground cable to the rear of the equipment. Be sure to leave an appropriate service loop to allow the removal of the equipment on the slide rails. If using the cable management arm, route the equipment ground wire around the arm. See Routing the Cables onto the Cable Management Arm on page 55. 3. Cut the length of the ground wire at the rear of the equipment as needed for proper fit.
Chapter 3 - Installing the Array Connecting Management Network Connecting the Serial Cable The serial null modem cable connects the host computer to the system’s debugging interface to retrieve system status and troubleshoot system events. The default serial port settings are shown in the following table. Table 3.
Connecting Management Network AC O K RAID ADMIN DC O K STA TU S ALA RM A B LOC Serial Console Figure 3.7 Connecting the Serial Cable to the Memory Array 2. If using the cable management arm, route the serial cable according to the instructions in Routing the Cables onto the Cable Management Arm on page 55. 3. At the rear of the host computer, plug the other end of the serial cable into the male DB-9 connector, see Figure 3.8. Secure the connection by tightening the screws on the DB-9 connector.
Chapter 3 - Installing the Array AC O K RAID ADMIN DC O K STA TU S ALA RM A B LOC Ethernet Port Figure 3.9 Connecting the Ethernet Cable to the Memory Array 52 2. If using the cable management arm, route the Ethernet cable according to the instructions in Routing the Cables onto the Cable Management Arm on page 55. 3. If directly connecting the Memory Array to a host machine, plug the other end of the cable into the Ethernet connector on the host. 4.
Connecting the PCIe Cable to a Host Computer or Memory Gateway Connecting the PCIe Cable to a Host Computer or Memory Gateway The Memory Array is connected via external PCIe cables (PCIe x8 cables) to one or two host computer(s) or memory gateway(s). Hosts support applications, such as databases, and run operating systems such as Linux or Windows. Memory gateways provide network connectivity to SANs or LANs.
Chapter 3 - Installing the Array Memory Gateway The steps for connecting the Memory Array to a memory gateway are: 1. Orient the unconnected end of the PCIe cable(s) to align with the PCIe connector on the back of the Memory Gateway. The PCIe cable is keyed and only goes in one way. 2. Securely plug the cable(s) into the PCIe connector. 3. Power-up the Memory Array (see Powering up the Memory Array on page 56).
Routing the Cables onto the Cable Management Arm Routing the Cables onto the Cable Management Arm After installing the Memory Array in an equipment rack and attaching the necessary cables at the rear of the system, route the cables along the cable management arm to prevent them from becoming entangled when the system is fully extended from the equipment rack. Route the cables along the length of the arm and hold in place with cable ties. To route the cables along the cable management arm: 1.
Chapter 3 - Installing the Array Powering up the Memory Array After connecting the AC power cords to the Memory Array, and connecting the PCIe, Ethernet, and serial cables between the Memory Array and the host computer or memory gateway, apply power to the Memory Array. To complete the power up sequence: 1. Plug each AC power cord from the chassis into an AC outlet. 2. On the Memory Array, press the power button to start the system boot process. The LEDs will begin to light up.
CHAPTER 4 Configuring the Array When the Memory Array is first powered on, all configuration settings are set to default values. You must change the default settings to communicate with the Memory Array over your network(s). This chapter explains how to log into the Memory Array’s command line interface (CLI) to change system settings, such as the hostname, IP address, DNS, and syslog options in the following sections.
Chapter 4 - Configuring the Array Memory Array Default Settings The Memory Array has the system default settings listed in Table 4.1. Change these settings using the CLI over a Telnet/SSH session or the serial port on the Memory Array. See Changing the Default System Settings on page 62. Table 4.1 Memory Array System Default Settings Setting 58 Default Value Host Name violin IP Address 192.168.1.2 (static) IP Netmask 255.255.255.
Connecting to the CLI Connecting to the CLI Logging into the CLI via the Serial Interface Access the Command Line Interface (CLI) through the serial connection between the host computer and the Memory Array. This connection was set up when the equipment was installed into its permanent location. See Connecting the Serial Cable on page 50. See Table 3.4 on page 50 for the serial interface default values. Your settings for the console connection may vary from the listed default settings.
Chapter 4 - Configuring the Array Logging in to the CLI via a Linux host computer Connect to the Memory Array using the Kermit application or another terminal application, such as tip, if your system does not have Kermit. Save the Kermit parameter settings in a .kermrc file so that you do not need to type them each time you connect. The Violin Utilities package for Linux includes Violin’s version of Kermit called vtkermit. Place the .
Connecting to the CLI 9. At this point, you are connected to the CLI of the Memory Array and can access the various CLI commands. To close the Kermit application, do one of the following: At the CLI prompt, type Ctrl-\, c, and then q. b. Close the terminal window, which terminates the Kermit connection. a.
Chapter 4 - Configuring the Array Changing the Default System Settings Table 4.1, Memory Array System Default Settings, on page 58 lists the system configuration default values. When you initially log into the Memory Array through the serial interface, change the following default configuration parameters for security and ease of use. Table 4.2 Changing the Default System Settings Setting Details Hostname See Changing the Hostname.
Changing the Default System Settings You will be prompted to enter a new password. If the new password meets the requirements you will be prompted to enter the same password again. A message appears indicating that the password has been changed. The command displays information similar to the following if the new password does not meet the requirements.
Chapter 4 - Configuring the Array When you change the IP address of the system, you will be logged off. Log in again using the new IP address. Note: To change the system’s IP address, netmask, and gateway from the default values: 1. Log into the Memory Array. Use Kermit or vtkermit, instead of Telnet, to change the IP address in case the IP address is set incorrectly. Note: 2. Navigate to the Ethernet 0 context level. At the root prompt, type: context chassis controller ethernet 0 3.
Configuring DHCP Settings Configuring DHCP Settings Configure several DHCP settings and DNS information automatically or manually on the Memory Array. Displaying DHCP Status Display whether or not DHCP is being used to automatically set the system’s IP address. By default DHCP is disabled. 1. Log into the Memory Array. 2. Navigate to the Ethernet 0 context level. At the root prompt, type: context chassis controller ethernet 0 3.
Chapter 4 - Configuring the Array Disabling DHCP Disable DHCP to manually set the Memory Array’s IP address. This is the system default setting. 1. Log into the Memory Array. 2. Navigate to the Ethernet 0 context level. At the root prompt, type: context chassis controller ethernet 0 3. At the Ethernet 0 context prompt, type: set dhcp disabled 4.
Configuring Domain Name System (DNS) Configuring Domain Name System (DNS) There are two available methods for configuring DNS on the Memory Array: 1. Automatic DNS configuration 2. Manual DNS configuration The Memory Array also allows pre-provisioning the DNS information to use when you change your system from automatic DNS configuration to manual.
Chapter 4 - Configuring the Array Configuring the DNS Search Domain Name When in automatic DNS mode and you set the DNS search domain name, you are pre-provisioning the value. It is not used until you change the DNS mode to manual. You can configure the DNS search domain name at any time. To specify the search domain name of the Memory Array: 1. Log into the CLI via a serial connection or the Ethernet interface (see Connecting to the CLI on page 59). 2. Navigate to the Ethernet 0 context level.
Configuring Domain Name System (DNS) 3. At the Ethernet 0 context prompt, type: show If DNS is currently in automatic mode, then the status for dns-config displays automatic. In the following example, the DNS name server IP address and the DNS search domain values have been pre-provisioned. chassis controller ethernet 0> show dhcp enabled ip-address 10.10.0.126 netmask 255.255.255.0 gateway 10.10.0.1 mac-address 00:1B:97:00:00:06 dns-config automatic dns-nameserver 10.10.0.2 dns-search violintech.
Chapter 4 - Configuring the Array Verifying the Ethernet Connection The Ethernet interface can also be used to connect to the CLI of the Memory Array. This section explains how to verify that the Ethernet connection is operating properly. To verify the Ethernet connection: 1. Log in to the host computer, as root on a Linux host or as an administrator on a Windows host. 2. To retrieve the IP address of the Memory Array, do one of the following: a.
Displaying and Setting System Log (Syslog) Options Displaying and Setting System Log (Syslog) Options The Memory Array logs system messages that can be sent to a host running a syslog server for long term storage. If numerous messages are generated, then the log buffer may fill up and, since it is a circular buffer, overwrite older messages. The message level mapping between the message level definitions and your host’s syslog message level definitions are listed in Table 4.3. View the man page for syslog.
Chapter 4 - Configuring the Array Setting the IP Address for the Syslog Host Send system log messages to a host attached to the Memory Array via the Ethernet port. This host must have syslog configured correctly. See your host’s syslog documentation for instructions. From the CLI prompt, use the ping command to verify the connection between the Memory Array and the remote syslog host. Note: To set the IP address of the host to which the system log messages will be sent: 1. Log into the Memory Array. 2.
Displaying and Setting System Log (Syslog) Options The command displays information similar to the following: system logging syslog> show service service on Sending the System Log to a Host Start or stop the service to send the system log messages to a host. By default, it is off. To set the status of the system log service: 1. Log into the Memory Array. 2. Navigate to the Syslog context level. At the root prompt, type: context system logging syslog 3.
Chapter 4 - Configuring the Array Formatting the Memory Array The array is formatted to 65% usable capacity at the factory and can be used without change. Note: To change the format of the Memory Array: 1. Log into the Memory Array. 2. At the root CLI prompt, type: format flash-capacity [] Where: value Specifies the percentage of usable flash capacity. Valid values are: • • • • • • 50 65 78 84 87 90 — Not recommended for high performance or high reliability systems. Default is 65%.
CHAPTER 5 Operating the System via the CLI The CLI resides on the Memory Array and is used to retrieve system status and set configuration information.
Chapter 5 - Operating the System via the CLI Connecting to the CLI Connect to the Memory Array’s CLI via SSH or Telnet on the host computer over the Ethernet interface. You can also log into the system via the serial port. See Logging into the CLI via the Serial Interface on page 59 for instructions. To connect to the Memory Array from a Windows machine, see Logging in via a Windows host computer on page 59. The default command line editor for the admin user is Emacs.
Connecting to the CLI To connect to the Memory Array from a Windows machine, see Logging in via a Windows host computer on page 59. Note: To connect to the Memory Array from a Linux desktop: 1. Right-click on the desktop and select Open Terminal. At the command prompt in the terminal window, type: telnet Where: ip_address HP-AM456-9002A Rev 01 Specifies the IP address of the Memory Array. 2. At the login prompt, type the user login name (default is admin). 3.
Chapter 5 - Operating the System via the CLI [root@lab5 ~]# telnet 10.10.20.4 Trying 10.10.20.4... Connected to 10.10.20.4. Escape character is '^]'. violin login: admin Password: ..... ..... ..... ..... ..... ~ ..... ~ ..... ~ ..... ~ ..... ~ ..... ~ ~ ~ ..... ~ ___ ___ ..... ~ || // o / o .. ~ || // .--. / /_-_ ~ ||// / / / / / / / ~ ||/ / /___/ / / / / ~ ___ ___ ~ ~ //| //| ~ //|| //|| .--. /_ _ .--. /.-- . . // ||// || /__/ / / / / / / / / // ||/ || /__ / / / /___/ / /__/ / http://www.violin-memory.
Displaying and Setting the CLI Window Options Displaying and Setting the CLI Window Options The settings for the terminal window displaying the current CLI session can be modified to suit your display equipment. You can set or retrieve the following window display options: • Number of columns and lines in the display window • Pagination • Command line editing mode • Size of the history buffer Displaying the Number of Columns To view the number of columns in the current CLI display window: 1.
Chapter 5 - Operating the System via the CLI Displaying the Command Line Edit Mode 1. Log into the Memory Array. 2. Navigate to the CLI context level. At the root prompt, type: context cli 3. At the CLI context prompt, type: show edit-mode The command displays information similar to the following:. cli> show edit-mode Current edit-mode setting is: emacs Setting the Command Line Editor Set the command line editor to either Emacs or vi for the current CLI session. The default editing mode is Emacs. 1.
Displaying and Setting the CLI Window Options The command displays information similar to the following: cli> show history-size Current history-size setting is: 100 Setting the History Buffer Size Modify the size of the history buffer to hold from 10-1000 lines. To modify the number of lines in the history buffer: 1. Log into the Memory Array. 2. Navigate to the CLI context level. At the root prompt, type: context cli 3.
Chapter 5 - Operating the System via the CLI Displaying the Pagination Mode To view whether pagination is enabled or disabled in the current CLI window: 1. Log into the Memory Array. 2. Navigate to the CLI context level. At the root prompt, type: context cli 3. At the CLI context prompt, type: show pagination The command displays information similar to the following:. cli> show pagination Current pagination setting is: on Setting the Pagination Mode Enable or disable pagination in the CLI window.
Displaying and Setting System Information Displaying and Setting System Information You can display and set various system information such as the system date and time, system operational time, the system’s IP address, the log, spare VIMM information, and RAID group mapping. The following sections describe how to display and set this information. Displaying System Status Information Display the status of the various software modules and the validity of the current VIMM configuration. 1.
Chapter 5 - Operating the System via the CLI slot state protocol link-width neg-link-width max-data-rate cfg-data-rate host slot state host port-2 enabled pcie 4 4 10 Gb/s 10 Gb/s detected port-0 disabled undetected If the VIMM configuration is invalid, or the system is rebuilding the RAID groups, then up to two extra lines are displayed that list: • ID numbers of the affected VIMMs • When the RAID group rebuild is active • Affected RAID group and VIMM Displaying the System Operational Time Display
Displaying and Setting System Information Displays how long the system has been operational since the last power cycle or system reboot in year, day, hour formats. time Displaying the System Date and Time 1. Log into the Memory Array. 2. Navigate to the System context level. At the root prompt, type: context system 3. At the System context prompt, type: show clock The command displays information similar to the following:.
Chapter 5 - Operating the System via the CLI Displaying the System Clock Source The clock source can be the host computer or the Memory Array. 1. Log into the Memory Array. 2. Navigate to the System context level. At the root prompt, type: context system 3. At the System context prompt, type: show clock-source The command displays information similar to the following:.
Displaying and Setting System Information The command displays information similar to the following: system version> show software version: software build date: software build info: 12:44:52 built on swbuild.violintech.
Chapter 5 - Operating the System via the CLI 2. Navigate to the Ethernet 0 context level. At the root prompt, type: context chassis controller ethernet 0 3. At the Ethernet 0 context prompt, type: show The command displays text similar to the following: chassis controller ethernet 0> show dhcp ip-address netmask gateway mac-address dns-config dns-nameserver dns-search provisioned-info prov-ip-address prov-netmask enabled 10.10.0.126 255.255.255.0 10.10.0.1 00:1B:97:00:00:05 automatic 10.10.0.2 domain.
Displaying and Setting System Information 1. From the CLI prompt, type: show chassis controller ethernet 0 2. Log into the host computer and type: vinfo To add the Memory Array’s MAC address to your DHCP server, consult your DHCP server documentation. Clearing Provisioned IP Information Provisioned IP address information can be cleared at any time. 1. Log into the CLI via a serial connection or the Ethernet interface (see Connecting to the CLI on page 76). 2.
Chapter 5 - Operating the System via the CLI 3. At the Ethernet 0 context prompt, type: clear dns-nameserver clear dns-search 4. To commit the changes made, at the System context level command prompt, type: save config Displaying the VIMM RAID Group Mapping The Memory Array supports up to 16 RAID groups per system. Each RAID group can contain up to five VIMMs and supports data striping across the VIMMs and RAID groups. Four VIMMs in a RAID group contain data and one contains parity information.
Displaying and Setting System Information state Indicates the state of the VIMM in the 5-VIMM RAID group. Valid values are: • data—VIMM is being used for data, either user data or parity data. • REBUILDING—VIMM is currently being rebuilt by the RAID engine to recover from a prior failure. • FAULT—A fault has occurred for this VIMM. If a spare is available, a rebuild occurs for this virtual VIMM.
Chapter 5 - Operating the System via the CLI Displaying and Setting Hardware Information Display hardware information for the Memory Array, including: • Fan tray status • Which slots are populated with VIMMs • Individual VIMM information • Test slots • System LEDs Displaying VIMM Configuration Information Display the VIMM configuration information at the Slot context level. To display the VIMM configuration information: 1. Log into the Memory Array. 2.
Displaying and Setting Hardware Information sw-date sw-version is-programmed id-assigned environment temperature sensor-1.2v sensor-1.8v sensor-2.5v sensor-3.
Chapter 5 - Operating the System via the CLI 3. At the context prompt, type: show vimm-summary The command displays information similar to the following: chassis board 0> show vimm-summary num-vimms installed-vimm-ids flash-vimm-ids admin-down-vimm-ids installed-mem-raw usable-mem-raw parity-mem-raw spare-mem-raw unavailable-mem-raw formatted-percentage usable-mem-formatted 42 3-8,12-18,22-27,35,38-45,48,60,64-69,71,75,76,78-80 3-8,12-18,22-27,35,38-45,48,60,64-69,71,75,76,78-80 39 2886.
Displaying and Setting Hardware Information The command displays information similar to the following:. chassis fan-tray 1> show fan left speed rpm high 4800 Displaying Main Board Information 1. Log into the Memory Array. 2. Navigate to the Board 0 context level. At the root prompt, type: context chassis board 0 3. At the context prompt, type: show info The command displays information similar to the following:.
Chapter 5 - Operating the System via the CLI Displaying Alarms and Logs Display the current alarms that light the System LED on the Memory Array to help prevent system damage in the case of a fan failure, lid removal, or to diagnose performance problems when one or more VIMMs are affected by high temperatures. See Appendix C, Alarm Reference for more information on alarms.
Displaying Alarms and Logs The command displays information similar to the following: system> show log xxx xx xx:xx:xx [000000000] INFO vtu_log_init(): ------------ LOG RESTART -----------xxx xx xx:xx:xx [000000010] INFO ecpu_hwmgr_init(): Running fans at full speed xxx xx xx:xx:xx [000000010] INFO main(): Main controller build ID: 12954 xxx xx xx:xx:xx [000000010] INFO main(): S/W Rel: , Built: 12:16:39 on swbuild.violintech.
Chapter 5 - Operating the System via the CLI Rebooting the Memory Array When you reboot the Memory Array, you must specify which processors to restart. The two processors are: 1. System—Contains the software that manages the VIMM topology. Restarting the system processor interrupts traffic and causes loss of some older system logs and diagnostic data. To preserve this diagnostic data it is recommended that the vincident and/or save log commands be used prior to reboot.
Rebooting the Memory Array 2. Navigate to the System context level. At the root prompt, type: cancel reboot 3. You will be prompted to confirm the cancelation of the reboot. Type y to confirm cancelling the reboot or type n to keep the scheduled reboot. Displaying the Scheduled Reboot To display when a reboot is scheduled to run: 1. Log into the Memory Array. 2. Navigate to the System context level. At the root prompt, type: context system 3.
Chapter 5 - Operating the System via the CLI Upgrading the System Software To upgrade the software on the Memory Array, perform the following steps: 1. Copy the upgrade image to a location on a host that is accessible to the Memory Array target system using FTP, HTTP, NFS, SCP, SFTP, or TFTP. 2. Set the upgrade path to the above location. The upgrade image will download to the upgrade partition of the Memory Array. 3. Set the upgrade partition to activate upon bootup. 4. Schedule the system reboot.
Upgrading the System Software Specify the path to the upgrade image using one of the methods listed in the following table. Table 5.3 Downloading Methods and Example Paths Using Path Description FTP @ftp:////.upg bob@ftp://10.10.0.15/pub/vtms-array-firmware-x8-A3.7.2-18919.upg HTTP http:////.upg http://10.10.0.15/vtms-array-firmware-x8-A3.7.2-18919.upg NFS nfs:////.upg nfs://10.10.0.
Chapter 5 - Operating the System via the CLI host_ip_addr Specifies the IP address of the host. path Specifies the path location of the upgrade file on the host. upgr_image Specifies the file name of the upgrade image. Make sure to use the appropriate image for your application. You are prompted to confirm the download of the upgrade software. Upon confirmation, the upgrade software is downloaded to RAM on the main board and then copied into the upgrade partition of flash.
Upgrading the System Software 4. Specify the system processor to restart when the system reboots. At the root context prompt, type: reboot system all The command displays information similar to the following: > reboot system all Do you wish to reboot the specified processor(s) now (Y/N)? y Scheduling an immediate reboot. > SYSTEM REBOOTING....... The reboot request has succeeded. 5. While the system is rebooting, reboot your host computer.
Chapter 5 - Operating the System via the CLI 3. Set the system processor to restart when the system reboots. At the root context prompt, type: reboot system all WARNING! This procedure interrupts service. The command displays information similar to the following: > reboot system all Do you wish to reboot all processors now (Y/N)? y Scheduling an immediate reboot. > SYSTEM REBOOTING....... The reboot request has succeeded.
Upgrading the System Software 4. While the system is rebooting, reboot your host server. 5. Log back into the Memory Array when it is finished rebooting. Displaying the Upgrade Path After setting the upgrade path, and before the system reboots, display the path to the upgrade software. 1. Log into the Memory Array. 2. Navigate to the Sw-upgrade context level. At the root prompt, type: context system sw-upgrade 3.
Chapter 5 - Operating the System via the CLI 106 VMA-series Memory Array Installation and Service Guide HP-AM456-9002A Rev 01
CHAPTER 6 Servicing the Array This chapter describes how to service the Memory Array by following safety precautions while replacing the fan trays, AC power supplies, and VIMMs in the following sections.
Chapter 6 - Servicing the Array Guidelines for Servicing the System Only authorized, qualified, and trained personnel should attempt to service or maintain this equipment. WARNING! Caution: Read this guideline section before proceeding with any of the service procedures. See System LEDs on page 25 for detailed information on the system LEDs located on the front and rear of the Memory Array.
Testing the LEDs Testing the LEDs Perform functional tests on the LEDs associated with the VIMM slots and the system LEDs located on the front and rear of the Memory Array. Displaying the Status of the System LEDs 1. Log into the Memory Array. 2. Navigate to the System context level. At the root prompt, type: context system 3. At the context prompt, type: show led-state The command displays information similar to the following:.
Chapter 6 - Servicing the Array Where: n 3. Specifies the VIMM slot ID. Valid values are in the range of 083, inclusive. At the context prompt, type: show led-state The command displays information similar to the following:. chassis board 0 slot 12> show led-state led-state slow-flash Testing the VIMM LEDs Test the LEDs associated with a specific VIMM. The slot ID is specified when you navigate to the Slot context level.
Replacing the Fans Replacing the Fans The six fans are installed prior to shipping, but may need to be replaced in the unlikely event of a fan failure. The fans are hot-swappable components and can be replaced while the Memory Array is in-service. WARNING! Allow the fans to slow down before removing them.
Chapter 6 - Servicing the Array Replacing the AC Power Supplies The redundant AC power supplies can be hot-swapped at any time if one fails during operation of the Memory Array. To replace an AC power supply: 1. At the rear of theMemory Array, disconnect the AC power cord from the system and the wall outlet. 2. Remove the module by pushing on the green tab at the right of the power supply faceplate and pulling the power supply firmly by the handle over the fan, as illustrated in the figure below.
Replacing VIMMs Replacing VIMMs There are up to four spare VIMMs in the Memory Array system. If a VIMM experiences errors: • Route the data to a spare VIMM. • Remove the errored VIMM from the RAID group. • Power down the slot in which the VIMM is located. • Replace the errored VIMM with a new, working VIMM and place as a spare in the system. Wear a grounding strap that has been attached to the Memory Array chassis to avoid damage from static electricity. Caution: To replace a VIMM: 1.
Chapter 6 - Servicing the Array 5. Press firmly down on the latches until the VIMM disengages from the slot. Lift the VIMM out straight vertically to avoid shorting the pins and place in a static bag. 6. Align the new VIMM with the empty slot, as shown in the following figure. VIMM Latches Figure 6.3 Inserting the Replacement VIMM 7. Firmly press the VIMM into the slot until the latches click close.
PART III Host Utilities Chapter 7 Linux Drivers Chapter 8 Windows Drivers Chapter 9 Violin Utilities Chapter 10 Performance Tuning and Troubleshooting
CHAPTER 7 Linux Drivers This chapter describes the configuration of a direct-attached Memory Array system using a Linux host. Topics covered include system prerequisites, installation of the Linux drivers, installation of the Violin Utilities, and creation of block device partitions.
Chapter 7 - Linux Drivers Linux Drivers Overview In a direct-attached configuration, the Linux driver enables the host (a Linux machine) to access block storage on a Memory Array. The Linux driver (vtms-linux-driver) must be installed on the host machine if the Memory Array is to be directly attached to a Linux host. If the Memory Array is to be directly attached to a Windows host, see Windows Drivers on page 135.
Installing Linux Driver Prerequisites In general, the configuration of a direct-attached Memory Array system using a Linux host is a five-step process. PHASE 3: Direct-Attach Configuration (Linux) Installing Prerequisites Building and Installing Drivers 1 Loading Device Drivers 2 3 Installing Scripts and Utilities 4 Creating Partitions 5 Figure 7.
Chapter 7 - Linux Drivers If a kernel was custom built from http://kernel.org/ sources, the kernel build tree must be available for the Linux driver to reference. GCC Compiler The GCC Compiler compiles the Linux kernel and modules. The GCC Compiler version should match the version that was used to build the running kernel. Libaio Development Package The Libaio Development Package is an asynchronous I/O development package for applications that use libaio.so.
Installing Linux Drivers Installing Linux Drivers Before installing the Linux driver, ensure that the host computer has the kerneldevel RPM installed and GCC installed for the running kernel, which will allow the driver source to compile. These packages may not be installed by default on the Linux host. The information shown in the following examples may vary from your installation depending on the host computer kernel and distribution.
Chapter 7 - Linux Drivers The script begins installing the driver, as shown in following example: # ./vtms-linux-driver-.run Copying to a temporary location... Creating directory vtms-linux-driver- Verifying archive integrity... All good. Uncompressing Violin Memory, Inc. V1010 Linux Driver source........................ Current settings detected: ------------------------------------------------Kernel = 2.6.18-194.8.1.el5 Kernel Dir = /lib/modules/2.6.18-194.8.1.el5/build Kernel GCC = 4.
Installing Linux Drivers Installing Linux Drivers on Non-Running Linux Kernels To install the Linux driver on a non-running kernel: 1. Power up the Memory Array and verify the PCIe connectivity between the Memory Array and the host computer before installing and loading the Linux driver onto the host computer. Because the PCIe Hot Plug is not supported by most current BIOS versions, you must power up the Memory Array before powering up the host computer. 2. Log into the host computer as root.
Chapter 7 - Linux Drivers 8. When prompted to build the Linux driver type y. At the Build dir prompt, type the path to the non-running build directory: Build the driver now? [y]: Detected kernel build dirs: ------------------------------------------------/lib/modules/2.6.18-194.8.1.el5/build Build dir [/lib/modules/2.6.18-194.8.1.el5/build]: 9. When prompted, follow the instructions to install the Linux driver into the / lib/modules directory.
Loading and Unloading Linux Drivers Where N specifies the next available integer or blank if it is the first alias entry for a SCSI host adapter. Removing the Linux Drivers 1. Log into the Linux host as root. 2. Open a terminal window and at the system prompt, type: cd /tmp/vtms-linux-driver- make uninstall The Linux driver is removed from the /lib/modules directory, but can still be loaded and unloaded using the steps described in Loading and Unloading Linux Drivers on page 125.
Chapter 7 - Linux Drivers 3. At the system prompt, navigate to the following directory: cd /tmp/vtms-linux-driver-// Where: 4. Indicates the release number, such as D4.5.4.1. Indicates the kernel version, such as 2.6.942.ELsmp. Indicates the architecture type of the host computer, such as x86_64. Load the Linux driver; at the system prompt, type: ./load_strad.sh 5.
Installing the Violin Utilities 5. To load the Linux driver, at the system prompt, type: modprobe vtms [] Where indicates device type of the loaded driver. Valid values are: none Load as a block device [use_cdev=1] Load as a character device [use_scsi=1] Load as a SCSI device After loading the Linux driver, create partitions and file systems on the Memory Array or directly access the character device. Unloading the Linux Driver 1. Log into the host computer as root. 2.
Chapter 7 - Linux Drivers Table 7.1 Memory Array Commands for Viewing Linux Driver Information Utility Description veeprom Displays information, such as the main board serial number and the management MAC address. vinfo Displays driver version and registry tunable parameters. vpartial Displays Memory Array partial flash page counters. vstat Displays Memory Array status information. vzero Resets Memory Array I/O counters to zero.
Configuring Partitions and Storage Devices Configuring Partitions and Storage Devices In most deployments, the fifth step towards configuring a direct-attached Memory Array system with a Linux host is to configure block device partitions. Create block device partitions on the Memory Array for creating multiple file system partitions. Use the /dev/vtmsa device for creating file systems only if a single large partition is required.
Chapter 7 - Linux Drivers 3. At the Command prompt, type n to create a new partition: n Where n specifies to create a new partition. The command displays information similar to the following: Command (m for help): n Command action e extended p primary partition (1-4) 4. Next, at the Command prompt, create the new partition by typing: p Where p creates a primary partition.
Configuring Partitions and Storage Devices The command displays information similar to the following: Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. # The system command prompt is returned. Finish by creating the file system that uses the new block device partition, creating the new mount path, and mounting the new block device file system. 6.
Chapter 7 - Linux Drivers The command displays information similar to the following: # mkfs -t ext3 /dev/vtmsa1 mke2fs 1.39 (date) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 176160768 inodes, 352321536 blocks 17616076 blocks (5.
Configuring Partitions and Storage Devices 9. To unmount the file system, at the command prompt, type: umount /mnt/strad Enabling Host to Automatically Mount Partitions By editing the /etc/fstab file, you can enable the host computer to automatically mount Memory Array partitions on boot up. 1. Log into the host computer as root and change directories into /etc. 2. Edit the /etc/fstab file with the desired text editing tool. 3.
Chapter 7 - Linux Drivers 134 Specifies whether the device is backed up by the dump utility or not. If 0 is specified, the device will not be backed up. 1 specifies that the device will be backed up. Specifies what order the devices are checked. If 0 is specified, the device won’t be checked by fsck.
CHAPTER 8 Windows Drivers This chapter describes the installation of the Memory Array Storport driver and Violin Utilities on a Windows host computer.
Chapter 8 - Windows Drivers Windows Driver Overview In a direct-attached configuration, the Windows driver enables the host (a Windows machine) to access block storage on a Memory Array. The Windows Storport driver must be installed on the host machine if the Memory Array is to be directly attached to a Windows host. If the Memory Array is to be directly attached to a Linux host, see Linux Drivers on page 117.
Installing Windows Drivers DiskPart successfully changed the SAN policy for the current operation system. DISKPART> exit Installing Windows Drivers The Windows Storport driver enables a direct-attached PCIe connection between a Memory Array and a Windows host machine.
Chapter 8 - Windows Drivers The Welcome to the Violin Array Storport Setup Wizard window appears. 5. Click the Next button. The License Agreement window appears. 6. Select the I Accept the Agreement option and click the Next button. The Select Destination Location window appears.
Installing Windows Drivers 7. To change the destination folder, click the Browse button and navigate to the desired location otherwise do nothing to accept the default directory. Click the Next button. The Select Start Menu Folder window appears. 8. To change the destination folder, click the Browse button and navigate to the desired location. Click the Next button. The Ready to Install window appears. 9. HP-AM456-9002A Rev 01 Click the Install button.
Chapter 8 - Windows Drivers The Completing the Violin Array Storport Setup Wizard window appears. 10.To view the readme file, select the View README.TXT check box. 11.Click the Finish button. The Welcome to the Device Driver Installation Wizard window appears. 12.Click the Next button. The Completing the Device Driver Installation Wizard window appears.
Installing Windows Drivers 13.Click the Finish button. 14.Reboot 15.Log the host. into the host as administrator. The Found New Hardware window appears, The window verifies that the Memory Array is properly connected to the host and is ready to be configured. 16.Select the No, Not This Time option and proceed with the installation of the Windows device driver. For step-by-step instructions, see Installing the Violin Utilities on page 144.
Chapter 8 - Windows Drivers The Update Driver Software: Unknown Device window appears. 6. Select the Browse My Computer for Driver Software option. The Browse for Driver Software On Your Computer window appears. 142 7. Click the Browse button and navigate to the directory where you saved the zipped file (driver-storport-Dx.x.x.zip). 8. Ensure that the Include Subfolders option is selected and click the OK button.
Installing Windows Drivers The Windows system installs the drivers. A confirmation dialog box confirms that the driver was correctly installed. 9. Reboot the host. 10.Log into the host as administrator. The Found New Hardware window appears, The window verifies that the Memory Array is properly connected to the host and is ready to be configured. 11.Select the No, Not This Time option and proceed with the installation of the Windows device driver.
Chapter 8 - Windows Drivers 3. Select Add or Remove Programs. The Uninstall or Change a Program manager appears. 4. Double-click the Violin Memory Array Storport program in the list. The Violin Array Storport Uninstall dialog box appears. 5. To delete the driver, click the Yes button. The Violin Array Storport Uninstall dialog box appears. You must restart the Windows host to complete the uninstall. To restart the host, click the Yes button.
Installing the Violin Utilities Table 8.1 Command Line Utilities for Displaying Windows Driver Information Utility Description vzero Reset Memory Array I/O counters to zero. vincident The vincident script collects useful information from the host servers and Memory Array such as the version/ timestamp of the current kernel, CPU information, partition information, Memory Array configuration, and Memory Array logs.
Chapter 8 - Windows Drivers The License Agreement window appears. 6. Select the I Accept the Agreement option and click the Next button. The Select Destination Location window appears. 7. To change the destination folder, click the Browse button and navigate to the desired location otherwise do nothing to accept the default directory. Click the Next button. The Select Start Menu Folder window appears.
Installing the Violin Utilities 8. To change the destination folder, click the Browse button and navigate to the desired location. Click the Next button. The Ready to Install window appears. 9. Click the Install button. The Completing the Violin Array Storport Setup Wizard window appears. 10.Click the Finish button. 11.Reboot the host. A desktop icon is created to the Violin Utilities cmd shell.
Chapter 8 - Windows Drivers Expand the Disk Drives node to view the Memory Array SCSI Disk Device. Removing the Violin Utilities 1. Log into the host as administrator. 2. Open the Control Panel and click Add or Remove Programs. The Uninstall or Change a Program manager appears. 3. Double-click the Violin Array Utilities program in the list. The Violin Array Utilities Uninstall confirmation dialog box appears. 4. To delete the Violin Utilities, click the Yes button.
CHAPTER 9 Violin Utilities This chapter describes the Violin Utilities used for configuring and performance testing the Memory Array system. These commands are common to the Linux and Windows drivers and to the Memory Gateway.
Chapter 9 - Violin Utilities Understanding the Violin Utilities The Violin Utilities are tools designed to enable you to monitor the performance of Memory Array systems in a direct-attached configuration. Using the Violin Utilities, you may retrieve detailed information about the Memory Array and data transfer counts that enable you to configure the system for optimal performance.
Violin Utilities Reference • vcounts on page 151 • veeprom on page 153 • vhelp on page 155 • vincident on page 155 • vinfo on page 156 • vpartial on page 158 • vring on page 159 • vstat on page 160 • vupdate_tz on page 162 • vzero on page 163 • perf_test on page 163 vcounts The vcounts utility displays data transfer counters for the Memory Array.
Chapter 9 - Violin Utilities Unaligned host buf reads: Unaligned host buf writes: Requested DMA reads: Requested DMA writes: Flash partial page reads: Flash partial page writes: 0 0 0 0 0 0 Returns The vcounts utility returns the following counters: 152 IRQ calls The total interrupt request handler calls to the Memory Array device driver. IRQ calls for V1010 The total calls to the Memory Array device driver where work was done.
Violin Utilities Reference Unaligned host buf reads The total I/O read requests from a Memory Array, but only incremented when an unaligned host address required special buffer byte copying to service the DMA request. Unaligned host buf writes The total I/O write requests to a Memory Array, but only incremented when an unaligned host address required special buffer byte copying to service the DMA request. Requested DMA reads Incremented for each read DMA descriptor added to the descriptor ring.
Chapter 9 - Violin Utilities Windows Example The veeprom utility returns information similar to the following example when run on a Windows host: C:\violin\utils> veeprom Violin Memory, Inc. Version: vtms-win-utils, Device: Index: \\.\scsi5: 0 -- EEPROM Part # Serial # Board Ver Mfg. Date Mgmt. MAC info -: 1000074S-C-08 : 6C057CWX00134 : 0 : 20071226 : 00:1b:97:00:00:86 The Windows example returns the following information. Part # Displays the part number of the main board.
Violin Utilities Reference The Linux example returns the following information. ee_version Displays the EEPROM data format version. ee_partnum Displays the part number of the main board. ee_serialnum Displays the serial number of the main board. ee_boardver Displays the version of the main board. ee_mfgdate Indicates the manufacturing date of the main board. ee_mgmtmac Displays the MAC address of the management interface.
Chapter 9 - Violin Utilities You must log in as root on the Linux host computer to run the vincident reporting script. In the event that the full path name of the vincident utility is not in the root PATH, the full path of vincident is /opt/violin/bin/ vincident. Example # vincident 10.1.10.123 Gathering information from host... Gathering information from target... Incident report created in vincident.20110624T110149 vinfo The vinfo utility displays the Memory Array type and version.
Violin Utilities Reference Returns The vinfo utility returns the following information. HP-AM456-9002A Rev 01 Host Driver Displays the host system vtms device driver version. Driver Date Displays block mode only. When set to 1, allows READA read-ahead I/Os to be accepted. Target S/W Displays the software / firmware version running on Memory Array. Memory Displays the size in bytes of usable system capacity. For flash VIMMs, this value changes based on formatted capacity.
Chapter 9 - Violin Utilities vpartial The vpartial utility displays the number of read/write I/O requests processed and the number of partial 4kB flash pages. Syntax vpartial [ ] Example The vpartial utility returns information similar to the following example when run on a Linux host: # vpartial Violin Memory, Inc. Version: vtms-linux-utils-D4.5.
Violin Utilities Reference Completed write I/O's Displays the total I/O write requests to a Memory Array. This is not the individual DMA descriptors completed, but for each of the user requested I/Os. Unaligned host buf writes Displays the total I/O write requests to a Memory Array, but only incremented when an unaligned host address required special buffer byte copying to service the DMA request.
Chapter 9 - Violin Utilities Parameters Table 9.1 vring Utility Parameters Parameter Description -p Specifies that a partition is to be selected. Specifies the name of the partition. Example The vring utility returns information similar to the following example when run on a Linux host: # vring Violin Memory, Inc. Version: vtms-linux-utils-D4.5.4, 05/23/2011 INDX 0 1 2 3 4 ...
Violin Utilities Reference Example The vstat utility returns information similar to the following example when run on a Linux host: # vstat Violin Memory, Inc. Version: vtms-linux-utils-D4.5.
Chapter 9 - Violin Utilities ready Indicates whether the data plane is online and ready or offline. formatting Indicates if formatting of the VIMMs is in progress or not. This is only applicable to flash VIMM systems. format_done Indicates the progress percentage done during formatting of the VIMMs. paused Indicates the pause interval for I/Os. link Indicates whether the PCIe connection is online or offline. lid_ajar Indicates whether the lid is closed or not.
Violin Utilities Reference Example The vupdate_tz utility returns information similar to the following example when run on a Linux host: # vupdate_tz Violin Memory, Inc. Version: vtms-linux-utils-D4.5.4, 05/23/2011 tz_secs=28800 tz_altsecs=25200 tz_minwest=420 tm_isdst=1 The output shows that this Memory Array is 300 minutes (5 hours) from GMT. vzero The vzero utility resets the I/O counters to zero.
Chapter 9 - Violin Utilities Syntax perf_test For a discussion of using the perf_test utility in Memory Array performance tuning, see Performance Testing Using perf_test on page 174. Options The perf_test utility has the following options: Table 9.2 perf_test Utility Options Option 164 Description -h | -? Displays help. -b block-size Sets the size of each block, in bytes, such as 128, 512, 1024, and so on. Recognized unit/size qualifiers include: k and K for the appropriate binary multipliers.
Violin Utilities Reference Table 9.2 perf_test Utility Options (Continued) Option Description -A async-io-depth Specifies the number of I/Os to generate using the operating system’s asynchronous I/O API. On Linux, this option is only available if the libaio and libaio-devel packages were installed with the Violin Utilities installation. Specify less threads using the -t option for Windows and Linux drivers and specify more asynchronous I/Os using the -A option, as it reduces CPU context switching.
Chapter 9 - Violin Utilities The perf_test utility returns information similar to the following example when run on a Linux host: # perf_test -s 640 -R -A64 -t8 -o Violin Memory, Inc. Version: vtms-linux-utils-D4.5.
CHAPTER 10 Performance Tuning and Troubleshooting This chapter provides an overview of Memory Array performance tuning and testing, describes flash-layer performance tuning, and network-layer performance testing techniques using the perf_test utility.
Chapter 10 - Performance Tuning and Troubleshooting Performance Tuning and Testing Overview One of the primary reasons for choosing a Memory Array for block storage is that a flash-based memory array enables you to extract maximum performance from your applications. But optimal performance is achievable only if the entire Memory Array system is properly tuned. In many cases, the default settings provide for significant application acceleration.
Flash-Layer Performance Tuning While these tests are running, use operating system tools to confirm that actual I/O activity is similar to the levels tested using the perf_test utility. If the I/O is not similar to the baselines, then the operating system, file system, or database may need to be tuned. Please contact HP Customer Support for assistance if needed.
Chapter 10 - Performance Tuning and Troubleshooting system, do so for traditional RAIDs and solid-state drives; that is, 63 sectors per track. Two Utilities included in the Violin Utilities package, the vpartial utility and the vring utility, enable you to identify these issues. This section describes how the Violin Utilities may be used to diagnose 4kB alignment issues and provides instructions for correcting these problems on Linux and Windows hosts.
Flash-Layer Performance Tuning between 512 and 3584 for transfer size, since two Read-Modify-Write operations occur for each 4kB of data. # vring Violin Memory, Inc. Version: vtms-linux-utils-D4.5.4, 05/23/2011 INDX 0 1 2 3 4 ...
Chapter 10 - Performance Tuning and Troubleshooting 1. If the disk you are aligning is already blank (raw), go to Step 3. If the disk contains data, back up the disk before proceeding. 2. Delete all partitions on the disk. 3. From the Windows 2003 Server, open a command prompt and run Diskpart.exe. 4. At the diskpart command prompt, type List Disk and press ENTER. If the disk you want to align does not appear in the list, make sure that it exists and is accessible using the Disk Management snap-in.
Network-Layer Performance Testing • Performance Testing Using perf_test on page 174 Preliminary Network-Layer Checks The Memory Array is designed for high-bandwidth connections via either single PCIe x8 G1 or dual PCIe x4 G1.
Chapter 10 - Performance Tuning and Troubleshooting Performance Testing Using perf_test The perf_test utility is a lightweight tool for measuring the I/O performance of storage devices. The perf_test utility was specifically designed to push the I/O device as hard as possible using a variety of methods including POSIX threads, variable block sizing, asynchronous I/O, direct communication, as well as sequential and random read/ write operations to data over a user-defined address range.
Network-Layer Performance Testing 2 817.132 MB/s0.000 MB/s817.132 MB/s1994950199495 3 817.160 MB/s0.000 MB/s817.160 MB/s1995010199501 4 817.096 MB/s0.000 MB/s817.096 MB/s1994860199486 The following table describes the options used in this command. For a complete list of perf_test utility options, is perf_test on page 163. -s memory-size Specifies the system memory size, in GB (if no units are provided).
Chapter 10 - Performance Tuning and Troubleshooting Block Size Consider the block size when testing for maximal bandwidth versus maximal IOPS. Use a larger block size (megabytes, if necessary) when evaluating bandwidth performance and smaller block sizes, such as 4kB, when evaluating a device’s maximum IOPS potential. Latency Use perf_test to measure round-trip latency of an I/O request. Generally, latency measurements should only be made using one thread and an asynchronous I/O depth of one.
Network-Layer Performance Testing • Random reads at 4kB block size:(-R) (-b 4096) • Sustained random writes at 4kB block size: (-R) (-w1)(-r0) (-b 4096) • Random reads and writes at mix & the expected block size (given the application and file system): (-R) (-w1)(-r1) (-b) Each of these tests should be run using asynchronous I/O settings (-A) and a range (-t) of thread counts (for example, 1- 64).
Chapter 10 - Performance Tuning and Troubleshooting In the following example, a performance test is run to check write bandwidth using the -w1 -r0 options to place the write to read ratio at 1:0. # perf_test -s 384 -R Running with options: threads block_size memory size memory start addr write:read ratio random mode duration path MB Time (sec) Read BW 1 0.000 MB/s 2 0.000 MB/s 3 0.000 MB/s 4 0.000 MB/s 5 0.000 MB/s Average 0.
APPENDIX A Product Models This appendix describes the differences between the various Memory Array models. Table A.
Appendix A - Product Models 180 VMA-series Memory Array Installation and Service Guide HP-AM456-9002A Rev 01
APPENDIX B Compliance Information This appendix contains the following compliance information for the Memory Array.
Appendix B - Compliance Information Regulatory Information For your protection, this product has been tested for conformance to various national and international regulations and standards. The scope of this regulatory testing includes electrical and mechanical safety, electromagnetic emissions, immunity, acoustics, and hazardous materials. Regulatory Model Number For the purpose of regulatory compliance certifications and identification, this product is assigned a Violin Memory regulatory model number.
Lithium Battery Caution 80004) is available (or supplied with memory additions). This kit contains one wrist strap, one conductive sheet, and one antistatic foam pad. • Always disconnect power from the server and wear a grounded wrist strap when working around the server. • Always wear a grounded wrist strap when handling printed circuit boards. • Treat all assemblies, components and interface connections as staticsensitive.
Appendix B - Compliance Information Disposal of Waste Equipment by Users in Private Households in the European Union This symbol on the product or on its packaging indicates that this product must not be disposed of with your other household waste. Instead, it is your responsibility to dispose of your waste equipment by handing it over to a designated collection point for the recycling of waste electrical and electronic equipment.
Japan Radio Frequency Interference VCCI Japan Radio Frequency Interference VCCI Korea RFI Statement Canada RFI Statement This Class A digital apparatus complies with Canadian ICES-003. Australia C-Tick Label Figure B.
Appendix B - Compliance Information 186 VMA-series Memory Array Installation and Service Guide HP-AM456-9002A Rev 01
APPENDIX C Alarm Reference This chapter describes how to diagnose Memory Array system alarms. The chapter describes service affecting and non-service affecting alarms which may occur during operation of the Memory Array and provides information on resolving those alarms in the following sections.
Appendix C - Alarm Reference Understanding Memory Array Alarms The Memory Array provides you with key tools for identifying and interpreting raised alarms. • Alarms are indicated by the state of the Alarm LED on the front of the Memory Array chassis. • Information about an active alarm may then be viewed by running the show system alarm command or show system message command. This appendix provides information about how to clear these alarms when they occur.
Understanding Memory Array Alarms during bootup because the data plane is not enabled until later in the process. Such alarms may be safely ignored. Understanding System Alarm and System Message Commands When hardware malfunctions or another error occurs on the Memory Array system, you are notified in the following ways: the Alarm LED on the front of the Memory Array chassis is lit (solidly or flashing) and a alarm is raised by the system.
Appendix C - Alarm Reference show system messages Command The show system messages command displays the current contents of the / var/log/messages file. The message log file created on the Memory Array contains system log and typical boot up messages in addition to any set CLI commands that are run on the system. The command may be run by entering show system messages at the root context level or, alternately, by entering show messages at the System context prompt.
Service-Affecting Alarms • Equipment Service-Affecting Alarms on page 191 • Flash Service-Affecting Alarms on page 191 • Port Service-Affecting Alarms on page 192 • Power Service-Affecting Alarms on page 192 • RAID Service-Affecting Alarms on page 193 • System Service-Affecting Alarms on page 194 • Temperature Service-Affecting Alarms on page 195 • VIMM Service-Affecting Alarms on page 196 Equipment Service-Affecting Alarms There are two service affecting equipment alarms.
Appendix C - Alarm Reference To clear the alarm, replace the non-functioning VIMM. Contact HP Customer Support for replacement parts. Once a VIMM is replaced, the VIMM configuration should once again be valid. Unformatted System Alarm The Unformatted System alarm indicates that all the VIMMs in the system are unformatted. This alarm applies only to flash-based systems. The system is unusable until the system (VIMMs) are formatted. Port Service-Affecting Alarms There are two service affecting port alarms.
Service-Affecting Alarms AC Power Failure, Shutting Down Alarm The AC Power Failure, Shutting Down alarm indicates a failure in the power feeds to the power supplies. Main Power Failure, System Shut Down Alarm The Main Power Failure, System Shut Down alarm indicates a failure detected in the main power supplies. RAID Service-Affecting Alarms There are five service affecting RAID alarms.
Appendix C - Alarm Reference RAID Group Faulted Alarm The RAID Group Faulted alarm indicates that two or more VIMMs in the specified RAID group have failed and no spares are available to rebuild the RAID group. To clear the alarm, replace the failed VIMMs and insert spares. RAID V2P Error Alarm The RAID V2P Error alarm indicates that the RAID group has experienced an error with a VIMM at the specified ID number. The Alarm LED flashes. This is a nonrecoverable error.
Service-Affecting Alarms This is a nonrecoverable error. Contact HP Customer Support for assistance. Scheduler Paused Alarm The Scheduler Paused alarm indicates that the hardware scheduler temporarily paused during bootup or when a VIMM is being taken out of service. To clear the alarm, wait for the system to successfully complete the bootup process.
Appendix C - Alarm Reference VIMM Service-Affecting Alarms There are four service affecting VIMM alarms. • Insufficient VIMMs Alarm on page 196 • Main Controller Does Not Support VIMMs Alarm on page 196 • Multiple VIMMs Failed; System Shut Down Alarm on page 196 • VIMM Flash Format In Progress Alarm on page 196 Insufficient VIMMs Alarm The Insufficient VIMMs alarm indicates that an insufficient number of VIMMs have been detected to construct a usable system.
Non-Service Affecting Alarms Unless noted otherwise, non-service affecting alarms are indicated whenever the Alarm LED displays a steady light. When the alarm clears and the system returns to a normal operational state, the Alarm LED displays no light. This sections describes the non-service affecting alarms that may be raised on the system and provides instructions for resolving those alarms.
Appendix C - Alarm Reference To clear the alarm, check fan operation, the fan filter, and the ambient temperature of the system. Equipment Non-Service Affecting Alarms There are seven non-service affecting equipment alarms.
Non-Service Affecting Alarms Fan Running Too Slowly Alarm The Fan Running Too Slowly alarm indicates that the fan specified is present but is spinning slowly. The speed of the fan is given in rpm. Fan Tray Removed Alarm The Fan Tray Removed alarm indicates that the specified fan tray has been removed after the system has booted. The alarm specifies whether the top (1) or bottom (2) fan tray has been removed. To clear the alarm, replace the fan tray in the system.
Appendix C - Alarm Reference Flash Sequence Number Mismatch Alarm The Flash Sequence Number Mismatch alarm indicates that the VIMM sequence numbers in a particular RAID group do not match when data is written to those VIMMs. To clear the alarm, update the sequence number on all the VIMMs in the group. The data on those VIMMs may be corrupt. Preparing Flash on VIMM Alarm The Preparing Flash on VIMM alarm indicates that flash is being prepared on the specified VIMM for use by the system.
Non-Service Affecting Alarms Port Is Not Running at the Maximum Data Rate Possible Alarm The Port Is Not Running at the Maximum Data Rate Possible alarm occurs when the negotiated rate of the connection on the specified port is lower than the maximum possible data rate. This error can occur, for example, when the PCIe card used in the host is not compatible with the host computer chipset or if the PCIe extender card in the host is not inserted into a PCIe that supports the maximum data rate (e.g.
Appendix C - Alarm Reference RAID Non-Service Affecting Alarms There are four non-service affecting RAID alarms.
Non-Service Affecting Alarms • Excessive ECC Errors on VIMM Alarm on page 203 • Failed to Validate Configuration of VIMMS, Raid Group Alarm on page 204 • No Spare Memory Modules Alarm on page 204 • Programming VIMM Alarm on page 204 • Unsupported VIMM Configuration Alarm on page 204 • VIMM Booting Alarm on page 204 • VIMM Configuration Out Of Spec Alarm on page 204 • VIMM Failed Alarms on page 205 • VIMM Extremely Hot; VIMM Shutdown Alarm on page 205 • VIMM Failed Alarm on page 206 • V
Appendix C - Alarm Reference Failed to Validate Configuration of VIMMS, Raid Group Alarm The Failed to Validate Configuration of VIMMS, Raid Group alarm indicates that the system failed to validate the current VIMM configuration. The alarm lists the ID of the invalid VIMMs and the RAID group in which the error has occurred. To clear the alarm, remove and replace the failed VIMMs.
Non-Service Affecting Alarms The show system status command and the alarm message lists the number of system VIMMs that are missing, failed, in maintenance, or in an admin down state. To clear the alarm, list the failed VIMMs using the show system status command, and shut down the system to replace the missing VIMMs. VIMM Failed Alarms A VIMM Failed alarm indicates that the VIMM failed for one of the following reasons, and that it has been taken out-of-service.
Appendix C - Alarm Reference 1. Check for any airflow restrictions, including the filter in the front panel. 2. If there are no airflow issues and the environment is within specifications, replace the VIMM. VIMM Failed Alarm The VIMM Failed alarm indicates that the specified VIMM has failed and is inoperable. To clear the alarm, replace the VIMM.
Non-Service Affecting Alarms VIMM Isolated Alarm The VIMM Isolated alarm indicates that the specified VIMM is isolated and not reachable by any other VIMM within the tree. This is caused by the failure of other VIMMs, preventing a path from the main controller to the VIMM. To clear the alarm, replace the failed VIMM(s).
Appendix C - Alarm Reference 208 VMA-series Memory Array Installation and Service Guide HP-AM456-9002A Rev 01
APPENDIX D CLI Reference This appendix lists and describes the available commands in the Command Line Interface (CLI) for the Memory Array. The CLI is comprised of several context levels, each of which contains various commands. The appendix is organized by context level and lists the available subcontext levels and commands in each level in the following sections.
Appendix D - CLI Reference 210 • In-memory Context Commands on page 281 • Category Context Commands on page 285 • Syslog Context Commands on page 287 • Status Context Commands on page 290 • Sw-upgrade Context Commands on page 294 • Uptime Context Commands on page 297 • Version Context Commands on page 298 VMA-series Memory Array Installation and Service Guide HP-AM456-9002A Rev 01
Context Navigation Context Navigation The CLI consists of a context hierarchy to access the various system components. Each system component and function has its own context level, which can be specified at a command prompt when entering a command. After entering the command to change to a specific context level, the prompt changes to indicate where you are within the CLI hierarchy. The following global commands let you navigate within the context levels of the CLI.
Appendix D - CLI Reference Navigate to the context level then enter the command When you navigate to the context level and then issue the command, you are moving to that command’s context level. The context command lets you navigate into a lower level of the CLI command hierarchy. Specify the various levels that are depicted in Figure D.1, Context Levels on page 214. For example, to display the speed of the left fan in the top fan tray (where 1 is top and 2 is bottom): 1.
General Commands General Commands The table below describes the general commands available at any context level of the CLI. Table D.1 General Commands Command Description cancel Cancels a scheduled reboot and CLI session. clear Initializes or erases the indicated system resource. context Moves to lower context level. exit Exits the CLI. format Formats flash capacity. help Displays this list of commands. history Retrieves the most recently typed user commands.
Appendix D - CLI Reference Where: cli Cancels the CLI. system Cancels a scheduled reboot. session Cancels the specified CLI session. reboot Cancels a system reboot. clear Clears the system log file. Syntax clear system log context Navigates into a lower level of the CLI command hierarchy. Specify the various levels that are depicted in the figure below.
General Commands Where: context_level Specifies the context level to navigate to. Valid values are: • chassis (See Chassis Context Commands on page 221.) • cli (See CLI Context Commands on page 245.) • raid (See RAID Context Commands on page 251.) • system (See System Context Commands on page 257.) The available commands and sublevels are different in each context level. exit Exits the CLI. Syntax exit format Configures the system for a specific percentage of usable flash capacity.
Appendix D - CLI Reference Where: value Specifies the percentage of usable flash capacity. Valid values are: • • • • • • 50 65 78 84 87 90 — Not recommended for high performance or high reliability systems. Default is 65%. Higher usable percentages provide more usable capacity where needed. Lower usable percentages increase system write performance, endurance, and reliability. For advice on selecting a good usable percentage, consult with HP Customer Support.
General Commands The command displays information similar to the following:. chassis board 0 slot 67> history 01 - context chassis 02 - help 03 - ? 04 - up 05 - context chassis 06 - context board 0 07 - context slot 4 08 - context vimm 09 - top 10 - context system version ping Sends an ICMP ECHO_REQUEST messages to another network host. Syntax ping { | } Where: hostname Specifies the hostname to send the ICMP ECHO_REQUEST messages to.
Appendix D - CLI Reference If you do not specify the time delay, you are prompted whether to reboot the system immediately. Answer y to reboot immediately or n to cancel the immediate reboot request. See Rebooting the Memory Array on page 98 for more information. reset Resets the Ethernet interface. During a reset, active Telnet and SSH sessions are terminated, which is useful if the session is hung. Syntax reset chassis controller ethernet 0 set Runs the specified command parameters.
General Commands Where: parameter Specifies the information to display. This parameter may include a context level, including: • • • • • • • vimm vimm-summary ethernet fan-speed alarms uptime version Example To show information for the chassis board 0 type: show chassis board 0 info The command displays information similar to the following:.
Appendix D - CLI Reference Syntax top Example If you are at the Chassis board 0 context level and you want to move to the root level of the CLI, at the chassis board 0> prompt, type: chassis board 0> top up Moves back up one context level of the CLI.
Chassis Context Commands Chassis Context Commands Figure D.2 Chassis Context Commands The table below describes the commands available at the Chassis context level of the CLI. Table D.2 Chassis Context Commands Command Description context board 0 Moves the user to the Board 0 context level. context controller Moves the user to the Controller context level. context fan-tray Moves the user to the specified fan tray context level. context board 0 Moves to the Board 0 context level.
Appendix D - CLI Reference Syntax context controller The system prompt changes to the following: chassis controller> context fan-tray Moves to the specified Fan-tray context level. See Fan-tray Context Commands on page 243. Syntax context fan-tray {1 | 2} Where: 1 Indicates the top fan tray context level.
Board 0 Context Commands Board 0 Context Commands Figure D.3 Chassis>Board 0 Context Commands The table below describes the commands available at the Board 0 context sublevel of the CLI. Table D.3 Board 0 Context Commands Command Description context slot Moves the user into the context level for the specified slot. See Slot Context Commands on page 227. set flash-scrubbing Sets whether the flash memory is scrubbed or not.
Appendix D - CLI Reference Where: Moves the user into the context level for the specified slot - . Valid values are in the range of 0-83, inclusive. See Slot Context Commands on page 227. The system prompt changes to the following: chassis board 0 slot n> Example To move into the context level for slot 56, at the Board 0 context prompt, type: context slot 56 The command displays information similar to the following:.
Board 0 Context Commands show flash-scrubbing Displays the status of flash memory scrubbing. Syntax show flash-scrubbing The command displays information similar to the following:. chassis board 0> show flash-scrubbing flash-scrubbing disabled show info Displays manufacturing and environmental information about the main board in the system.
Appendix D - CLI Reference Where: 226 enabled Enables the write buffer on the flash VIMMs. disabled Disables the write buffer on the flash VIMMs.
Slot Context Commands Slot Context Commands Figure D.4 Chassis>Board 0>Slot Context Commands The table below describes the commands available at the Slot context level of the CLI. Table D.4 Slot Context Commands context vimm Moves into the VIMM context level. See VIMM Context Commands on page 230. set led-test Initiates a functional test of the slot’s LED. show led-state Displays the state of the slot’s LED. context vimm Moves into the context level for the VIMM in the previously specified slot.
Appendix D - CLI Reference The command displays information similar to the following:. chassis board 0 slot 56> context vimm chassis board 0 slot 56 vimm> set led-test Starts a functional test of the LED associated with the slot specified in the context slot command. The LED stays lit for two seconds, blinks fast for two seconds, blinks slowly for two seconds, then returns to the previous state.
Slot Context Commands The command displays information similar to the following:.
Appendix D - CLI Reference VIMM Context Commands Figure D.5 Chassis>Board0>Slot >VIMM Context Commands The table below describes the commands available at the VIMM context level of the CLI. Specify the VIMM number when moving into the Slot context level. See context slot on page 223. Table D.5 VIMM Context Commands Command Description set admin-state Sets the administrative state of the VIMM. show Displays various VIMM information. set admin-state Sets the administrative state of the VIMM.
VIMM Context Commands WARNING! Before removing the VIMM, change the administrative state to down. If you fail to do so, the VIMM, the slot that it is in, or the main board may experience permanent electrical damage and cease to operate. If a VIMM is an active member of a RAID group and its administrative state is set to down, a RAID group rebuild begins. If the VIMM is in a RAID group that cannot survive with the VIMM being taken out of the group, then data loss will occur.
Appendix D - CLI Reference environment temperature sensor-1.2v sensor-1.8v sensor-2.5v sensor-3.
VIMM-summary Context Commands VIMM-summary Context Commands Figure D.6 Chassis>Board 0>VIMM-Summary Context Commands The table below describes the commands available at the VIMM-summary context level of the CLI. Specify the VIMM number when moving into the Board 0 context level. See context slot on page 223. Table D.6 VIMM-summary Context Commands Command show Description Displays various VIMM information.
Appendix D - CLI Reference Under normal conditions for a fully-populated system, the command displays the following information: chassis board 0> show vimm-summary num-vimms installed-vimm-ids 69,71,75,76,78-80 flash-vimm-ids 69,71,75,76,78-80 admin-down-vimm-ids installed-mem-raw usable-mem-raw parity-mem-raw spare-mem-raw unavailable-mem-raw formatted-percentage usable-mem-formatted 42 3-8,12-18,22-27,35,38-45,48,60,643-8,12-18,22-27,35,38-45,48,60,6439 2886.2GB 2199.0GB 549.8GB 68.7GB 68.7GB 78.
VIMM-summary Context Commands Table D.7 show vim-summary Command Output Descriptions Output HP-AM456-9002A Rev 01 Description oper-down-vimm-ids Indicates the IDs of the VIMMs that have been operationally taken out-of-service by the system. isolated-vimm-ids Indicates the IDs of the VIMMs that are isolated due to either improper placement in a partiallypopulated chassis or through multiple VIMM failures installed-mem-raw Indicates, in GB, the amount of raw memory installed.
Appendix D - CLI Reference Controller Context Commands Figure D.7 Chassis>Controller Context Commands The table below describes the commands available at the Controller context sublevel of the CLI. Table D.8 Controller Context Commands Command Description context ethernet 0 Moves the user to the Ethernet 0 context level. See Ethernet 0 Context Commands on page 238. set serial-speed Sets the speed of the serial port. show serial-speed Shows the speed of the serial port.
Controller Context Commands Syntax show serial-speed context ethernet 0 Moves into the Ethernet 0 context level.
Appendix D - CLI Reference Ethernet 0 Context Commands Figure D.8 Chassis>Controller>Ethernet Context Commands The table below describes the commands available at the Ethernet 0 context sublevel of the CLI. Table D.9 Controller Context Commands Command Description set dhcp Enables or disables using DHCP to automatically set the system’s IP address. set ip-address Manually sets the IP address of the system. clear ip-address Clears the provisioned ip/netmask/gateway to use when DHCP is disabled.
Ethernet 0 Context Commands Syntax set dhcp {enabled | disabled} Where: enabled Enables using DHCP to automatically set the system’s IP address. disabled Disables using DHCP to automatically set the system’s IP address. Use the save config command to save the changes across system reboots. set ip-address Manually sets the IP address of the system. Syntax set ip-address [:[:]] Where: ipaddr Specifies the system’s new IP address. netmask Optional.
Appendix D - CLI Reference Syntax set dns-config {manual | auto} Where: manual Sets the DNS to manual configuration. auto Sets the DNS to automatic configuration. Use the save config command to save the changes across system reboots. set dns-nameserver Provisions the IP address for the DNS server to use when the set dnsconfig command is set to manual. Syntax set dns-nameserver Where: ipaddr The DNS server’s IP address. Use the save config command to save the changes across system reboots.
Ethernet 0 Context Commands Where: value The local domain name. Use the save config command to save the changes across system reboots. clear dns-search Clears the provisioned domain name. Syntax clear dns-search Use the save config command to save the changes across system reboots. show Displays the IP, netmask, gateway, and MAC addresses of the Memory Array.
Appendix D - CLI Reference reset Resets the Ethernet port. Syntax reset Example To reset the Ethernet port, at the Controller context prompt, type: reset If the Ethernet port is reset while logged in vial Telnet or SSH, then the CLI session will be lost. Run this command only when running the CLI from the serial/console port.
Fan-tray Context Commands Fan-tray Context Commands Figure D.9 Chassis>Fan Tray Context Commands The table below describes the commands available at the Fan-tray context level of the CLI. Access the Fan-tray context level through the Chassis context level. See Chassis Context Commands on page 221. Table D.10 Fan-tray Context Commands Command context fan Description Moves into the Fan context level. See Fan Context Commands on page 244. context fan Moves into the context level for the specified fan.
Appendix D - CLI Reference Fan Context Commands Figure D.10 Chassis>Fan-Tray>Fan Context Commands The table below describes the commands available at the Fan context level of the CLI. Access the Fan context level through the Fan-tray context level. See Fan-tray Context Commands on page 243. Table D.11 Fan Context Commands Command show Description Displays the current fan speed and rpm. show Displays the current speed setting of the fan.
CLI Context Commands CLI Context Commands Figure D.11 CLI Context Level The table below describes the commands available at the CLI context level of the CLI. Table D.12 CLI Context Commands Command Description set columns Sets the number of columns in the display window. set edit-mode Sets the command line edit mode. set history-size Sets the size of the history buffer. set idle-timeout Sets the time, in minutes, before exiting due to user inactivity.
Appendix D - CLI Reference set edit-mode Sets the command line editing mode to vi or emacs. Syntax set edit-mode {vi | emacs} Where: vi Sets the command line editing mode to vi. emacs Sets the command line editing mode to emacs. set history-size Sets the history buffer to the specified size. Syntax set history-size Where: n The number of lines to set for the history buffer. Valid values are in the range of 10-1000.
CLI Context Commands Syntax set lines Where: The number of lines for the window size. Valid values are in the range of 10-100. n set pagination Enables or disables the pagination in the current CLI window. Enabling pagination is helpful when using the show log command because of the long output. Syntax set pagination {on | off} Where: on Enables the pagination setting of the display window. off Disables the pagination setting of the display window.
Appendix D - CLI Reference The command displays information similar to the following:. cli> show columns columns 80 show edit-mode Displays the current command line editing mode. Syntax show edit-mode The command displays information similar to the following: cli> show edit-mode edit-mode vi show history-size Displays the current size of the history buffer.
CLI Context Commands The command displays information similar to the following: cli> show idle-timeout idle-timeout 30 minutes show lines Shows the number of rows for the display window. Syntax show lines The command displays information similar to the following: cli> show lines lines 24 show pagination Displays the pagination setting for the display window, which can be on or off. Syntax show pagination The command displays information similar to the following:.
Appendix D - CLI Reference The command displays information similar to the following:. cli> show session Session ID ---------97 Terminal -------pts/0 Active Since ------------Jun 24 09:59 Source ---------10.10.0.113 Current cli session cancel session Cancels the oam_cli session.
RAID Context Commands RAID Context Commands Figure D.12 RAID Context Level The table below describes the commands available at the RAID context sublevel of the CLI. Table D.14 RAID Context Commands Command Description context group Moves the user into the context level for the specified RAID group. See RAID Group Context Commands on page 253. show spare-ids Displays the IDs of the spare VIMMs in a system. context group Moves into the context level for the specified RAID group.
Appendix D - CLI Reference The command displays information shown below:. raid> context group 5 raid group 5> show spare-ids Displays the IDs of the spare VIMMs in a Memory Array. These spares are used during RAID group rebuilding when a VIMM becomes unstable and is moved out of service.
RAID Group Context Commands RAID Group Context Commands Figure D.13 RAID>Group Context Level The table below describes the commands available at the RAID Group context sublevel of the CLI. Access the RAID Group context sublevel through the RAID context level. See RAID Context Commands on page 251. Table D.15 RAID Group Context Commands Command Description context maps Moves the user into the context level for the RAID group mapping. See Maps Context Commands on page 255.
Appendix D - CLI Reference The command displays the following information: raid> context group 5 maps raid group 5 maps> 254 VMA-series Memory Array Installation and Service Guide HP-AM456-9002A Rev 01
Maps Context Commands Maps Context Commands Figure D.14 RAID>Group>Maps Context Level The table below describes the commands available at the Maps context sublevel of the CLI. Access the Maps context sublevel through the RAID Group context level. See RAID Group Context Commands on page 253. Table D.16 Maps Context Commands Command show Description Displays information about the VIMMs in the specified RAID group. show Displays the VIMM mapping for the specified RAID group.
Appendix D - CLI Reference Where: group-number Indicates the RAID group ID. The valid range of values is 0-15, inclusively. id Indicates the physical VIMM ID. The valid range of values is 0-83, inclusively. state Indicates the state of each VIMM in the 5-VIMM RAID group. Valid values are: • data—VIMM is being used for data, either user data or parity data. • REBUILDING—VIMM is currently being rebuilt by the RAID engine to recover from a prior failure. • FAULT—A fault has occurred for this VIMM.
System Context Commands System Context Commands Figure D.15 System Context Level The table below describes the commands available at the System context level of the CLI. Table D.17 System Context Commands Command Description cancel reboot Cancels the scheduled reboot. clear log Clears the log buffer. context alarms Moves into the Alarms context level. See Alarms Context Commands on page 273. context all Moves into the all context level.
Appendix D - CLI Reference Table D.17 System Context Commands (Continued) Command Description save config Commits the admin login password and system log service changes to the flash or reverts back to the factory default settings. If the changes are not committed before the system is rebooted, then the changes are lost and the previous settings are used. set admin Changes the password for the admin login. set boot-params Sets the systems boot parameters.
System Context Commands Syntax clear log Example To clear the system log, at the System context prompt, type: clear log The command displays the following information:. system> clear log log clear context alarms Moves into the Alarms context level to access the alarm related commands. Syntax context alarms The system prompt changes to the following: system alarms> context all Moves into the all context level to reboot all system processors.
Appendix D - CLI Reference Syntax context boot-params The system prompt changes to the following: system boot-params> context led-state Moves into the LED State context level to access the LED state related commands. Syntax context led-state The system prompt changes to the following: system led-state> context logging Moves into the Logging context level to access the logging related commands.
System Context Commands context status Moves into the system Status context level to access the system status related commands. Syntax context status The system prompt changes to the following: system status> context sw-upgrade Moves into the software upgrade context level to access the software upgrade commands. Syntax context sw-upgrade The system prompt changes to the following: system sw-upgrade> context uptime Moves into the Uptime context level to access operational time related commands.
Appendix D - CLI Reference Syntax context version The system prompt changes to the following: system version> save log Saves the system log to a remote host using either TFTP or SCP. Syntax save log {@scp | tftp}:///system.log Where: user@scp Specifies to use SCP and the user name to log onto the host when using SCP. tftp Specifies to use TFTP. hostname Specifies the host name to copy the system log to.
System Context Commands Syntax set admin You will be prompted to enter a new password. If the new password meets the requirements you will be prompted to re-enter the same password. A message appears indicating that the password has been changed. The command displays information similar to the following if the new password does not meet the requirements.
Appendix D - CLI Reference set boot-params Sets the system boot parameters. Syntax set boot-params stagger-mem-clear Where Is either enable or disable. value set clock-source Sets the system clock source. The source can be set to the host computer or the Memory Array. The system clock only keeps a running count of the number of seconds that the system has been operational. It doesn’t keep an accurate calendar date and time.
System Context Commands The command displays information similar to the following:. system> save config Config operation succeeded. Validity check succeeded. restore config Restores the admin login password and system log service configuration changes back to the factory default settings. Requires a software reboot. Syntax restore config factory The command displays information similar to the following:. system> restore config factory Running this command requires a non service-affecting software reboot.
Appendix D - CLI Reference set name Sets the hostname of the system. When setting the system’s name, use only alphanumeric characters and the hyphen. Syntax set name Where: name Specifies the new name for the system. Use the save config command to save the changes across system reboots. show boot-params Displays the system boot parameters. Syntax show boot-params stagger-mem-clear The command displays information similar to the following:.
System Context Commands Where: clock Displays the date and time in the format yyyy-mmddThh:mm:ss. The T is a delineator between the date and the time. show clock-source Displays the current clock source of a Memory Array. The source can be the host of the system or local, which defines the clock source as the Memory Array. Syntax show clock-source The command displays information similar to the following:.
Appendix D - CLI Reference The command displays information similar to the following: system> show log xxx xx xx:xx:xx [000000000] INFO vtu_log_init(): ------------ LOG RESTART -----------xxx xx xx:xx:xx [000000010] INFO ecpu_hwmgr_init(): Running fans at full speed xxx xx xx:xx:xx [000000010] INFO main(): Main controller build ID: 12954 xxx xx xx:xx:xx [000000010] INFO main(): S/W Rel: Release Number, Built: Date 12:16:39 on swbuild.violintech.
System Context Commands The command displays information similar to the following:. system> show messages Date 00:28:22 kernel: Linux version Number (common@swbuild.violintech.net) (gcc version 3.4.6) #2 PREEMPT Mon Date 12:38:51 EST Date 00:28:22 kernel: ^O^M Date 00:28:22 kernel: Date 00:28:22 kernel: uClinux/Nios II Date 00:28:22 kernel: Altera Nios II support (C) 2004 Microtronix Datacom Ltd.
Appendix D - CLI Reference The command displays information similar to the following: system> show reboot There is a reboot scheduled in 14 minute(s) and 8 seconds. show status Displays the status of the various software modules and the validity of the current VIMM configuration.
System Context Commands The command displays information similar to the following when the system is operating correctly: system> show status alarm-mgr data-mgr diagnostics-mgr hardware-mgr inventory-mgr raid-mgr vimm-mon data-plane raid-rebuild vimm-config admin-down-vimm-ids missing-vimm-ids host-interfaces slot state protocol link-width neg-link-width max-data-rate cfg-data-rate host HP-AM456-9002A Rev 01 running running running running running running running available active (group 2, vimm 07, 47% c
Appendix D - CLI Reference The command displays information similar to the following when failed VIMMs are in the system: system> show status alarm-mgr data-mgr diagnostics-mgr hardware-mgr inventory-mgr raid-mgr vimm-mon data-plane raid-rebuild vimm-config failed-vimm-ids admin-down-vimm-ids missing-vimm-ids host-interfaces slot state protocol link-width neg-link-width max-data-rate cfg-data-rate host 272 running running running running running running running available active (group 2, vimm 07, 47% com
Alarms Context Commands Alarms Context Commands Figure D.16 System>Alarms Context Level The table below describes the commands available at the Alarms context sublevel of the CLI. Access the Alarms context sublevel through the System context level. See System Context Commands on page 257. Table D.18 Alarms Context Commands Command show Description Displays the current alarms on the system. show Displays the current alarms on a Memory Array.
Appendix D - CLI Reference The command displays information similar to the following: system alarms> show alarm1 alarm2 alarm3 alarm4 alarm5 alarm6 System booting (45% complete) Lid removed Top fan tray removed Bottom-left fan running too slowly, 2000 RPM VIMM 14 low 1.8V, 1.68 volts; VIMM shut down VIMM 68: hot, 71 C The command displays information similar to the following during a VIMM flash format.
Boot-params Context Level Boot-params Context Level Figure D.17 System>Boot-params Context Level The table below describes the commands available at the Boot-params context sublevel of the CLI. Table D.19 Boot-params Context Commands Command Description set stagger-memclear Enables or disables the staggered VIMM boot-up process. show stagger-memclear Displays the current state of the VIMM boot-up process. set stagger-mem-clear Enables or disables the staggered VIMM boot-up process.
Appendix D - CLI Reference show stagger-mem-clear Displays the current state of the VIMM boot-up process.
LED-state Context Commands LED-state Context Commands Figure D.18 System>LED-State Context Level The table below describes the commands available at the LED State context sublevel of the CLI. Access the LED State context sublevel through the System context level. See System Context Commands on page 257. Table D.20 LED State Context Commands Command show Description Displays the current status of the system LEDs. show Displays the current status of the system LEDs.
Appendix D - CLI Reference The command displays information similar to the following: system led-state> show power-a power-b status alarm 278 on on on off VMA-series Memory Array Installation and Service Guide HP-AM456-9002A Rev 01
Logging Context Commands Logging Context Commands Figure D.19 System>Logging Context Level The table below describes the commands available at the Logging context sublevel of the CLI. Access the Logging context sublevel through the System context level. See System Context Commands on page 257. Table D.21 Logging Context Commands Command Description context in-memory Moves into the In-memory context level. See Inmemory Context Commands on page 281. context syslog Moves into the Syslog context level.
Appendix D - CLI Reference context syslog Moves into the Syslog context level to access the syslogd related commands. Syntax context syslog Where: context syslog Moves into the Syslog context level.
In-memory Context Commands In-memory Context Commands Figure D.20 System>Logging>In-Memory Context Level The table below describes the commands available at the In-memory context sublevel of the CLI. Access the In-memory context sublevel through the Logging context level. See Logging Context Commands on page 279. Table D.22 In-memory Context Commands Command Description context category Moves into the Category context level. See Category Context Commands on page 285.
Appendix D - CLI Reference Table D.
In-memory Context Commands set default-level Sets the level of messages stored in the system log of the Memory Array. The message level can be set to: • DEBUG • INFO • WARN • ERROR • FATAL Setting the level to debug may fill up the log very quickly since this level logs every internal message created by the system. Syntax set default-level {default | fatal | error | warn | info | debug} Where: default The default value, which is currently info.
Appendix D - CLI Reference Syntax show default-level The command displays information similar to the following: system logging in-memory> show default-level default-level 284 info VMA-series Memory Array Installation and Service Guide HP-AM456-9002A Rev 01
Category Context Commands Category Context Commands Figure D.21 System>Logging>In-Memory>Category Context Level The table below describes the commands available at the Category context sublevel of the CLI. Access the Category context sublevel through the In-memory context level. See In-memory Context Commands on page 281. Table D.24 Category Context Commands Command Description set level Sets the message logging level of the specified message category.
Appendix D - CLI Reference Where: default Sets the category message level to the currently defined default level. fatal Sets the category message level to fatal. error Sets the category message level to error. warn Sets the category message level to warn. info Sets the category message level to info. This is the default value. debug Sets the category message level to debug. show level Displays the logging level of the specified message category stored in the system log of the Memory Array.
Syslog Context Commands Syslog Context Commands Figure D.22 System>Logging>Syslog Context Level The table below describes the commands available at the Syslog context sublevel of the CLI. Access the Syslog context sublevel through the Logging context level. See Logging Context Commands on page 279. Table D.25 Syslog Context Commands Command Description set host Sets the IP address for the syslogd host. set service Enables or disables the service that sends the system log.
Appendix D - CLI Reference Where: ip_address Specifies the IP address of the host to which the system log messages will be sent. Use the save config command to save the changes across system reboots. set service Enables or disables the service that sends the system log to a host running syslogd. See your host’s syslogd documentation for instructions. Display the man page for syslog.conf on your host for more information.
Syslog Context Commands show service Displays the status of the service that sends the system log to a host running syslogd.
Appendix D - CLI Reference Status Context Commands Figure D.23 System>Status Context Level The table below describes the commands available at the Status context sublevel of the CLI. Access the Status context sublevel through the System context level. See System Context Commands on page 257. Table D.26 Status Context Command Command show Description Displays the current status of the system software modules. show Displays the status of various software modules.
Status Context Commands host-interfaces slot state protocol link-width neg-link-width max-data-rate cfg-data-rate host port-1 enabled pcie 8 8 20 Gb/s 20 Gb/s detected slot state host port-2 disabled undetected slot state host port-0 disabled undetected The command displays information similar to the following when failed VIMMs are in the system: system status> show alarm-mgr data-mgr diagnostics-mgr hardware-mgr inventory-mgr raid-mgr data-plane raid-rebuild vimm-config failed-vimm-ids host-interfac
Appendix D - CLI Reference The command displays information similar to the following when one VIMM is missing and one VIMM has failed in the system: system status> show alarm-mgr data-mgr diagnostics-mgr hardware-mgr inventory-mgr raid-mgr data-plane raid-rebuild vimm-config failed-vimms missing-vimms host-interfaces slot state protocol link-width neg-link-width max-data-rate cfg-data-rate host 292 running running running running running running available inactive in-spec-84-vimm 32 61 port-1 enabled pci
Status Context Commands The command displays information similar to the following when a VIMM has been removed and the system is rebuilding the RAID group: system status> show alarm-mgr data-mgr diagnostics-mgr hardware-mgr inventory-mgr raid-mgr data-plane raid-rebuild vimm-config host-interfaces slot state protocol link-width neg-link-width max-data-rate cfg-data-rate host HP-AM456-9002A Rev 01 running running running running running running available active (group 15, vimm 30) in-spec-84-vimm port-1 e
Appendix D - CLI Reference Sw-upgrade Context Commands Figure D.24 System>Sw-upgrade Level The table below describes the commands available at the Sw-upgrade context level of the CLI. Access the sw-upgrade context level through the System context level. See System Context Commands on page 257. Table D.
Sw-upgrade Context Commands set active Sets the specified partition in flash to be activated during the next reboot of the Memory Array. Syntax set active {upgrade | factory} Where: upgrade Sets the upgrade partition in flash to be activated during the next system reboot. The upgrade partition contains the downloaded upgrade software. factory Sets the factory partition in flash to be activated upon the next system reboot. The factory partition contains the factory configuration defaults.
Appendix D - CLI Reference The command displays information similar to the following: system sw-upgrade> show active Checking partition information ... The active partition is set to 'factory' Where: upgrade Specifies that the upgrade partition in flash is set to be activated during the next system reboot. The upgrade partition contains the downloaded upgrade software. factory Specifies that the factory partition in flash is set to be activated upon the next system reboot.
Uptime Context Commands Uptime Context Commands Figure D.25 System>Uptime Level The table below describes the commands available at the Uptime context sublevel of the CLI. Access the Uptime context sublevel through the System context level. Table D.28 Uptime Context Command Command show Description Displays how long the Memory Array has been operational. show Displays how long the system has been operational. The time is displayed in tenths of a second and in years, days, and hours.
Appendix D - CLI Reference Version Context Commands Figure D.26 System>Version Level The table below describes the command available at the Version context sublevel of the CLI. Access the Version context sublevel through the System context level. Table D.29 Version Context Command Command show Description Displays the versions of the software modules. show Displays the versions of the software modules.
Version Context Commands controller version info: saxpow version info: saxled version info: HP-AM456-9002A Rev 01 12954_x8a @ 05/28/09 11:39 8418 @ 03/12/08 15:26 7642 @ 01/25/08 13:48 VMA-series Memory Array Installation and Service Guide 299
Appendix D - CLI Reference 300 VMA-series Memory Array Installation and Service Guide HP-AM456-9002A Rev 01
