iodrive product family - fujitsu technology...

User Guide

ioDrive Product Family User Guide - Linux

for Driver Release 2.3.1English

ioDrive Product Family

User Guide - Linux

for Driver Release 2.3.1

5.26.2011

ioDrive User Guide for Driver 2.3.1 - Linux - D0001657-006_1 | _________ ___ ___ 2

ioDrive User Guide for Driver Release 2.3.1 - Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Performance Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installing RPM Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installing DEB Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Building the ioMemory VSL from Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Loading the ioDrive ioMemory VSL Facility (Driver) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Setting the ioMemory VSL Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Upgrading the Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Using the ioDrive as Swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Using the Logical Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Configuring RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Understanding Discard (TRIM) Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

ioDrive LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

ioManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Command-line Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Common Maintenance Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Disabling Auto-Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Unmanaged Shutdown Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Disabling the ioMemory VSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Appendix A- Utilities Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

fio-attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

fio-beacon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

fio-bugreport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

fio-detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

fio-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

fio-pci-check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

fio-snmp-agentx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

fio-status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

fio-update-iodrive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Appendix B- Monitoring the Health of ioDrive Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

NAND Flash and Component Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45


Health Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Health Monitoring Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Software RAID and Health Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Appendix C- Using Module Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Appendix D- Setting Up SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

SNMP Master Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Fusion-io SNMP AgentX Subagent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Using the SNMP Sample Config Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Enabling SNMP Test Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

SNMP MIB Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Appendix E- SMI-S Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Installing the SMI-S WMI Provider on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Linux Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Appendix F- Documentation Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

AVR Bootloader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

tree.h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Fusion Powered Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75


ioDrive User Guide for Driver Release 2.3.1 - Linux

Copyright Notice

The information contained in this document is subject to change without notice.

Fusion-io MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING,BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE. Except to correct same after receipt of reasonable notice, Fusion-io shall not be liable forerrors contained herein or for incidental and/or consequential damages in connection with the furnishing,performance, or use of this material.

The information contained in this document is protected by copyright.

© 2011 Fusion-io, Inc. All rights reserved.

Fusion-io, the Fusion-io logo, and ioDrive are registered trademarks of Fusion-io, Inc. in the United States and othercountries.

The names of other organizations and products referenced herein are the trademarks or service marks (as applicable)of their respective owners. Unless otherwise stated herein, no association with any other organization or productreferenced herein is intended or should be inferred.

Fusion-io2855 E. Cottonwood Parkway, Box 100Salt Lake City, UT 84121USA

(801) 424-5500

Part Number D0001657-006_1


Introduction

Overview

Congratulations on your purchase of a Fusion-io solid-state storage device. This guide explains how to install,troubleshoot, and maintain your ioDrive, ioDrive Duo, or ioSAN.

Throughout this manual, when you see a reference to an ioDrive, you may substitute your device if you are using adifferent product from the ioDrive line (such as an ioDrive Duo).

Designed around a revolutionary silicon-based storage architecture, the ioDrive is the world's most advanced NANDflash storage device, with performance comparable to DRAM and storage capacity on par with today's harddisks--giving you the power to improve storage performance by orders of magnitude. The ioDrive allows everycomputer to exceed the I/O performance of an enterprise SAN.

The ioDrive is a data accelerator designed specifically to improve the bandwidth for I/O-bound applications. TheioDrive is a no-compromise solution for the toughest computational challenges faced by data centers today, putting itin a league of its own.

About the ioMemory Virtual Storage Layer (VSL)

In addition to the hardware driver, the ioDrive also includes the ioMemory Virtual Storage Layer (VSL). This is ahybrid of the RAM virtualization subsystem and the disk I/O subsystem, combining the best of both worlds. Itappears like a disk to interface well with block-based applications and software. At the same time, it runs like RAMunderneath to maximize performance. This provides the following game-changing benefits:

Performance: The VSL offers direct and parallel access to multiple CPU cores, enabling near-linearperformance scaling, consistent performance across different read/write workloads, and low latency withminimal interrupts and context switching

Extensibility: The VSL enables flash-optimized software development, making each ioMemory module aflexible building block for building a flash-optimized data center.

Flash: Not Just Another Disk Drive

Whether on a PCIe card or in a drive bay, other SSD providers besides Fusion-io simply treat flash as another diskdrive, putting it behind RAID controllers. This approach has the following limitations:

Reduced performance and reliability


Increased latency and complexity

Limited potential for software development and optimization around the flash storage medium

With the ioMemory VSL, the ioDrive avoids this limiting approach and provides a wealth of performance andoptimization possibilities.

Performance Attributes

ioDriveCapacity

160GB 320GB 640GB

NAND Type Single Level Cell (SLC) Multi Level Cell (MLC) Multi Level Cell

ReadBandwidth

770 MB/s (64K packet size) 735 MB/s (64K packet size) 750 MB/s (64K packet size)

WriteBandwidth

750 MB/s (64K packet size) 510 MB/s (64K packet size) 550 MB/s (64K packet size)

IOPS* 140,000 (512B read packet size) 123,000 (75/25 r/w mix 512Bpacket size)

100,000 (512B read packet size) 67,000 (75/25 r/w mix 512Bpacket size)


Access Latency 26 μs Read 29 μs Read 30 μs Read

ioDuoCapacity

320GB 640GB 1.28TB

NAND Type Single Level Cell (SLC) Multi Level Cell (MLC) Multi Level Cell

ReadBandwidth

1.5 GB/s (64K packet size) 1.5 GB/s (64K packet size) 1.5 GB/s (64K packet size)

WriteBandwidth

1.5 GB/s (64K packet size) 1.0 GB/s (64K packet size) 1.1 GB/s (64K packet size)

IOPS* 261,000 (512B read packet size) 238,000 (75/25 r/w mix 512Bpacket size)



AccessLatency

26 μs Read 29 μs Read 30 μs Read

*Performance achieved using multiprocessor enterprise server

Enterprise Data Integrity

Field upgradeability

Green footprint


System Requirements

Supported Operating Systems

All operating systems must be 64-bit x86 architecture to support the ioDrive. Running the latest Service Pack of arelease is strongly recommended.

UPGRADE WARNING: Version 2.1 and later of the driver software, including ioMemory VSL, are notbackward-compatible with any driver version earlier than 2.1. When you install version 2.1 or later, you cannotrevert to any driver version before 2.1.

Supported Linux Distributions

Red Hat Enterprise Linux 4, 5, 6

SUSE Linux Enterprise Server (SLES) 10, 11

openSUSE 11

Debian Lenny, Debian Squeeze

Fedora 12, 13, 14

Ubuntu 8.04, 9.10, 10.04, 10.10

CentOS 4, 5

Chaos 4.3

OEL 5

Hardware Requirements

For hardware installation instructions, please refer to the .ioDrive Hardware User Guide

ioDrive Requirements

The ioDrive requires at least:

A PCI-Express (PCIe) Gen1 x4 slot.The ioDrive is a half-height, half-length, PCIe 1.1 x4 card and for full performance, it must reside in a PCIe slotwhere at least 4 lanes are electrically active.


1.

2.

Adequate system cooling.To maximize the longevity and performance of an ioDrive, we recommend at least 300 Linear Feet per Minute(LFM) of airflow through the system at an ambient air temperature of no more than 55°C.

In order to protect against thermal damage, the ioDrive monitors the temperature of its onboard controller chip(This is reported by the command line utility as "Internal temperature"). fio-status

The ioDrive will start throttling write performance once the controller temperature reaches 78°C. If thecontroller temperature continues to rise, the ioDrive will shut down once the controller temperature reaches85°C. If the device is shut down due to insufficient cooling, reboot the system to re-enable the device.

If you experience write-performance throttling due to high temperatures, consult your server'sdocumentation for details on increasing airflow within your system (for example, by increasing theminimum fan speeds within the system via a BIOS setting).

High Performance/Power ModeIf your BIOS has a High Performance/Power Mode, enable it when using ioDrive devices. Also disableany power-saving modes. This improves performance in two ways:

Prevents operating systems and the BIOS from suspending PCIe devices (using ASPM), includingioDrive devices. ioDrive devices do not support ASPM.

Maintains higher fan speeds to prevent thermal throttling.

Sufficient system memory (RAM).The amount of RAM the VSL requires varies according to the average block size written to the device. Usingthe average block size table below, you can estimate the amount of system memory needed. You can reduceworst-case memory use by formatting your ioDrive with a 4K sector size and thereby force the average writtenblock size to be 4K or greater.

Since the average write I/O size for most workloads is 4k or larger, the 4k average write size is typically themost accurate representation of memory utilization.

At various block sizes, the following table shows the upper limit of RAM that may be required of your system forevery 80 GB of ioDrive storage space used.

Average Written Block Size (bytes) RAM Usage (MB) per 80GB of storage space

8192 225

4096 (Most common) 425

2048 825

1024 1600

512 3175

For example, if your system is equipped with a 640GB ioDrive Duo, formatted to use 4,096 byte sectors, your system


may require as much as:(425 MB of RAM / 80 GB) x (640 GB) = for use by the ioDrive3,400 MB (or around 3.32 GB) of system RAMDuo driver.

ioDrive Duo Requirements

In addition to the ioDrive cooling and RAM requirements given above, the ioDrive Duo requires at least:

A PCIe Gen1 x8 slot or a PCIe Gen2 x4 slot.

A minimum of a , half-length slot with a x8 physical connection. For systems with PCI 1.1, all 8full-heightsignaling lanes must be active for full ioDrive Duo performance. For systems with PCIe 2.0, only 4 signalinglanes must be active for full performance.

For maximum performance, it is strongly recommended that an auxiliary power source be connected to theioDrive Duo, via the ioDrive Duo's external power connector. For additional information, see the ioDrive

.Hardware User Guide

ioSAN Requirements

In addition to the ioDrive cooling and RAM requirements, the ioSAN requires at least:

A PCIe Gen1 x8 slot or a PCIe Gen2 x4 slot.

QSFP connectors for external network connections.

External power cables

A power source that provides 45 watts of power.

For the ioSAN to properly function, an auxiliary power source must be connected to the ioSAN, via the ioSANexternal power connector. For additional information, including adding network drivers, see the ioDrive Hardware

.User Guide

ioOctal Requirements

The ioDrive Octal hardware requirements differ from other ioMemory devices. See the ioDrive Octal Hardware User for those hardware requirements.Guide


1.

2.

3.

4.

Software Installation

Before installing the ioMemory VSL (driver), make sure you have properly installed the ioDrive device(s). Refer tothe for full details. ioDrive Hardware User Guide

The ioMemory VSL (driver) requires a 64-bit operating system. See in the introduction to thisSystem Requirementsguide for a full list of supported operating systems.

After you install this version of the ioMemory VSL, you may need to upgrade the firmware to enable operation.See later in this section for more informationUpgrading the Firmware

UPGRADE WARNING: Version 2.1 and later of the driver software, including ioMemory VSL, are notbackward-compatible with any driver version earlier than 2.1. When you install version 2.1 or later, you cannotrevert to any driver version before 2.1.

All commands require administrator privileges. Use sudo or log in as "root" to run the install.

Installation Overview

If needed, uninstall previous versions of the ioMemory VSL (driver) and the utilities. Instructions foruninstalling current and previous versions of the driver are available in the section.Common Maintenance TasksOnce you have uninstalled the packages, return to this page.

Install the latest version of the ioMemory VSL. You can install the ioMemory VSL asA pre-compiled binary package

A source-to-build package

Follow the instructions under or to determineInstalling RPM Packages Installing DEB Packageswhether pre-compiled binary packages are available for your kernel version or if you need to build

.the driver package from source

Install utilities and management software (included in driver installation instructions).

Load the ioMemory VSL and .Set the Options


5.

1.

2.

Upgrade the Firmware to the latest version, if needed (recommended).

Installing RPM Packages

To install the ioDrive Linux driver and utilities on SUSE, RHEL, Fedora, and CentOS:

You will need to install a version of the ioMemory VSL (driver) that is built for your kernel. To determine whatkernel version is running on your system, use the following command at a shell prompt:

$ uname -r

Compare your kernel version with the binary versions of the driver available at http://ts.fujitsu.com/support/. .If there is a binary version of the driver that corresponds to your kernel version, download that. For

:example

iomemory-vsl-<kernel-version>-<driver-version>.x86_64.rpm

If there is no binary version of the driver corresponding to your kernel, download the source package. :For example

iomemory-vsl-<driver-version>.src.rpm

Exact package names may vary, depending on driver and kernel version chosen.


3.

4.

5.

6.

Download the appropriate support .rpm packages from http://ts.fujitsu.com/support/downloads.html.These packages provide utilities, firmware, and other files.

Examples:fio-util-<driver-version>.x86_64.rpm

fio-firmware-<firmware-version>.noarch.rpm

fio-snmp-agentx-<version>.x86_64.rpm

iomanager-gui-<version>.noarch.rpm

iomanager-jre-<version>.x86_64.rpm

fio-smis-<version>.x86_64.rpm

fio-snmp-agentx-<version>.x86_64.rpm

fio-snmp-mib-<version>.x86_64.rpm

libfio-dev-<version>.x86_64.rpm

libfio-doc-<version>.x86_64.rpm

libfusionjni-<version>.x86_64.rpm

fio-common-<driver-version>.x86_64.rpm

fio-sysvinit-<driver-version>.x86_64.rpm

Build the driver from source: if you downloaded the driver source package, you must now follow theinstructions in . If you downloaded a binary version of the driver, continue.Building the ioMemory VSL from Source

Change to the directory to where you downloaded the installation packages.

Enter the following command to install the custom built driver package. Use the package name that you justcopied into that directory.

rpm -Uvh iomemory-vsl-<driver-version>.x86_64.rpm


7.

8.

1.

2.

Enter the following commands to install the support files:

rpm -Uvh lib*.rpmrpm -Uvh fio*.rpm

The drivers and utilities are installed to the following locations:

Package Type Installation Location

Drivers /lib/modules/<kernel-version>/extra/fio/iomemory-vsl.ko

Utilities /usr/bin

Firmware /usr/share/fio/firmware

SNMP MIB /usr/share/fio/mib

Continue to later in the section.Loading the ioDrive ioMemory VSL Facility (Driver)

Installing DEB Packages

To install the ioDrive Debian/Ubuntu driver and utilities:

You will need to install a version of the ioMemory VSL (driver) that is built for your kernel. To determine whatkernel version is running on your system, use the following command at a shell prompt:

$ uname -r

Compare your kernel version with the binary versions of the driver available at http://ts.fujitsu.com/support/. If there is a binary version of the driver that corresponds to your kernel version, download that. For

:example

iomemory-vsl-<kernel-version>-server_<driver-version>_amd64.deb

If there is no binary version of the driver corresponding to your kernel, download the source package. :For example

iomemory-vsl_<driver-version>.tar.gz

Exact packages names may vary, depending on driver and kernel version chosen.


3.

4.

5.

Download appropriate support .deb packages from http://ts.fujitsu.com/support/downloads.html. Examples:

fio-common_<driver-version>_amd64.deb

fio-firmware_<firmware-version>_all.deb

fio-sysvinit_<driver-version>_all.deb

fio-util_<driver-version>_amd64.deb

libfio_<driver-version>_amd64.deb

fio-smis_<version>_amd64.deb

fio-snmp-agentx_<version>_amd64.deb

fio-snmp-mib_<version>_amd64.deb

libfio-dev_<version>_amd64.deb

libfio-doc_<version>_amd64.deb

libfusionjni_<version>_amd64.deb

iomanager-gui_<version>_all.deb

iomanager-jre_<version>_amd64.deb

Do not use spaces in the current working directory name or the build will fail.

Build the driver from source: if you downloaded the driver source package, you must now follow theinstructions in . If you downloaded a binary version of the driver, continue.Building the ioMemory VSL from Source

Change to the directory to where you downloaded the installation packages.


6.

7.

1.

2.

3.

Use the following command to install each of the desired packages, adding package names as needed.

Your exact package names will depend on the file names you download. Use the ioMemory VSL packagename that is built for your kernel version.

$ dpkg -i iomemory-vsl-<kernel-version>-<driver-version>_amd64.debfio-firmware_<firmware-version>.deb fio-util_<driver-version>.deb

The drivers are now in /lib/modules/<kernel-version>/extra/fio/

The drivers and utilities are installed to the following locations:

Package Type Installation Location

Drivers /lib/modules/<kernel-version>/extra/fio/

Utilities /usr/bin

Firmware /usr/share/fio/firmware

SNMP MIB /usr/share/fio/mib

Continue to .Loading the ioDrive ioMemory VSL Facility (Driver)

Building the ioMemory VSL from Source

The ioMemory VSL is distributed as a source package. If a binary version of the driver is not available, you will need tobuild the ioMemory VSL from source. Use the source package that is made for your distribution. Source packagesfrom other distributions are not guaranteed to work.

Download current driver source and support packages from http://ts.fujitsu.com/support/downloads.html.

The exact source package to download depends on your operating system, but it is either an .rpmpackage (for operating systems that use packages) or a tarball installation package (for anything.rpmelse).

Change directory to wherever you downloaded the source package.

Follow the instructions in or below toBuilding a .rpm Installation Package Building from a Debian Source Packagecreate an installation package tailored to your needs.

Building a .rpm Installation Package

To build a .rpm installation package:


1.

2.

3.

Install the prerequisite files for your kernel version.

Some of the prerequisite packages may already be in the default OS installation. If your system is notconfigured to get packages over the network, then you may need to mount your install CD/DVD.

On RHEL4, you need , , and GCC4.kernel-devel-smp kernel-headers

$ yum install kernel-devel-smp kernel-headers gcc rsync

On RHEL 5/6, you need , , and GCC4.kernel-devel kernel-headers

$ yum install kernel-devel kernel-headers gcc rsync

On SLES 10/11 you need , , and GCC4kernel-syms make

$ zypper install kernel-syms gcc rsync make

To build an .rpm installation package for the current kernel, run this command:

$ rpmbuild --rebuild iomemory-vsl-<driver-version>.src.rpm

When using a .rpm source package for a non-running kernel, run this command:

$ rpmbuild --rebuild --define 'rpm_kernel_version <kernel-version>' iomemory-vsl-<driver-version>src.rpm

The new package is located in a directory that is indicated in the output from the command..rpm rpmbuildTo find it, look for the "wrote" line. In the following example, the .rpm packages are located in the

directory./usr/src/redhat/RPMS/x86_64/

...Processing files: iomemory-vsl-source-2.2.3.66-1.0.x86_64.rpmRequires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1rpmlib(CompressedFileNames) <= 3.0.4-1Obsoletes: iodrive-driver-sourceChecking for unpackaged file(s): /usr/lib/rpm/check-files/var/tmp/iomemory-vsl-2.2.3.66-rootWrote:/usr/src/redhat/RPMS/x86_64/iomemory-vsl-2.6.18-128.el5-2.2.3.66-1.0.x86_/usr/src/redhat/RPMS/x86_64/iomemory-vsl-source-2.2.3.66-1.0.x86_64.rpm

Make a note of the .rpm location; you will need this information later in the installation.


4.

5.

6.

1.

2.

3.

4.

5.

6.

You have now built installation packages for your distribution and kernel.

Copy your custom-built driver installation package (.rpm) into the directory where you downloaded theinstallation packages.

Return to the section of this guide.Installing RPM Packages

Building a Debian Installation Package

To build a Debian installation package:

Install the prerequisites for building the Fusion-io source driver package.

$ sudo apt-get install gcc fakeroot build-essential debhelperlinux-headers-$(uname --r) rsync

You can also install packages separately by running this command:

$ sudo apt-get install gcc rsync

Download the driver source file for your target operating system at http://ts.fujitsu.com/support/.

Unpack the driver source file.

$ tar zxvf iomemory-vsl_<driver-version>.tar.gz

Change directory to the folder created in the previous step.

$ cd iomemory-vsl-source-<driver-version>

Begin the driver rebuild.

$ sudo dpkg-buildpackage

You can also build the driver as a non-root user.

$ dpkg-buildpackage -rfakeroot -b

The new package is located in the parent directory..deb

A failure of any of these builds may be due to required packages missing from the system. The outputfrom the failed command informs you of which packages are missing. Try installing any missing packagesand then repeating the build process.


7.

8.

9.

1.

2.

You have now built installation packages for your distribution and kernel.

Copy your custom-built driver installation package (.deb) into the directory where you downloaded theinstallation packages.

Return to the section of this guide.Installing DEB Packages

Loading the ioDrive ioMemory VSL Facility (Driver)

To load the ioDrive driver:

Run this command:

$ modprobe iomemory-vsl

The ioMemory VSL automatically loads at system boot. The ioDrive is now available to the OS as , where is a letter (i.e., a, b, c, etc.)./dev/fiox x

On SLES11 you must allow unsupported modules for this command to work. Modify the file and uncomment the appropriate line:/etc/modprobe.d/iomemory-vsl.conf

# To allow the ioDrive driver to load on SLES11, uncommentbelowallow_unsupported_modules 1

To confirm the ioDrive is attached, run the utility from the command line. The output lists eachfio-statusdrive and its status (attached or not attached).

If the ioMemory device is not automatically attaching, check the /etc/modprobe.d files to see if the option is turned off (set to 0).auto_attach

Controlling ioMemory VSL Loading

You can control driver loading either through the init script or through udev.

In newer Linux distributions, users can rely on the udev device manager to automatically find and load drivers for theirinstalled hardware at boot time, though udev can be disabled and the init script used in nearly all cases. For older Linuxdistributions without this functionality, users must rely on a boot-time init script to load needed drivers. Fusion-ioprovides an init script in to load the ioDrive driver in older RHEL4 releases and/etc/init.d/iomemory-vslSLES10 distributions.


Using the init Script

On systems where udev loading of the driver doesn't work, or is disabled, the init script may be enabled to load thedriver at boot. On some distros it may be enabled by default.

The init Script is part of the package, which must be installed before you can enable it.fio-sysvinit

You can disable this loading of the ioDrive ioMemory VSL with the following command:

$ chkconfig --del iomemory-vsl

To re-enable the ioMemory VSL loading in the init script, use the following command:

$ chkconfig --add iomemory-vsl

For further details on the init script, see Using the Init Script later in this section.

Using udev

On systems that rely on udev to load drivers, users need to modify an ioDrive's options file if they want to preventudev from auto-loading the ioDrive ioMemory VSL at boot time. To do this, locate and edit the

file that already has the following line:/etc/modprobe.d/iomemory-vsl.conf

# blacklist iomemory-vsl

To disable loading, remove the "#" from the line and save the file.

With the blacklist command in place, restart Linux. The ioDrive ioMemory VSL will not be loaded by udev.

To restore the udev-loading of the ioMemory VSL, replace the "#" to comment out the line.

The version of on RHEL4u7/CentOS4u7 and earlier do not support the the 'blacklist' directive. Even if theudevdriver is blacklisted as documented, udev will still load the driver.

To blacklist the driver in these versions, put the name of the driver on its own line in the file. Example:/etc/hotplug/blacklist

iomemory-vsl


1.

2.

On either udev or init script systems

Users can disable the loading of the ioDrive ioMemory VSL at boot time, and thus prevent the auto-attach process fordiagnostic or troubleshooting purposes on either udev or init script systems. Follow the steps in the Disabling

section to disable or re-enable the auto-attach functionality.Auto-Attach

Alternatively, you can prevent the ioMemory VSL from loading by appending the following parameter at the kernelcommand line of your boot loader:

iodrive=0

However, this method is not preferred as it prevents the ioMemory VSL from functioning at all, thus limiting theamount of troubleshooting you can perform.

Using the Init Script

The ioDrive install process places an init script in . In turn, this script uses the setting/etc/init.d/iomemory-vsloptions found in the options file in . The options file must have ENABLED set/etc/sysconfig/iomemory-vsl(non-zero) for the init script to be used:

ENABLED=1

The options file contains documentation for the various settings---two of which, and MOUNTS, are discussed further in the Handling ioMemory VSL Unloads section later in thisKILL_PROCS_ON_UMOUNT

document.

Mounting Filesystems

Because the ioDrive ioMemory VSL does not load by the standard means (in the , or built into the kernel),initrdusing the standard method for mounting filesystems ( ) for filesystems hosted on the ioDrive does not/etc/fstabwork. To set up auto-mounting of a filesystem hosted on an ioDrive:

Add the filesystem mounting command to /etc/fstab as normal.

Add the 'noauto' option to etc/fstab as in the two following sample entries.

/dev/fioa /mnt/fioa ext3 defaults,noauto 0 0/dev/fiob1 /mnt/ioDrive ext3 defaults,noauto 0 0

(where the in can be , , , etc., depending on how many ioDrives you have installed in the system).a fioa a b c

To have the init script mount these drives after the ioMemory VSL is loaded and unmounted and before theioMemory VSL is unloaded, add a list of mount points to the options file using the procedure documented there.


For the filesystem mounts shown in the earlier example, the line in the options file would look like this:

MOUNTS="/mnt/fioa /mnt/iodrive"

Handling ioMemory VSL Unloads

Special consideration must be taken during ioMemory VSL unload time. By default, the init script searches for anyprocesses holding open a mounted filesystem and kills them, thus allowing the filesystem to be unmounted. Thisbehavior is controlled by the option in the options file. If these processes are not killed,KILL_PROCS_ON_UMOUNTthe filesystem cannot be unmounted. This may keep the ioMemory VSL from unloading cleanly, causing a significantdelay on the subsequent boot.

Setting the ioMemory VSL Options

This section explains how to set ioMemory VSL options. For more information about setting specific options, see .Appendix C- Using Module Parameters

One-Time Configuration

ioDrive ioMemory VSL options can be set at install time, on the command line of either or . Forinsmod modprobeexample, to set the ioMemory VSL option to 0, run the command:auto_attach

$ modprobe iomemory-vsl auto-attach=0

This option takes effect only for this load of this ioMemory VSL; subsequent calls to or will notmodprobe insmodhave this option set.

Persistent Configuration

To maintain a persistent setting for an option, add the desired option to /etc/modprobe.d/iomemory-vsl.confor a similar file. To prevent the ioDrives from auto-attaching, add the following line to the iomemory-vsl.conffile:

options iomemory-vsl auto_attach=0

This ioMemory VSL option then takes effect for every subsequent ioMemory VSL load, as well as on autoload of theioMemory VSL during boot time.


Upgrading the Firmware

With the ioDrive ioMemory VSL loaded, you need to check to ensure that the ioDrive's firmware is up-to-date. To dothis, run the command-line utility.fio-status

If the output shows that the device is running in minimal mode, download the latest firmware from http://ts.fujitsu.com/support/downloads.html, then use the ioManager application or the fio-update-iodrive

f utility to upgrade the firmware.

Only driver versions 1.2.4 and higher, with their corresponding firmware versions, can be upgraded to version2.1.0 or later. If your driver version is older than 1.2.4, it must be upgraded to 1.2.4 before advancing to adriver/firmware version later than that.

Using the ioDrive as Swap

To safely use the ioDrive as swap space requires passing the preallocate_memory kernel module parameter. Therecommended method for providing this parameter is to add the following line to the

file:/etc/modprobe.d/iomemory-vsl.conf

options iomemory-vsl preallocate_memory=1072,4997,6710,10345

Where 1072,4997,6710,10345 are serial numbers obtained from .fio-status

A 4K sector size format is required for swap—this reduces the driver memory footprint to reasonable levels. UseioManager or to format the ioDrive with 4k sector sizes.fio-format

Be sure to provide the serial numbers for the ioMemory modules, not the adapter.

The module parameter is necessary to have the drive usable as swap space. Seepreallocate_memoryAppendix D- Using Module Parameters for more information on setting this parameter.

You must have 400MB of free RAM per 80GB of ioDrive capacity (formatted to 4KB block size) to enable theioDrive with pre-allocation enabled for use as swap. Attaching an ioDrive, with pre-allocation enabled, withoutsufficient RAM may result in the loss of user processes and system instability.

The parameter is recognized by the ioMemory VSL at load time, but the requestedpreallocate_memorymemory is not actually allocated until the specified device is attached.


1.

2.

Using the Logical Volume Manager

The Logical Volume Manager (LVM) volume group management application handles mass storage devices like theioDrive if you add the ioDrive as a supported type:

Locate and edit the /etc/lvm/lvm.conf configuration file.

Add an entry similar to the following to that file:

types = [ "fio", 16 ]

The parameter "16" represents the maximum number of partitions supported by the drive.

If using LVM or MD, do not use udev to load the driver. The init script will ensure that the LVM volumes andMD devices are detached before attempting to detach the ioMemory device.

Configuring RAID

You can configure two or more ioDrives into a RAID array using software-based RAID solutions.

If you are using RAID1/Mirrored and one device fails, be sure to run on the replacement devicefio-format(not the existing, good device) before rebuilding the RAID. Following are some examples of some commonRAID configurations using the utility.mdadm

RAID 0

To create a striped set, where fioa and fiob are the two ioDrives you want to stripe, run this command:

$ mdadm --create /dev/md0 --chunk=256 --level=0 --raid-devices=2 /dev/fioa/dev/fiob

Making the Array Persistent (Existing after Restart)

On some versions of Linux, the configuration file is in , not /etc/mdadm/mdadm.conf./etc/mdadm.conf

Inspect , if there are one or more lines declaring the devices to inspect, make sure one of those/etc/mdadm.conflines specifies "partitions" as an option, if it does not add a new DEVICE line to the file specifying "partitions" likethis:


DEVICE partitions

Also add a device specifier for the ioDrive fio devices:

DEVICE /dev/fio*

To see if any updates are needed to , issue the following command:/etc/mdadm.conf

$ mdadm --detail --scan

Compare the output of this command to what currently exists in mdadm.conf and add any needed sections to/etc/mdadm.conf. For further details please see the mdadm and mdadm.conf man pages for your distribution.

With these changes, on most systems the RAID 0 array will be created automatically upon restart. However, if youhave problems accessing after restart, run the following command:/dev/md0

$ mdadm --assemble --scan

You may also want to disable udev loading of the driver, if needed, and use the init script provided for driver loading.Please see the section of this guide for further details on how to use the init script.Using the Init Script

RAID 1

To create a mirrored set using the two ioDrives and , run this command:fioa fiob

$ mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/fioa /dev/fiob

RAID 10

To create a striped, mirrored array using four ioDrives (fioa, fiob, fioc, and fiod), run this command:

$ mdadm --create /dev/md0 -v --chunk=256 --level=raid10 --raid-devices=4/dev/fioa /dev/fiob /dev/fioc /dev/fiod

Building a RAID10 across Multiple ioDrive Duos

In a RAID10 configuration, sets of two disks are mirrored, and then those mirrors are striped. When setting up aRAID10 across multiple ioDrive Duos, it is best to make sure that no mirror resides solely on the two ioMemorymodules that comprise an ioDrive Duo.


In order to get the data to lay out properly,

Use the option when creating the RAID10 (though it should be the default)--layout=n2

Ensure that no two ioMemory modules from the same duo are listed side by side.

The following sample code shows some recommended configurations.

The following commands assume that all ioMemory modules have been freshly formatted with the utility.fio-format

The ordering of the fiox devices is critical.

# 2 Duos RAID10$ mdadm --create --assume-clean --level=raid10 --layout=n2 -n 4 /dev/md0 \ /dev/fioa /dev/fioc \ /dev/fiob /dev/fiod# Mirror groups are: fioa,fioc and fiob,fiod

# 3 Duos RAID10$ mdadm --create --assume-clean --level=raid10 --layout=n2 -n 6 /dev/md0 \ /dev/fioa /dev/fiod \ /dev/fioc /dev/fiof \ /dev/fioe /dev/fiob

# 4 Duos RAID10$ mdadm --create --assume-clean --level=raid10 --layout=n2 -n 8 /dev/md0 \ /dev/fioa /dev/fiod \ /dev/fioc /dev/fiof \ /dev/fioe /dev/fioh \ /dev/fiog /dev/fiob

# 8 Duos RAID10$ mdadm --create --assume-clean --level=raid10 --layout=n2 -n 16 /dev/md0 \ /dev/fioa /dev/fiod \ /dev/fioc /dev/fiof \ /dev/fioe /dev/fioh \ /dev/fiog /dev/fioj \ /dev/fioi /dev/fiol \ /dev/fiok /dev/fion \ /dev/fiom /dev/fiop \ /dev/fioo /dev/fiob


Understanding Discard (TRIM) Support

With driver version 2.2.0 and later, Discard (also known as TRIM) is enabled by default.

Discard addresses an issue unique to solid-state storage. When a user deletes a file, the device does not recognize that itcan reclaim the space. Instead the device assumes the data is valid.

Discard is a feature on newer filesystem releases. It informs the device of logical sectors that no longer contain validuser data. This allows the wear-leveling software to reclaim that space (as reserve) to handle future write operations.

Discard (TRIM) on Linux

Discard is enabled by default in the Linux ioMemory VSL (driver), version 2.2.0 and later. However, for discard to beimplemented, the Linux distribution must support this feature, and discard must be turned on.

In other words, if your Linux distribution supports discard, and discard is enabled on the system, then discard will beimplemented on your ioDrive device.

Under Linux, discards are not limited to being created by the filesystem, discard requests can also be generated directlyfrom userspace applications using the kernels discard ioctl.

There is a known issue that ext4 in Kernel.org 2.6.33 or earlier may silently corrupt data when discard is enabled.This has been fixed in many kernels provided by distribution vendors, please check with your kernel provider tobe sure your kernel properly supports discard. For more information, see the Errata in the for thisRelease Notesversion of the driver

On Linux, MD and LVM do not currently pass discards to underlying devices. Thus any ioDrive device that ispart of an MD or LVM array will not receive discards sent by the filesystem.


Maintenance

The ioDrive includes both software utilities for maintaining the device as well as external LED indicators to display itsstatus. You can also install SNMP as a monitoring option.

ioDrive LED Indicators

The ioDrive includes three LEDs showing drive activity or error conditions.

Optional External Hard Drive LED

You can also use your computer's existing external HDD access light to indicate a combination of both the reads andwrites executing on your ioDrive. This provides a quick activity check for your device. (See the forHardware User Guideinstructions on how to connect this LED to the ioDrive pinout.)


ioManager

Your ioDrive software includes the ioManager. This application performs the most common operations you need todo with the ioDrive. In addition, it provides a detailed information screen on each of your installed devices.

The ioManager can perform:

Firmware upgrades

Low-level formatting

Attach and detach actions

Device status and performance information

The ioManager installs as an package. Details on how to install and use ioManager appear in the ioManager UserRPMGuide.

Command-line Utilities

Several command-line utilities are included in the installation packages for managing your ioDrive:

fio-attach

fio-beacon

fio-bugreport

fio-detach

fio-format

fio-pci-check

fio-snmp-agentx

fio-status

fio-update-iodrive

For more information on command-line utilities, see Appendix A- Utilities Reference

Common Maintenance Tasks

The following are the most common tasks for maintaining your ioDrive using command-line utilities. (You can alsouse the ioManager application to do firmware upgrades as well.)

All commands require administrator privileges. Log in as "root" or use sudo to run the commands.


If you came to this section from the section, to that section after you uninstall previousSoftware Installation returnversions of the driver and utilities.

Unloading the ioMemory VSL

To unload the ioMemory VSL, run this command:

$ modprobe -r iomemory-vsl

Uninstalling the ioMemory VSL RPM Package

Versions 1.2.x

Remove prior versions of the ioDrive driver using this command:

$ rpm -e iodrive-driver

Versions 2.x.x

With versions 2.x.x of the ioMemory VSL, you must specify the kernel version of the package you are uninstalling.Run this command to find the installed driver packages:

$ rpm -qa | grep -i iomemory

Sample output:

iomemory-vsl-2.6.18-194.el5-2.2.2.82-1.0

Uninstall the ioMemory VSL by running a command similar to this example (specify the kernel version of the driveryou wish to uninstall):

$ rpm -e iomemory-vsl-2.6.18-194.el5-2.2.0.82-1.0

Uninstalling the ioMemory VSL DEB Package

Versions 1.2.x

Remove prior versions of the ioDrive driver using this command:


$ dpkg -r iodrive-driver

Versions 2.x.x

With versions 2.x.x of the ioMemory VSL, you must specify the kernel version of the package you are uninstalling.Run this command to find the installed driver packages:

$ dpkg -l | grep -i iomemory

Sample output:

iomemory-vsl-2.6.32-24-server

Uninstall the ioMemory VSL by running a command similar to this example (specify the kernel version of the driveryou wish to uninstall):

$ dpkg -r iomemory-vsl-2.6.32-24-server

Uninstalling the ioDrive Utilities, ioManager, and Other Support Packages

To uninstall the support RPM packages, run this command (adding or removing package names as needed):

$ rpm -e fio-util fio-snmp-agentx fio-common fio-firmware iomanager-guiiomanager-jre libfio-doc libfusionjni fio-sysvinit

To uninstall the support DEB packages, run this command (adding or removing package names as needed):

$ dpkg -r fio-util fio-snmp-agentx fio-common fio-firmware iomanager-guiiomanager-jre libfio-doc libfusionjni fio-sysvinit fio-smis fio-snmp-miblibfio-dev

Disabling Auto-Attach

When the ioDrive ioMemory VSL is installed, it is configured to automatically attach any devices when the ioMemoryVSL is loaded. Sometimes you may want to disable the auto-attach feature. To do so:


1.

2.

3.

1.

2.

Edit the following file:

/etc/modprobe.d/iomemory-vsl.conf

Add the following line to that file:


Save the file. To re-enable auto-attach, simply edit the file and either remove that line or change it to thefollowing:


Unmanaged Shutdown Issues

Unmanaged shutdowns due to power loss or other circumstances can force the ioDrive to perform a consistencycheck during the restart. This may take several minutes or more to complete and is shown by a progress percentageduring startup.

Although data written to the ioDrive is not lost due to unmanaged shutdowns, important data structures may not havebeen properly committed to the drive. This consistency check repairs these data structures.

Disabling the ioMemory VSL

The ioDrive ioMemory VSL automatically loads by default when the operating system starts. You can disableioMemory VSL auto-load for diagnostic or troubleshooting purposes.

To disable ioMemory VSL auto-load:

Append the following parameter at the kernel command line of your boot loader:

iodrive=0

The ioDrive ioMemory VSL won't load, so the device won't be available to users.

You can also uninstall the ioMemory VSL to keep it from loading, or move it out of the directory./lib/modules/<kernel_version>

Proceed with troubleshooting to correct the problem. If the problem is outdated firmware, use toiodrive=1place the ioMemory VSL in minimal mode. You can then use or the ioManagerfio-update-iodriveapplication to update the firmware.


3. Use either the utility or the ioManager application to attach the ioMemory VSL to the operatingfio-attachsystem.


Appendix A- Utilities Reference

The ioDrive installation packages include various command-line utilities, installed by default to . These/usr/binprovide a number of useful ways to access, test, and manipulate your device.

Utility Purpose

fio-attach Makes an ioDrive available to the OS

fio-beacon Lights the ioDrive's external LEDs

fio-bugreport Prepares a detailed report for use in troubleshooting problems

fio-detach Temporarily removes an ioDrive from OS access

fio-format Used to perform a low-level format of an ioDrive

fio-pci-check Checks for errors on the PCI bus tree, specifically for ioDrives

fio-snmp-agentx SNMP sub-agent that implements the SNMP FUSION-IODRV-MIB for the Fusion-ioioMemory VSL

fio-status Displays information about the device

fio-update-iodrive Updates the ioDrive's firmware

There are (Help) and (Version) options for all of the utilities. Also, and cause the utility to exit after-h -v -h -vdisplaying the information.

fio-attach

Description

Attaches the ioDrive and makes it available to the operating system. This creates a block device in named /dev fiox(where is , , , etc.). You can then partition or format the ioDrive, or set it up as part of a RAID array. Thex a b ccommand displays a progress bar and percentage as it operates.

In most cases, the ioMemory VSL automatically attaches the device on load and does a scan. You only need torun if you ran or if you set the ioDrive's auto_attach parameter to 0.fio-attach fio-detach


Syntax

fio-attach <device> [-q, -h, -v]

where is the name of the device node ( ), where indicates the card number: 0, 1, 2, etc. For<device> /dev/fctx xexample, indicates the first ioDrive installed on the system./dev/fct0

You can specify multiple ioDrives. For example, indicates the second and third ioDrives/dev/fct1 /dev/fct2installed on the system. You can also use a wildcard to indicate all ioDrives on the system. For example, /dev/fct*

Option Description

-q Quiet: disables the display of the progress bar and percentage.

fio-beacon

Description

Lights the ioDrive's three LEDs to locate the device. You should first detach the ioDrive and then run .fio-beacon

This utility always turns the LEDs on, unless you specifically use the option.-0

Syntax

fio-beacon <device> [-0, -1, -p, -h, -v]


Options Description

-0 Off: Turns off the three LEDs

-1 On (default): Lights the three LEDs

-p Prints the PCI bus ID of the device at to standard output. Usage and error information may be written<device>to standard output rather than to standard error.

fio-bugreport

Description

Prepares a detailed report of the device for use in troubleshooting problems. The results are saved in the /tmpdirectory in the file that indicates the date and time the utility was run.


Example:

/tmp/fio-bugreport-20100121.173256-sdv9ko.tar.bz2

Syntax

fio-bugreport

Notes

This utility captures the current state of the device. When a performance or stability problem occurs with the device,run the utility and send the output to your Fujitsu service representative for assistance. fio-bugreport

Sample Output

-bash-3.2# fio-bugreport /tmp/fio-bugreport-20090921.173256-sdv9ko ~Collecting fio-status -aCollecting fio-status Collecting fio-pci-check Collecting fio-pci-check -v Collecting fio-read-lebmap /dev/fct0 Collecting fio-read-lebmap -x /dev/stdout/dev/fct0 Collecting fio-read-lebmap -t /dev/fct0 Collecting fio-get-erase-count/dev/fct0 Collecting fio-get-erase-count -b /dev/fct0 Collecting lspci Collecting lspci -vvvvv Collecting lspci -tv Collecting messages file(s) Collecting procfusion file(s) Collecting lsmod Collecting uname -a Collecting hostname Collecting sar -r Collecting sar Collecting sar -A Collecting syslog file(s) Collecting proc file(s) Collecting procirq file(s) Collecting dmidecode Collecting rpm -qa iodrive* Collecting find /lib/modules Please send the file /tmp/fio-bugreport-20090921.173256-sdv9ko.tar.bz2along with your bug report to [email protected] The file is in the /tmpdirectory.


For example, the filename for a bug report file named indicates the following:/tmp/fiobugreport-20090921.173256-sdvk0.tar.bz2

Date (20090921)

Time (173256, or 17:32:56)

Misc. information ( )sdv9ko.tar.bz2

fio-detach

Description

Detaches the ioDrive and removes the corresponding ioDrive block device from the OS. The fctx fio-detachutility waits until the device completes all read/write activity before executing the detach operation. By default, thecommand also displays a progress bar and percentage as it completes the detach.

Before using this utility, ensure that the device you want to detach is not currently mounted and in use.

Syntax

fio-detach <device> [-i, -q, -h, -v]


You can specify multiple ioDrives. For example, indicates the second and third ioDrives/dev/fct1 /dev/fct2installed on the system. You can also use a wildcard to indicate all ioDrives on the system. For example, /dev/fct*

Options Description

-i Immediate: Causes a forced immediate detach (does not save metadata). This will fail if the device is in use by theOS.

-q Quiet: Disables the display of the progress bar and percentage.

Notes

With version 2.0 and later of the driver, attempting to detach an ioDrive may fail with an error indicating that thedevice is busy. This typically may occur if the ioDrive is part of a software RAID (0,1,5) volume, is mounted, or someprocess has the device open.

The tools fuser, mount, and lsof can be helpful in determining what is holding the device open.


fio-format

Description

The ioDrive ships pre-formatted, so is generally not required except to change the logical size orfio-formatblock size of the device, or to erase user data on the drive.

Performs a low-level format of the board. By default, displays a progress-percentage indicator as it runs.fio-format

Use this utility with care, as it deletes all user information on the board.

Using a larger block (sector) size, such as 4096 bytes, can significantly reduce worst-case ioDrive host memoryconsumption. However, some applications are not compatible with non-512-byte sector sizes.

If you do not include the or options, the drive size defaults to the advertised capacity. If used, the and -s -o -s options must include the size or percentage indicators.-o

Syntax

fio-format <device> [-b <size>, -f, -o <size B|K|M|G|T|%>, -q, -s<device-size>, -y, -h, -v]


Options Description

-b <sizeB|K>

Set the block (sector) size, in bytes or KiBytes (base 2). The default is 512 bytes. For example: -b 512Bor ( in is optional).-b 4K B 512B

-f Force the format size, bypassing normal checks and warnings. This option may be needed in rare situationswhen does not proceed properly. (The "Are you sure?" prompt still appears unless you usefio-formatthe option.) This option can only be used with the option.-y -o

-q Quiet mode: Disable the display of the progress-percentage indicator.


-s <sizeB|K|M|G|T|%>

Set the device capacity as a specific size (in TB, GB, or MB) or as a percentage of the advertised capacity:

T Number of terabytes (TB) to format

G Number of gigabytes (GB) to format

M Number of megabytes (MB) to format

% Percentage, such as 70% (the percent sign must be included).

-o <sizeB|K|M|G|T|%>

Over-format the device size (to greater than the advertised capacity), where the maximum size equals themaximum physical capacity. If a percentage is used, it corresponds to the maximum physical capacity of thedevice. (Size is required for the option; see the option above for size indicator descriptions.)-o -s

Before you use this option, please discuss your use case with your Fujitsu servicerepresentative or call customer support (see http://ts.fujitsu.com/support/servicedesk.html).

.

-y Auto-answer "yes" to all queries from the application (bypass prompts).

fio-pci-check

Description

Checks for errors on the PCI bus tree, specifically for ioDrives. This utility displays the current status of each ioDrive.It also prints the standard PCI Express error information and resets the state.

It is perfectly normal to see a few errors (perhaps as many as five) when fio-pci-check is initially run. Subsequentruns should reveal only one or two errors during several hours of operation.

Syntax

fio-pci-check [-d <value>, -f, -i, -r, -v, -y, -h]

Options Description

-d <value> 1 = Disable the link; 0 = bring the link up (Not recommended)

-f Scan every device in the system.

-i Print the device serial number. This option is invalid when the ioMemory VSL is loaded.

-r Force the link to retrain.

-v Verbose: Print extra data about the hardware.


fio-snmp-agentx

Description

This utility is an SNMP sub-agent that implements the SNMP FUSION-IODRV-MIB for the Fusion-io ioMemoryVSL. fio-snmp-agentx communicates with the SNMP master agent via the agentx protocol.

Syntax

fio-snmp-agentx [-c, -f, -l <log file>, -m, -s, -h, -v]

Option Description

-c <config file>

This option is not supported for 2.1.0 or later

-f Force the sub-agent to run in the foreground instead of as a daemon.

-l <log file> Log file to use.

-m

This option is not supported for 2.1.0 or later

-s Send errors to stderr instead of to syslog.

Configuration File

Field Setting Description

test_mode_enabled true/false Enables test mode (must be 'true' to enable the test-mode file) configuration

testmode_file <filename> Pathname of test-mode file. The default is 'testmode.ini' in the startup directory.

update_delay <msec> Sets the rate (in milliseconds) for polling the ioMemory VSL for updated data

traps_enabled true/false Enables traps (default=false)

fio-status

Description

Provides detailed information about the installed devices. This utility operates on either or devices. Thefctx fioxutility depends on running as root and having the ioMemory VSL loaded. If no ioMemory VSL is loaded, a smaller setof status information is returned.


fio-status provides alerts for certain error modes, such as a minimal-mode, read-only mode, and write-reducedmode, describing what is causing the condition.

Syntax

fio-status <device> [-a, -c, -d, -fk, -h, -v]


If is not specified, displays information for all cards in the system. If the ioMemory VSL is not<dev> fio-statusloaded, this parameter is ignored.

Options Description

-c Count: Report only the number of ioDrives installed.

-d Show basic information set plus the total amount of data read and written (lifetime data volumes). This option is notnecessary when the -a option is used.

-fk Format key: Force alternate <"key=value"> format output, which may be easier for scripts and parsing programs toread.

-a Print all available information for each device.

Basic Information: If no options are used, reports the following basic information:fio-status

Number and type of cards installed in the system

Driver versionAdapter information:

Adapter type

Product number

PCI power limit threshold (if available)

Connected ioMemory modulesBlock device information:

Attach status

Product name

Product number

Serial number

Firmware version

Size of the device, out of total capacity


Internal temperature (average and maximum, since ioMemory VSL load) in degrees Centigrade

Health status: healthy, nearing wearout, write-reduced or read-only

Reserve capacity (percentage)

Warning capacity threshold (percentage)

Data Volume Information: If the -d option is used, the following data volume information is reported toin additionthe basic information:

Physical bytes written

Physical bytes read

All Information: If the option is used, all information is printed, which includes the following information -a in to basic and data volume information:addition

Adapter information:

Manufacturer number

Date of manufacture

Power loss protection status

PCIe bus voltage (avg, min, max)

PCIe bus current (avg, max)

PCIe power limit threshold (watts)

PCIe slot available power (watts)

PCIe negotiated link information (lanes and throughput)

Block device information:

Part number

Manufacturer's code

Manufacturing date

PCIe slot number

Vendor and sub-vendor information

Size of the device, out of total capacity

Format status and sector information (if device is attached)

FPGA ID and Low-level format GUID

PCIe slot available power


PCIe negotiated link information

Card temperature, in degrees Centigrade

Internal voltage, avg. and max.

Auxiliary voltage:, avg. and max.

Percentage of good blocks, data and metadata

Lifetime data volume statistics

Error Mode Information: If the ioMemory VSL is in minimal mode, read-only mode, or write-reduced mode when is run, the following differences occur in the output:fio-status

Attach status is "Status unknown: Driver is in MINIMAL MODE:"

The reason for the minimal mode state is displayed (such as "Firmware is out of date. Update firmware.")

"Geometry and capacity information not available." is displayed.

No media health information is displayed.

fio-update-iodrive

You should back up the data on the ioDrive prior to any upgrade as a precaution.

Description

Updates the ioDrive's firmware. This utility scans the PCIe bus for all ioDrives and updates them. A progress bar andpercentage are shown for each drive as the update completes.

It is extremely important that the power not be turned off during a firmware upgrade, as this could cause devicefailure. If a UPS is not already in place, consider adding one to the system prior to performing a firmwareupgrade.

Note that when running multiple upgrades in sequence (such as going from 1.2.1 to 1.2.4 to 2.1.0), it is critical toload the driver after each firmware upgrade step. Otherwise the on-drive format will not be changed, and therewill be data loss.

Do not use this utility to downgrade the ioDrive to an earlier version of the firmware. Doing so may result in dataloss. Contact customer support at http://ts.fujitsu.com/support/ if you need to downgrade your firmware.


The default action (without using the or option) is to upgrade all ioDrive devices with the firmware-d -scontained in the file. Confirm that all devices need the upgrade prior to running<iodrive_version.fff>the update. If in doubt, use the (Pretend) option to view the possible results of the update.-p

You must detach all ioDrive devices before updating the firmware.

Only driver versions 1.2.4 and higher, with their corresponding firmware versions, can be upgraded to version2.1.0 or later. If your driver version is older than 1.2.4, it must be upgraded to 1.2.4 before advancing to adriver/firmware version later than that.

If you receive an error message when updating the firmware that instructs you to update the midprominformation, contact Customer Support.

To update one or more specific drives:

If the ioMemory VSL is loaded, use the option with the device number.-d

Syntax

fio-update-iodrive <iodrive_version.fff> [-d, -f, -l, -p, -q, -s, -h, -v]

where is the path and firmware archive file provided by Fusion-io. The default path is <iodrive_version.fff>. This parameter is required./usr/share/fio/firmware

Options Description

-d Updates the specified devices (by , where is the number of the device shown in ). If thisfctx x fio-statusoption is not specified, all devices are updated.

Use the or options with care, as updating the wrong ioDrive could damage your device.-d -s

-f Force upgrade (used primarily to downgrade to an earlier firmware version). If the ioMemory VSL is not loaded, thisoption also requires the option.-s

Use the -f option with care, as it could damage your card.

-l List the firmware available in the archive.

-p Pretend: Shows what updates would be done. However, the actual firmware is not modified.

-q Runs the update process without displaying the progress bar or percentage.


-s Updates the devices in the specified slots using '*' as a wildcard for devices. The slots are identified in the followingPCIe format (as shown in lspci):

[[[[<domain>]:]<bus>]:][<slot>][.[<func>]]

All three external LED indicators light up during the update process.


Appendix B- Monitoring the Health of ioDrive Devices

This section describes how the health of ioDrive devices can be measured and monitored in order to safeguard dataand prolong device lifetime.

NAND Flash and Component Failure

An ioMemory product is a highly fault-tolerant storage subsystem that provides many levels of protection againstcomponent failure and the loss nature of solid-state storage. As in all storage subsystems, component failures mayoccur.

By proactively monitoring device age and health, you can ensure reliable performance over the intended product life.

Health Metrics

The ioMemory VSL manages block retirement using pre-determined retirement thresholds. The ioManager and the utilities show a health indicator that starts at 100 and counts down to 0. As certain thresholds arefio-status

crossed, various actions are taken.

At the 10% healthy threshold, a one-time warning is issued. See the 'monitoring' section below for methods forcapturing this alarm event.

At 0%, the device is considered unhealthy. It enters mode, which somewhat prolongs its lifespan so datawrite-reducedcan be safely migrated off. In this state the ioDrive behaves normally, except for the reduced write performance.

After the 0% threshold, the device will soon enter mode – any attempt to write to the ioDrive causes an error.read-onlySome filesystems may require special mount options in order to mount a read-only block device in addition tospecifying that the mount should be read-only.

For example, under Linux, requires that " " is used, the " " option tells the filesystem toext3 -o ro,noload noloadnot try and replay the journal.

Read-only mode should be considered a final opportunity to migrate data off the device, as device failure is more likelywith continued use.

The ioDrive may enter failure mode. In this case, the device is offline and inaccessible. This can be caused by aninternal catastrophic failure, improper firmware upgrade procedures, or device wearout.


For service or warranty-related questions please refer to the Fujitsu support site at http://ts.fujitsu.com/support/.

For ioDrive Duos, these modes are maintained independently for each half of the Duo and not for the Duo as awhole.

Health Monitoring Techniques

fio-status: Output from the utility shows the health percentage and drive state. These items arefio-statusreferenced as " " in the sample output below.Media status

Found 1 ioDrive in this systemFusion-io driver version: 2.2.3 build 240Adapter: ioDriveFusion-io ioDrive 160GB, Product Number:FS1-002-161-ES...Media status: Healthy; Reserves: 100.00%, warn at 10.00%; Data: 99.12%Lifetime data volumes: Physical bytes written: 6,423,563,326,064 Physical bytes read : 5,509,006,756,312

ioManager: In the Device Report tab, look for the Reserve Space percentage in the right column. The higher thepercentage, the healthier the drive is likely to be.

SNMP/SMI-S: On Windows or Linux, see the corresponding appendix for details on how to configure SNMP orSMI-S health indicators.

The following Health Status messages are produced by the utility:fio-status

Healthy

Low metadata

Read-only

Reduced-write

Unknown


Software RAID and Health Monitoring

Software RAID stacks are typically designed to detect and mitigate the failure modes of traditional storage media. TheioDrive attempts to fail as gracefully as possible, and these new failure mechanisms are compatible with existingsoftware RAID stacks. An ioDrive in a RAID group will fail to receive data at a sufficient rate if a) the drive is in awrite-reduced state, and b) it is participating in a write-heavy workload. In this case, the drive will be evicted from theRAID group. A drive in read-only mode will be evicted when write I/Os are returned from the device as failed.Catastrophic failures are detected and handled just as though they are on traditional storage devices.


Appendix C- Using Module Parameters

The following table describes the module parameters you can set by editing the file and changing their values./usr/modprobe.d/iomemory-vsl.conf

These changes must be completed before the ioMemory VSL is loaded in order to take effect.

Module Parameter Default(min/max)

Description

auto_attach True Attach the device on startup.

fio_dev_wait_timeout_secs 30 Number of seconds to wait for /dev/fio* files to show up during driverload. For systems not using udev, this should be set to 0 to disable thetimeout and avoid an unneeded pause during driver load.

force_minimal_mode False Force minimal mode on the device.

parallel_attach True Enable parallel attach of multiple drivers.

preallocate_memory No devicesselected

For the selected devices, pre-allocate all memory necessary to have thedrive usable as swap space.

tintr_hw_wait 0 (0, 255) Interval (microseconds) to wait between hardware interrupts. Alsoknown as interrupt coalescing. 0 is off.

use_workqueue 3 (1 or 3) Linux only: 3=use standard OS I/O elevators; 0=bypass.

Other than the , module parameters are global — they apply to all Fusion-io devicespreallocate_memoryin the computer.


Appendix D- Setting Up SNMP

The SNMP agent is an RFC 2741-compliant AgentX sub-agent. It can work with anyfio-snmp-agentxRFC-compliant SNMP agent, such as Net-SNMP. The master SNMP agent defers queries to forfio-snmp-agentxsupported MIBs.

SNMP Master Agent

The , provided in the package, requires an already-installed SNMP master agent. Thefio-snmp-agentx fio-utilSNMP master agent must support and be configured for AgentX connections (see ).http://www.ietf.org/rfc/rfc2741.txtThe is tested and verified with Net-SNMP, which is the typical SNMP agent provided with mostfio-snmp-agentxLinux distributions.

There are several agents available that support this functionality. If you choose to use Net-SNMP, then use theinstructions in the following sections to configure and launch it.

Launching the SNMP Master Agent

Install the Net-SNMP package using the package manager for your version of Linux.

Red Hat

Use the following command to install Net-SNMP on Red Hat:

yum install net-snmp rsync

Other Linux Versions

Use the standard system package manager to install the package on your Linux distribution. The Net-SNMP package places MIB files in .fio-snmp-mib /usr/share/fio/mib

Configuring the Master Agent

You can configure the Net-SNMP master agent daemon to set the network communications parameters, security, andother options by using the text file. The location of this file is system-dependent; often it is in snmpd.conf

or ./etc/snmp /usr/share/snmp


1.

2.

A simple configuration file might include the following:snmpd

# set standard SNMP variables syslocation "Data room, third rack" syscontact [email protected] # required to enable the AgentX protocol master agentx agentxsocket tcp:localhost:705 #set the port that the agent listens on (defaults to 161) agentaddress 161 # simple access control (some form of access control is required) rocommunity public

Running the Master Agent

Once you install and configure the master agent, you must start or restart the daemon for the new parameterssnmpdto take effect. You can simply run from its installed location (often – see the man page forsnmpd /usr/sbin snmpdoptions). It typically needs root privileges to run properly. You can also use the startup script in snmpd

. If you are concerned about security, use the more advanced SNMPv3/etc/init.d or /etc/rc.d/init.daccess control instead of the and access control directives as outlined in the relevantrocommunity rwcommunityman page.

Fusion-io SNMP AgentX Subagent

Installing the Fusion-io SNMP Subagent

Download the Fusion-io SNMP packages from http://ts.fujitsu.com/support/downloads.html.

Install the package using your operating systems package manager. For instance, on Red Hat, run the following:

rpm -Uvh fio-snmp-*.rpm

The ioDrive SNMP package places its MIB files in ./usr/share/fio/mib


1.

2.

3.

1.

2.

Running and Configuring the Fusion-io SNMP Subagent

Configure the subagent by creating a fio-snmp-agentx.conf file.

Store this .conf file in the directory where the snmpd.conf file is located for the master agent.

At a minimum, set the agent network parameters in this file similar to the following:

# required to enable the AgentX protocol

agentxsocket tcp:localhost:705

This must match the AgentX network parameters in the file for the master agent. For further AgentXsnmpd.confconfiguration information, consult the man pages or visit .http://www.net-snmp.org

The script will launch automatically at boot time once the installation andfio-snmp-agentx startupconfiguration is complete.

Manually Running the Fusion-io SNMP Subagent

If you need to run the Fusion-io SNMP Subagent manually, follow these steps:

After the SNMP master agent is started, start the subagent by running this command:

/usr/bin/fio-snmp-agentx

This command launches the ioDrive subagent using the Net-SNMP configuration file named . This file must reside in one of the Net-SNMP configuration directories: fio-snmpagentx.conf

, , or . (These paths can be changed;/etc/snmp, /usr/share/snmp /usr/lib/snmp $HOME/.snmpconsult the man page for .)snmp_config

You can now view the ioDrive management information using an SNMP MIB browser or by using a networkmanagement system accessing (in ).FIOioDrv.mib /usr/share/fio/mib

Subagent Log File

The ioDrive SNMP subagent can maintain a log file regarding its own activities. This file is separate from the MIB, asit includes entries on the subagent's communications with the master agent, including any errors or intermittent issues.

To have the subagent maintain this log file, include the parameter and a path to the log file as part of the--lcommand in running the subagent. For example, this command:

fio-snmp-agentx -l /usr/snmp/subagent.log


1.

2.

3.

keeps the subagent log file as , in the directory.subagent.log /usr/snmp

The ioDrive SNMP subagent is now ready to monitor your device.

Using the SNMP Sample Config Files

When you install SNMP, the following sample config files are available:

/usr/share/doc/fio-snmp-agentx/conf/snmpd.conf/ (master agent)

/usr/share/doc/fio-snmp-agentx/conf/fio-snmp-agentx.conf/ (sub-agent)

To customize and use the sample config files,

Rename your (such as to ) and your filesnmpd.conf file snmpd-orig.conf fio-snmp-agentx.conf(such as to ). These files usually reside in or fio-snmp-agentx-orig.conf /etc/snmp

./usr/share/snmp

In the directory, copy the sample file and a sample /usr/share/doc/fio-snmp/conf/ snmpd.conf file to your target SNMP directory.fio-snmp-agentx.conf

Edit the sample files you copied and save your changes as and .snmpd.conf fio-snmp-agentx.conf

Enabling SNMP Test Mode

When the SNMP Agentx runs, it reads the file:fio-snmp-agentx config


1.

2.

3.

4.

#################################################################### Example config file for fio-snmp-agentx SNMP AgentX subagent. ## Fusion-io, Inc. #

agentxsocket tcp:localhost:705

# test_mode_enabled # set to 1, true or yes to enable 0, false or no to disable (default: false)test_mode_enabled true # traps_enabled traps_enabled true # testmode_file # name of test mode file (default: testmode.ini) testmode_file testmode.ini

# update_delay # delay between agent polling requests in milliseconds (default: 250) update_delay 100

# mib_select # set to fio for FUSIONIO-IODRV-MIB or cpq for CPQIODRV-MIB (default: fio) mib_select fio ###################################################################

Conditions for test mode are described below.

If the Admin has set the parameter from TRUE to FALSE, the Fusion-io SNMP doestest_mode_enablednot try to run test mode. Instead, it continues processing data as usual from the ioMemory VSL, storing thedata in the MIB.

If the CONF file says that is TRUE, the SNMP subagent reads the istest_mode_enabled testmode.iniread periodically by the subagent to check for any changes. A sample testmode.ini file is installed in

./usr/share/doc/fio-snmp-agentx/conf

If the file shows the test mode is set to ON, then it engages the test mode.testmode.ini

If test mode is ON, the SNMP Agentx reads the next line, , to identify which ioDrive orTestModeIndexioDrive to test. The number in this parameter is the PCIe device number shown using such as:fio-status

PCI:01:00.0

The first two numerals identify the PCIe bus number (in this case, 01). This bus number is reported in , whereas the in the file must be specified in decimal. Thehexadecimal TestModeIndex testmode.ini

converted number should be entered into . The must be a valid bus numbertestmode.ini TestModeIndexof an ioDrive installed in the system.


The Fusion-io SNMP subagent now replaces any existing ioDrive ioMemory VSL data it may have (for the ioDrivespecified by TestModeIndex) with any populated fields in the list of parameters. If a field is not populated, Agentxretains the existing data and reports it to the MIB. If there is a value in a field, then the Agentx replaces that data andreports it to the MIB.

The subagent continues in test mode until the file parameter is set to OFF. The test mode information is.INIdescribed in the file :testmode.ini

# SNMP Test Mode sample file.# These values may be used to test the SNMP subsystem when it is in testmode.

[SNMP Agent Test Mode]TestMode = offTestModeIndex = 0

# InfoState: Note that the following states may change, but currentdefinitions are:# 0 = unknown# 1 = detached# 2 = attached# 3 = minimal mode# 4 = error# 5 = detaching# 6 = attaching# 7 = scanning# 8 = formatting# 9 = updating firmware# 10 = attach# 11 = detach# 12 = format# 13 = update


InfoState = 2

InfoInternalTemp = 45InfoAmbientTemp = 35InfoWearoutIndicator = 2 ; 2=normal, 1=device is wearing out.InfoWritableIndicator = 2 ; 2=normal, 1=non-writable, 0=write-reduced,3=unknownInfoFlashbackIndicator = 2 ; 2=normal, 1=flashback protection degraded.

ExtnTotalPhysCapacityU = 23ExtnTotalPhysCapacityL = 215752192ExtnUsablePhysCapacityU = 21ExtnUsablePhysCapacityL = 7852192ExtnUsedPhysCapacityU = 4ExtnUsedPhysCapacityL = 782330816ExtnTotalLogCapacityU = 18ExtnTotalLogCapacityL = 2690588672ExtnAvailLogCapacityU = 14ExtnAvailLogCapacityL = 3870457856

ExtnBytesReadU = 18ExtnBytesReadL = 3690588672ExtnBytesWrittenU = 4ExtnBytesWrittenL = 2578550816

InfoHealthPercentage = 95

InfoMinimalModeReason = 7 ; 0=unknown, 1=fw out of date,2=low power, ; 3=dual plane failure, 5=internal,6=card limit, ; 7=not in minimal mode,8=unsupported OS, ; 9=low memory

InfoReducedWriteReason = 0 ; 0=none, 1=user requested, 2=no mdblocks, ; 3=no memory, 4=failed die,5=wearout, ; 6=adapter power, 7=internal,8=power limit


InfoMilliVolts = 12000InfoMilliVoltsPeak = 12100InfoMilliVoltsMin = 11900InfoMilliWatts = 6000InfoMilliWattsPeak = 15000InfoMilliAmps = 500InfoMilliAmpsPeak = 1000

InfoAdapterExtPowerPresent = 1 ; 1=present, 2=absent

InfoPowerlossProtectDisabled = 2 ; 1=powerloss protection available butdisabled ; 2=any other powerloss protectioncondition

SNMP MIB Support

The following SNMP MIB fields are supported in Linux:

fusionIoDimmMibRevMajor fusionIoDimmInfoReducedWriteReason

fusionIoDimmMibRevMinor fusionIoDimmInfoMilliVolts

fusionIoDimmMibCondition fusionIoDimmInfoMilliVoltsPeak

fusionIoDimmInfoIndex fusionIoDimmInfoMilliVoltsMin

fusionIoDimmInfoStatus fusionIoDimmInfoMilliWatts

fusionIoDimmInfoName fusionIoDimmInfoMilliWattsPeak

fusionIoDimmInfoSerialNumber fusionIoDimmInfoMilliAmps

fusionIoDimmInfoPartNumber fusionIoDimmInfoMilliAmpsPeak

fusionIoDimmInfoSubVendorPartNumber fusionIoDimmInfoAdapterType

fusionIoDimmInfoSparePartNumber fusionIoDimmInfoAdapterPort

fusionIoDimmInfoAssemblyNumber fusionIoDimmInfoAdapterSerialNumber

fusionIoDimmInfoFirmwareVersion fusionIoDimmInfoAdapterExtPowerPresent

fusionIoDimmInfoDriverVersion fusionIoDimmInfoPowerlossProtectDisabled

fusionIoDimmInfoUID fusionIoDimmInfoInternalTempHigh

fusionIoDimmInfoState fusionIoDimmInfoAmbientTemp

fusionIoDimmInfoClientDeviceName fusionIoDimmExtnIndex


fusionIoDimmInfoBeacon fusionIoDimmExtnTotalPhysCapacityU

fusionIoDimmInfoPCIAddress fusionIoDimmExtnTotalPhysCapacityL

fusionIoDimmInfoPCIBandwidthCompatibility fusionIoDimmExtnUsablePhysCapacityU

fusionIoDimmInfoPCIDeviceID fusionIoDimmExtnUsablePhysCapacityL

fusionIoDimmInfoPCIPowerCompatibility fusionIoDimmExtnUsedPhysCapacityU

fusionIoDimmInfoPCISubdeviceID fusionIoDimmExtnUsedPhysCapacityL

fusionIoDimmInfoPCIVendorID fusionIoDimmExtnTotalLogCapacityU

fusionIoDimmInfoPCISubvendorID fusionIoDimmExtnTotalLogCapacityL

fusionIoDimmInfoPCISlot fusionIoDimmExtnAvailLogCapacityU

fusionIoDimmInfoWearoutIndicator fusionIoDimmExtnAvailLogCapacityL

fusionIoDimmInfoFlashbackIndicator fusionIoDimmExtnBytesReadU

fusionIoDimmInfoWritableIndicator fusionIoDimmExtnBytesReadL

fusionIoDimmInfoInternalTemp fusionIoDimmExtnBytesWrittenU

fusionIoDimmInfoHealthPercentage fusionIoDimmExtnBytesWrittenL

fusionIoDimmInfoMinimalModeReason fusionIoDimmExtnFormattedBlockSize


Appendix E- SMI-S Interface

Introduction to the SMI-S Interface

The SMI-S interface is based on Web-Based Enterprise Management (WBEM) and provides a Common InformationModel (CIM) model that represents the ioDrive and associated software, in accordance with existing DistributedManagement Task Force (DMTF), Storage Networking Industry Association (SNIA), and Storage ManagementInitiative Specification (SMI-S) standards. This model permits backward-compatible extension, accommodating newhardware and software features developed by Fusion-io.

It is assumed that the reader is versed in WBEM, SMI-S and DMTF standards. This document and associated modelmay change at any time as feedback is received.

References

CIM Schema v2.22http://www.dmtf.org/standards/cim/cim_schema_v2220

DMTF DSP1011, Physical Asset Profilehttp://www.dmtf.org/standards/published_documents/DSP1011_1.0.2.pdf

DMTF DSP1023, Software Inventory Profilehttp://www.dmtf.org/standards/published_documents/DSP1023_1.0.1.pdf

DMTF DSP1033, Profile Registration Profilehttp://www.dmtf.org/standards/published_documents/DSP1033_1.0.0.pdf

DMTF DSP1075 PCI Device Profilehttp://www.dmtf.org/standards/published_documents/DSP1075_1.0.0.pdf

DMTF DSP1002, Diagnostics Profilehttp://www.dmtf.org/standards/published_documents/DSP1002_2.0.0.pdf

SMI-S v1.4 Architecturehttp://www.snia.org/tech_activities/standards/curr_standards/smi/SMI-Sv1.4_Architecture.book.pdf

SMI-S v1.4 Common Profileshttp://www.snia.org/tech_activities/standards/curr_standards/smi/SMI-Sv1.4_CommonProfiles.book.pdf

SMI-S v1.4 Host Profileshttp://www.snia.org/tech_activities/standards/curr_standards/smi/SMI-Sv1.4_Host.book.pdf


1.

2.

3.

4.

5.

SMI-S v1.4 Common Diagnostic Modelhttp://www.dmtf.org/standards/mgmt/cdm/

Installing the SMI-S WMI Provider on Linux

The Fusion-io SMI-S provider implements a standard WBEM interface based on DMTF and SNIA standards forremote management of Fusion-io products including the ioDrive and ioDrive Duo. The provider is a CMPI-basedprovider and should work with popular CIMOMs including SFCB, OpenPegasus, and OpenWBEM. We also have aversion that supports WMI on Windows.

In order to use the provider, a CIMOM must be installed and configured. The provider and associated MOF files mustthen be installed and registered with the CIMOM. The MOF files define the CIM objects available from the SMI-Sprovider.

Initially, the provider has been tested with SFCB on Linux and WMI on Windows.

Install the SFCB CIM broker (CIMOM).On Debian-like:

$ sudo apt-get install sfcb sfcb-test wbemcli sblim-cmpi-basersync

Others: Install , , , ,sblim-sfcc sblim-sfcc-devel cim-schema-2.21.0 sblim-sfcb, and sblim-indication-helper sblim-cmpi-base sblim-testsuite

RPMs available for SLES, RHEL, and others on OpenSUSE Build Service.

Configure SFCB: Copy the file ( ) to sfcb.cfg /etc/sfcb

Install SMI-S provider: Install package from Fusion-io distribution and copy fio-smis to (or as appropriate)./usr/lib/fio/libfiosmis.so /usr/lib/sfcb /usr/lib64/sfcb

Register the SMI-S provider with SFCB:

cd /usr/share/fio/cim

sh /usr/share/sblim-cmpi-base/provider-register.sh -rfiosmis.registration cimv222-dmtf.mof

Restart SFCB:

$ /etc/init.d/sfcb restart


1.

2.

3.

Linux Testing

The utility can be used to test the SMI-S provider.wbemcli

Query the provider for the driver version and the firmware version for each IoDimm in the system:

$ wbemcli -nl ei http://localhost:5988/root/cimv2:FIO_SoftwareIdentity

The output should look something like this (values may change as development continues):

localhost:5988/root/cimv2:FIO_SoftwareIdentity.InstanceID="Fusion-iodrive driver"-InstanceID="Fusion-io drive driver"-TargetTypes=-OtherExtendedResourceTypeDescription=-MinExtendedResourceTypeRevisionNumber=. . .

Query the SMI-S provider for each ioDimm's health:

wbemcli -nl ei http://localhost:5988/root/cimv2:FIO_IoMemoryPort


localhost:5988/root/cimv2:FIO_IoMemoryPort.DeviceID="fct1",CreationClassN. .

Query capacity and usage counters of a specific ioDimm (in this case fct0):

$ wbemcli -nl gihttp://localhost:5988/root/cimv2:FIO_SSDStatistics.InstanceID="fct0"


localhost:5988/root/cimv2:FIO_SSDStatistics.InstanceID="fct0"-InstanceID="fct0"-WriteOperations=0-ReadOperations=6887-PhysicalMBytesWritten=1523769. . .


The Linux SMI-S provider can be tested remotely with the utility by replacing in the exampleswbemcli localhostabove with the hostname or IP address of the remote host. This method cannot be used to test the Windows SMI-Sprovider remotely, however, since (of course) Windows doesn't follow the emerging standard.

The SMI-S provider indications can be tested as well.

Description

SMI-S is a collection of specifications that traditionally focus on Storage Area Network (SAN) systems based on theSCSI command set, such as Fibre Channel, iSCSI, and SAS. However, the general pattern used to model these storagesystems can be applied to solid-state, direct-attached storage systems such as those provided by Fusion-io.

The Fusion-io ioDrive is modeled using the SMI-S patterns established in the Storage HBA, Direct Attached (DA)Ports, and Host Discovered Resources Profiles. The physical aspects of the ioDrive and all firmware and ioMemoryVSL software are modeled using published DMTF specifications, including the Physical Asset, Software Inventory,PCI Device Profiles, and Common Diagnostic Model Profile.

The following chart describes Fusion-io SMI-S CIM model, with the ioDrive and its associated firmware and software.For simplicity, the prefix FIO_ has been removed from the class names.


A: IOMemoryPort Class

The central instance of the model is of the class (A in the figure), a logical representation of theIOMemoryPortioDrive PCI adapter. It supports the extrinsic methods necessary to provision the drive. An instance of PCIDevice(B) and exist for each installed ioDrive, and they are associated with instances of IOMemoryPort

(1). An instance of (C), which contains important performance and capacityConcreteIdentity SSDStatisticsdata for the device, is associated by an association (2) to each .ElementStatisticalData IOMemoryPort

is scoped by an instance of the class. The (3) aggregationIOMemoryPort ComputerSystem SystemDeviceaggregates within the containing .IOMemoryPort ComputerSystem

E: IOMemoryPortController Class

An instance of (E) represents the ioMemory VSL used to control the installedIOMemoryPortControllerioDrives. specializes , and it aggregates withIOMemoryPortController CIM_PortController IoMemoryPortthe (4) aggregation. The driver version and vendor information are represented by the ControlledBy

(F) instance that is associated to (E) via SoftwareIdentity IOMemoryPortController (5). The that represents the installed ioMemory VSL softwareElementSoftwareIdentity SoftwareIdentity

is associated to the scoping using the association (6).ComputerSystem InstalledSoftwareIdentity

An instance of the class (G) represents both ends of the logical data path between the ProtocolEndpoint and the solid state storage. This aspect of the model is derived from the pattern in the DA PortsIOMemoryPort

Profile, where the port is both an initiator and target. is associated to the by ProtocolEndpoint IOMemoryPort (7) and to the by (8).DeviceSAPImplementation ComputerSystem HostedAccessPoint

H: LogicalSSD Class (Block Device)

The block device exposed to applications (file systems, database, and logical volume manager) is modeled using aninstance of (H), a subclass of . It is associated with a (J) using the LogicalSSD CIM_DiskDrive StorageExtent

association (9), but the will always be present. It is also associated to the MediaPresent StorageExtent (G) representing the using (10) and to theProtocolEndpoint IOMemoryPort SAPAvailableForElement

scoping using (3).ComputerSystem SystemDevice

The ioDrive, being a PCIe device, is also represented by an instance of the class (B). isPCIDevice IOMemoryPortan alternate representation of the and its associated control device. It is associated to it by the PCIDevice

association.ConcreteIdentity

K: SoftwareIdentity

The ioMemory VSL software is also represented with , which is associated to the SoftwareIdentity PCIDeviceby the association (11). The (firmware) is associated to theElementSoftwareIdentity SoftwareIdentityscoping by the association (12). An instance of ComputerSystem InstalledSoftwareIdentity

(L) is associated with each , which can be used to update deviceSoftwareInstallationService PCIDevicefirmware.


M: Physical Aspects

The physical aspects of the ioDrive are represented by an instance of the class (M), which isPhysicalPackageassociated to the by Realizes (13) and to the scoping by (14).PCIDevice ComputerSystem SystemPackagingThe temperature sensor on the ioDrive is represented by an instance of (N) and is associatedTemperatureSensorto the by .PhysicalPackage AssociatedSensor

Implementation

This section describes the arrangement of instances and associations for the Fusion-io device CIM model. Not all classproperties are described in detail. Consult the CIM schema for detailed description of all properties.

A WBEM CIM provider based on this model will be developed in the future. Fusion-io intends to support popularCIMOMs, including OpenPegasus, OpenWBEM, SFCB, and Windows WMI.

The drive health is indicated by the value of the property. Values include: Healthy, Warning, ReducedHealthLevelWrite, and Read Only. These values are mapped to values – OK, Degraded/Warning, andstandardHealthStateCritical Failure – as appropriate.

Extrinsic methods for drive provisioning include attach, detach, format, and update. The attach method creates a blockdevice for the drive. Detach disables the block device. A format option enables users to specify the device size in eithermegabytes or a percentage. The update method allows users to upgrade the firmware on the device.

Drive longevity is indicated by the value of the property. HealthPercentage FlashbackAvailabilityindicates whether or not this feature of the ioDrive is online.

IOMemoryPorts are aggregated by via the aggregation. Instances ofIOMemoryPortController ControlledBy are associated to their corresponding with the association. The IOMemoryPort PCIDevice ConcreteIdentity is a logical device of the scoping and is indicated as such by the IOMemoryPort ComputerSystem SystemDevice

aggregation.

The ioDrive Duo is a version of ioDrive with connectors for two ioMemory modules. Logically, an ioDrive Duo lookslike two separate ioDrives. The class is extended to include information about the carrier card type,IOMemoryPortserial number, and external power connection. This way, both the ioDrive and the ioDrive Duo are supported.

IOMemoryPort

One instance of exists for each ioDrive installed in the .IOMemoryPort ComputerSystem

The property reflects the state of the device indicator beacon (e.g., all LEDs on solid).LocationIndicatorReading the value gives the current state of the indicator. Writing the value with "On" or "Off" turns the indicator onor off and can be used to determine the device's physical location.


SSDStatistics

One instance of exists for each instance. Properties of this object provideSSDStatistics IOMemoryPortperformance and capacity information. Some of this information is only available when the drive is attached (i.e., thestate of the associated is "Attached").IOMemoryPort

IOMemoryPortController

Only one instance of exists, representing the ioMemory VSL software used to control IOMemoryPortContoller. The specializes the .IOMemoryPorts IOMemoryPortController CIM_PortController

IOMemoryPortController is aggregated to the scoping using the ComputerSystem SystemDeviceaggregation. is associated with a instance representing theIOMemoryPortController SoftwareInventoryioMemory VSL software properties via the association.ElementSoftwareIdentity

ProtocolEndpoint

One instance of exists for each instance of . It is associated to the ProtocolEndpoint IOMemoryPort using and to using .IOMemoryPort DeviceSAPImplementation LogicalSSD SAPAvailableForElement

Because an represents both the initiator and target ports, only one per IOMemoryPort ProtocolEndpoint is needed to model the connection between and .IOMemoryPort IOMemoryPort LogicalSSD

LogicalSSD

One instance of , a subclass of , exists for each block device ( ) exposed byLogicalSSD CIM_DiskDrive /dev/fioXa Fusion-io drive. Correlatable IDs are used, based on operating system device names. This enables client applicationsto associate block devices discovered through this model with resources discovered from other SMI-S modelsinstrumented on the host system.

ComputerSystem aggregates via . The instances are associated to their LogicalSSDs SystemDevice LogicalSSD via . If the associated to the endpoint is notProtocolEndpoints SAPAvailableForElement IOMemoryPort

attached, then the Availability property is set to "Off Line," and the DeviceID property value is "Unknown."

StorageExtent

One instance of is associated with each and represents the logical storage of theStorageExtent LogicalSSDassociated device.

SoftwareIdentity

One instance of exists to represent the ioMemory VSL software. The firmware is also modeledSoftwareIdentityusing but requires an instance for each ioDrive installed. The property has a valueSoftwareIdentity IsEntityof True, indicating that the instance corresponds to a discrete copy of the ioMemory VSLSoftwareIdentitysoftware or firmware. The , , , and propertiesMajorVersion MinorVersion RevisionNumber BuildNumberconvey the driver/firmware version information. The property can be used to identify Fusion-io.Manufacturer

Another option for the firmware is to omit the association with InstalledSoftwareIdentity


, because the firmware is not really installed on . This option would depend onComputerSystem ComputerSystemhow users want to model the firmware.

SoftwareInstallationService

An instance of exists for each and can be used to update theSoftwareInstallationService PCIDeviceassociated device's firmware.

PCIDevice

An instance of is instantiated for each Fusion-io drive (PCIe card) in the computer. Properties are set asPCIDevicefollows:

BusNumber – bus number where the PCIe device exists

DeviceNumber – device number assigned to the PCI device for this bus.

FunctionNumber – set to the function number for the PCI device.

SubsystemID, , , , and are optional but canSubsystemVendorID PCIDeviceID VendorID RevisionIDbe populated if values can be extracted from the configuration registers of the PCI device.

PCIDevice is associated with , its alternate logical representation, using . The IOMemoryPort ConcreteIdentity is also associated with , representing the physical aspects of the ioDrive, via Realizes.PCIDevice PhysicalPackage

PhysicalPackage

One instance of exists for each discrete, physical ioDrive installed in the computer system. The PhysicalPackage, , , , Version, and PartNumber properties can be used to describe theseManufacturer Model SKU SerialNumber

aspects of the physical card. is associated with PCIDevice via Realizes and the scoping PhysicalPackage via .ComputerSystem SystemPackaging

TemperatureSensor

One instance of exists for each . Temperature information for the driveTemperatureSensor PhysicalPackageis stored in the properties of this object.

Diagnostic Test

One instance of will exist. The method will trigger a snapshot of deviceDiagnosticTest RunDiagnostic()status for the specified which must be an instance of . The diagnostic run isManagedElement IoMemoryPortsynchronous and runs instantaneously. The resulting object will associate to the originating ConcreteJob

instance and the respective instance that was specified (see Figure 2). At thisDiagnosticTest IoMemoryPorttime, can only be used with the default provided.RunDiagnostic() DiagnosticSettingData

Each run will add a single entry of and associated DiagnosticSettingDataRecord in the . The property of the DiagnosticCompletionRecord DiagnosticLog RecordData will record critical device status at the time of the run. The format of the DiagnosticCompletionRecord

string can be found in the property.RecordData RecordFormat


The format is a series of status strings, each of which can hold one of the following values delimited by an asterisk (*)character: "Unknown", "OK", "Warning", or "Error". Currently, seven status values are recorded: ,WearoutStatus

, , , , and WritabilityStatus FlashbackStatus TemperatureStatus MinimalModeStatus PciStatus. All of these should report "OK" under normal operating conditions.InternalErrorStatus

WearoutStatus will be set to "Warning" when less than 10% reserve space is left on the device. It will be set to "Error"when there is no more reserved space.

WritabilityStatus will be set to "Error" whenever the device is write throttling or in read-only mode.This can happen due to a variety of conditions including device wearout and insufficient power.

FlashbackStatus will report "Warning" if a catastrophic error causes Flashback protection to be degraded.

TemperatureStatus will report "Warning" when the device temperature is nearing the maximum safetemperature and "Error" when the maximum safe temperature is reached or surpassed.

MinimalModeStatus will report either "Warning" or "Error" whenever the device is in minimal mode.

PciStatus will report "Warning" or "Error" if there are compatibility problems with the host PCIe bus.

InternalErrorStatus will report "Error" if there are any internal problems with the ioMemory VSL.

The property will summarize the results and may be set to Unknown, OK, Warning or Failed. IfCompletionStateany status is in error the state will report as Failed. Otherwise, if there is any warning status the state will reportWarning. The Message property will be set to indicate the appropriate action if there are any warnings or errors.

DiagnosticSetting Data

There will be an instance of associated with the instance (see FigureDiagnosticSettingData DiagnosticTest2). It records the default settings for each call to .RunDiagnostic

DiagnosticServiceCapabilities

There is an instance of associated with the instanceDiagnosticServiceCapabilities DiagnosticTestwhich records the capabilities of the service.DiagnosticTest

DiagnosticLog

An instance of is associated with the instance and will store the results of eachDiagnosticLog DiagnosticTestrun.

DiagnosticSettingRecord

A copy of the default will be stored in a each timeDiagnosticSettingData DiagnosticSettingDataRecorda diagnostic is run and will be associated with an instance of .DiagnosticCompletionRecord


DiagnosticCompletionRecord

An instance of will store the results of each execution. TheDiagnosticCompletionRecord RunDiagnosticdetails are explained in .DiagnosticTest

RegisteredDiskDriveLiteProfile

Only one instance of this class is needed. It resides in the namespace and indicates the/root/interopimplementation of the Disk Drive Lite Profile. The following properties are set as follows:

InstanceID – set to " "SNIA:DiskDriveLiteProfile-1.4.0

RegisteredOrganization – set to " " (SNIA)11

RegisteredName – set to " "DirectAccess Ports Profile

RegisteredVersion – set to " "1.4.0

RegisteredDAPortsProfile

Only one instance of this class is needed. It resides in the namespace and indicates the/root/interopimplementation of the DA Ports Profile. The properties are set as follows:

InstanceID – set to " "SNIA:DAPortsProfile-1.4.0


RegisteredName – set to " "DirectAccess Ports Profile


RegisteredStorageHBAProfile

Only one instance of this class is needed. It resides in the namespace and indicates the/root/interopimplementation of the Storage HBA Profile. The properties are set as follows:

InstanceID – set to " "SNIA:StorageHBAProfile-1.4.0


RegisteredName – set to " "Storage HBA Profile


RegisteredHostDiscoveredResourcesProfile

Only one instance of this class is needed. It resides in the namespace and indicates the/root/interopimplementation of the Host Discovered Resources Profile. The properties are set as follows:

InstanceID – set to " "SNIA:HostDiscoveredResourcesProfile-1.2.0



RegisteredName – set to " "Host Discovered Resources Profile


RegisteredPCIDeviceProfile

Only one instance of this class is needed. It resides in the namespace and indicates the/root/interopimplementation of the PCI Device Profile. The properties are set as follows:

InstanceID – set to " "DMTF:DSP1075-PCIDevice-1.0.0a

RegisteredOrganization – set to " " (DMTF)2

RegisteredName – set to " "PCIDevice Profile

RegisteredVersion – set to " "1.0.0a

RegisteredSoftwareInventoryProfile

Only one instance of this class is needed. It resides in the namespace and indicates the/root/interopimplementation of the Software Inventory Profile. The properties are set as follows:

InstanceID – set to " "DMTF:DSP1023-SoftwareInventory-1.0.1

RegisteredOrganization – set to "{[2}}" (DMTF)

RegisteredName – set to " "Software Inventory Profile


RegisteredSoftwareUpdateProfile

Only one instance of this class is needed. It resides in the namespace and indicates the/root/interopimplementation of the Software Update Profile. The properties are set as follows:

InstanceID – set to " "DMTF:DSP1023-SoftwareUpdate-1.0.0


RegisteredName – set to " "Software Update Profile


RegisteredPhysicalAssetProfile

Only one instance of this class is needed. It resides in the namespace and indicates the/root/interopimplementation of the Physical Asset Profile. The properties are set as follows:

InstanceID – set to " "DMTF:PhysicalAssetProfile-1.0.2



RegisteredName – set to " "PhysicalAsset Profile


RegisteredSensorsProfile

Only one instance of this class is needed. It resides in the namespace and indicates the/root/interopimplementation of the Sensors Profile. The properties are set as follows:

InstanceID – set to " "SNIA:SensorsProfile-1.0.0


RegisteredName – set to " "Sensors Profile


RegisteredCommonDiagnosticProfile

Only one instance of this class is needed. It will reside in the namespace and indicate the/root/interopimplementation of the Common Diagnostic Model Profile. The property will be set to a value of "InstanceID

". The DMTF:DiagnosticsProfile-2.0.0a RegisteredOrganizatio}}n property will be set to" (DMTF). The property will be set to a value of "Diagnostics Profile". The a value of "{{2 RegisteredName

property will be set to a value of " ".RegisteredVersion 2.0.0a

Indications

An indication will be generated periodically when a serious condition exists for a particular ioDrive device. TheWBEM provider currently supports six types of indications. They alert users of the SMI-S provider to conditions suchas imminent wearout, degradation of writability, degradation of the flashback feature, higher temperature, and internalerror states.

The indications will be instances of the class which simply specializes the FIO_AlertIndication class.CIM_AlertIndication

The values for the properties of the instances are under development and may change asFIO_AlertIndicationtesting proceeds and feedback is received.


FIO_AlertIndication

Property Value

IndicationIdentifier See below for each type

IndicationTime Timestamp when sent

AlertingManagedElement IoMemoryPort.DeviceID=<device ID>

AlertingElementFormat CIMObjectPath (2)

AlertType Device Alert (5)

PerceivedSeverity See below for each type

ProbableCause See below for each type

SystemCreationClassName "FIO_AlertIndication"

SystemName <hostname>

ProviderName "fiosmis"

CorrelatedIndications Not used

Description Class description

OtherAlertType Not used

OtherSeverity Not used

ProbableCauseDescription Not used

EventID Same as IndicationIdentifier

OwningEntity <vendor>

MessageID TBD

Message TBD

MessageArguments TBD

Reduced Writability Indication

The ioDrive ioMemory VSL can dramatically reduce write throughput to manage device conditions such as excessivewear, high temperature, and insufficient power. The reduced writability indication is generated while the drive is in thismode. If the triggering condition is excessive wear, the health percentage will report 0% health.IoMemoryPort

Property Value

IndicationIdentifier <mfr>":"<hostname>":write"

PerceivedSeverity Degraded/Warning (3)


ProbableCause Threshold Crossed (52) Temperature Unacceptable (51) Power Problem (36)

Read-only Indication

When the drive has reached the end-of-life, it can no longer be written to and can only be read from. The read-onlyindication will be sent when this occurs. The health percentage will continue to report 0% healthIoMemoryPortwhen this happens.

Property Value

IndicationIdentifier <mfr>":"<hostname>":read_only"


ProbableCause Threshold Crossed (52)

Wearout Indication

As the drive wears out, this indication is generated as a warning when the drive health percentage drops below 10%,before write throughput is reduced.

Property Value

IndicationIdentifier <mfr>":"<hostname>":wearout"


ProbableCause Threshold Crossed (52)

Flashback Indication

If a catastrophic part failure degrades the effectiveness of the flashback feature, this indication will be sent.

Property Value

IndicationIdentifier <mfr>":"<hostname>":flashback"


ProbableCause Loss of Redundancy (88)

High Temperature Indication

This indication will be sent when the temperature of the card becomes excessive.

Property Value

IndicationIdentifier <mfr>":"<hostname>":temperature"

PerceivedSeverity Critical (6)


ProbableCause Temperature Unacceptable (51)

Error Indication

If the ioMemory VSL is in an error state the error indication will be sent.

Property Value

IndicationIdentifier <mfr>":"<hostname>":error"

PerceivedSeverity Major (6)

ProbableCause Other (1)


Appendix F- Documentation Permissions

The and the file, which ship in binary form with the driver, contain content that have theAVR bootloader tree.hfollowing documentation copyright requirements:

AVR Bootloader

Copyright © 2002, 2003, 2004, 2005, 2006, 2007 Eric B. Weddington

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the followingdisclaimer.

Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.

Neither the name of the copyright holders nor the names of contributors may be used to endorse or promoteproducts derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FORANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSSOF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

tree.h

Copyright 2002 Niels Provos <[email protected]>All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the


1.

2.

following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the followingdisclaimer.

Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENTSHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISINGIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OFSUCH DAMAGE.

ioDrive Hardware User Guide - 2.3.1 | D0002881_006_1 | _______________ ___ ___75

Fusion Powered Support

We offer ioDrive Customer Support by phone, e-mail and on the Web.

Telephone Support

For customer support phone numbers, please refer to the Fujitsu Technology Solutions service desk athttp://ts.fujitsu.com/support/servicedesk.html.

E-Mail

Please use the contact form at http://ts.fujitsu.com/support/contact/contact.html.

Web

Go online to download the latest ioDrive guides, driver and support packages athttp://ts.fujitsu.com/support/downloads.html.Select your PRIMERGY server and operating system to find all supported drivers.

iodrive product family - fujitsu technology...

Documents