HP SimpliVity OmniCube CN-1400, SimpliVity OmniCube CN-2400, SimpliVity OmniCube CN-3400, SimpliVity OmniCube CN-5400 Installation And Maintenance Manual

Hewlett Packard

Enterprise

SimpliVity OmniCube CN-1400, CN-2400,
CN-3400, and CN-5400 Series Hardware
Installation and Maintenance Guide

Part number: 760-000249 Rev A
Published: June 2017

Trademarks

Patents

SimpliVity®,

®

, SimpliVity cube logo®, SimpliVity The Data Virtualization Company®,
OmniCube®, OmniStack®, Global Federated Architecture®, Data Virtualization Platform™, SVT™, and
RapidDR™ are trademarks or registered trademarks of SimpliVity® Corporation in the United States and
certain other countries.

All other trademarks are the property of their respective owners.

SimpliVity OmniCube® and OmniStack® products are covered by various United States and foreign
patents and pending patent applications.

Patents include:

AU 2010265954; BR PI1013789-0; CA 2,776,231; CN ZL201080033630.9; DE 2433226; DK 2433226;
EP 2433226; ES 2433226; FI 2433226; FR 2433226; GB 2433226; IN 679/CHENP/2012; IT 2433226; JP
5695040; NO 2433226; SE 2433226; US 8,478,799; US 9,367,551; US 2016/0283498; EP 12738334.7;
HK 14110213.4; US 2013/0024615; AU 2012273295; BR 112013032706-5; CA 2,840,178; CN

201280036259.0; EP 12732895.3; HK 14110215.2; IN 368/CHENP/2014; JP 6059216; US 9,436,748;
US 2016-0371354; AU 2013222325; BR 112014020806-9; CA 2,865,240; CN 201380017261.8; EP

13710149.9; HK 15100889.7; IN 6929/CHENP/2014; JP 5902323; US 9,032,183; US 2015/0242315;
AU 2014308938; BR 112016003205-5; CA 2,921,039; CN 201480045910.X; EP 14759406.3;
IN 201647008897; JP 2016-536408; US 9,043,576; US 2015-0254256; AU 2016206826; BR
112016028144-6; CA WO2016/115219; CN WO2016/115219; EP 16703395.0; IN 201647041955; JP
WO2016/115219; US 2016/0202927; US 15/280,347

Copyright

Information in this document is subject to change without notification. Reproduction in any manner
whatsoever without the written permission of SimpliVity Corporation is strictly forbidden.

© SimpliVity Corporation 2017

Customer support

To contact SimpliVity Customer Support, visit https://support.simplivity.com. When contacting a
representative, you need to know the serial number of your OmniStack server to verify your service
subscription.

SimpliVity uses OmniWatch to automatically monitor the health of your OmniStack equipment and have it
send us notifications of any alerts or errors.

2

Contents

Chapter 1: Hardware overview...............................................................5

Hardware components.................................................................................................................. 5

Environmental and technical specifications................................................................................ 14

About hardware upgrades...........................................................................................................16

About firmware revisions.............................................................................................................16

Chapter 2: Install the server hardware............................................... 17

About electrostatic discharge...................................................................................................... 17

Unpack the shipping carton........................................................................................................ 17

Install the server enclosure in a rack......................................................................................... 20

Mount the enclosure in the rails................................................................................................. 21

Connect the network cables....................................................................................................... 22

Connect the power cables.......................................................................................................... 23

Organize the cables.................................................................................................................... 24

Power on the system.................................................................................................................. 25

Attach the OmniCube bezel........................................................................................................25

About the front panel components................................................................................... 10

About the back panel components................................................................................... 11

Enclosure size and weights.............................................................................................. 14

Power and thermal............................................................................................................14

Temperature and humidity................................................................................................ 14

Vibration and shock.......................................................................................................... 15

Altitude and airborne contaminants.................................................................................. 15

Agency compliance standards..........................................................................................15

Shipping carton contents.................................................................................................. 18

Hardware not supplied in the shipping carton..................................................................19

Detach the OmniCube bezel............................................................................................ 27

Chapter 3: Configure the IPMI port for remote management........... 28

Connect to IPMI and launch the Virtual Console....................................................................... 29

IPMI configuration requirements................................................................................................. 30

Chapter 4: About OmniCube CN-2400-E and CN-5400-E drive

encryption............................................................................................31

Access the PERC BIOS Configuration Utility............................................................................. 32

Check drive security in the BIOS................................................................................................32

Check drive security in the IPMI web interface.......................................................................... 34

3

Create a Security Key.................................................................................................................34

Secure disk groups with a Security Key..................................................................................... 35

Delete disk groups...................................................................................................................... 36

Change the passphrase for a Security Key................................................................................38

Delete a Security Key................................................................................................................. 39

Erase a drive that supports encryption.......................................................................................40

Chapter 5: Server troubleshooting......................................................43

About diagnostic indicators......................................................................................................... 43

About drive monitoring................................................................................................................ 44

About front drive numbering............................................................................................. 46

About power supply monitoring...................................................................................................48

Accelerator card monitoring........................................................................................................ 48

Accelerator card not detected........................................................................................... 49

Revert an Accelerator card to its backup firmware.......................................................... 50

About network interface monitoring............................................................................................ 50

Chapter 6: Drive maintenance............................................................. 52

Drive maintenance guidelines..................................................................................................... 52

Remove a drive........................................................................................................................... 53

Remove a secured drive.............................................................................................................54

Install a drive............................................................................................................................... 55

Install and secure a drive........................................................................................................... 56

Chapter 7: Power supply maintenance...............................................57

Power supply maintenance guidelines........................................................................................57

Remove a power supply............................................................................................................. 57

Install a power supply................................................................................................................. 58

Chapter 8: Network cabling options................................................... 60

About the 10GbE-only network configuration............................................................................. 60

About the direct-connected network configuration......................................................................61

About the switch-connected network configuration.....................................................................62

Appendix A: Additional information....................................................63

SimpliVity documentation conventions........................................................................................ 63

SimpliVity terminology................................................................................................................. 64

Websites...................................................................................................................................... 65

Regulatory information................................................................................................................ 65

Documentation feedback.............................................................................................................66

4

Chapter 1: Hardware overview

This section contains the following topics:

• Hardware components

• Environmental and technical specifications

• About hardware upgrades

• About firmware revisions

The foundation of the SimpliVity architecture is two or more high-performance and highly-available OmniCube
servers. An OmniCube server provides computing, storage, networking, and other resources to the virtual
machines (VM) in the Federation.

After installing the hardware in a rack and connecting power and network cables, you can deploy each OmniCube
server into a SimpliVity Federation. As your capacity and performance needs increase, you can add more
OmniCube servers for easy, on-demand scalability, with no disruption to users.

Hardware components

Each OmniCube model provides different hardware configurations for storage, compute, and memory.

Table 1: Hardware components by hybrid model (hybrid models may contain both HDD and
SSD physical drives)

Component CN-1400

CPU

Front SSD
Drives

Model Intel Xeon

E5-2600 V3 or
V4 series

CPU Count 1 1 or 2 1 or 2 1 or 2

CPU Core
Count

Speed in GHz 2.3GHz or

Wattage 145W or less 145W or less 145W or less 145W or less

Quantity 2 2 4 4

Capacity 400GB 400GB 400GB 800GB

6 or 8 8 or greater 8 or greater 8 or greater

greater

CN-2400 and
CN-2400-E

CN-2400:
Intel Xeon
E5-2600 V3 or
V4 series

CN-2400-E:
V4 series

2.3GHz or
greater

CN-3400

Intel Xeon
E5-2600 V3 or
V4 series

2.3GHz or
greater

CN-5400 and
CN-5400-E

Intel Xeon
E5-2600 V3 or
V4 series

2.3GHz or
greater

Interface SATA SAS SAS SAS

Hardware components 5

Component CN-1400

CN-2400 and
CN-2400-E

CN-3400

CN-5400 and
CN-5400-E

Front HDD
Drives

Dimension 2.5" (2.5"

carrier)

2.5" (2.5"
carrier)

2.5" (2.5"
carrier)

2.5" (2.5"
carrier)

RAID Type RAID1 RAID1 RAID5 RAID5

Self­Encrypting

No CN-2400-E

only

No CN-5400-E

only

Drives

Quantity 4 8 20 20

Capacity 1TB CN-2400 1TB

1TB 1.2TB
(V3), 1.2TB
(V4)

CN-2400-E:

1.2TB (V4)

Interface SAS SAS SAS SAS

Dimension 2.5" (2.5"

carrier)

2.5" (2.5"
carrier)

2.5" (2.5"

carrier)

2.5" (2.5"
carrier)

RAID Type RAID5 RAID6 RAID60 RAID60

Rear HDD
Drives

RPM 7,200 CN-2400:

7,200 10,000
7,200 (V3),
10,000 (V4)

CN-2400-E:
10,000 (V4)

Self­Encrypting

No CN-2400-E

only

No CN-5400-E

only

Drives

Quantity 2 2 2 2

Capacity 300GB 300GB 300GB 300GB

Interface SAS SAS SAS SAS

Dimension 2.5" 2.5" 2.5" 2.5"

RAID Type RAID1 RAID1 RAID1 RAID1

RPM 10,000 10,000 10,000 10,000

6 Hardware components

Component CN-1400

CN-2400 and
CN-2400-E

CN-3400

CN-5400 and
CN-5400-E

Effective
Storage
Capacity

Memory
Size and
Frequency

Total storage
capacity for
user data.
Omits storage
reserved by
SimpliVity.

2.34TB CN-2400:

4.79TB (V3),

5.7TB (V4)

CN-2400-E:

5.7TB (V4)

12.86TB 15.46TB

Single CPU • 128GB;4x32GB RDIMM @ 2133MHz or 2400MHz

• 192GB;4x32GB + 4x16GB RDIMM @ 2133MHz or
2400MHz

• 256GB;8x32GB RDIMM @ 2133MHz or 2400MHz

• 384GB;12x32GB RDIMM @ 1866MHz or 2133MHz

Contact your SimpliVity sales representative to learn about
memory sizes greater than 384GB.

Dual CPU N/A • 256GB;8x32GB RDIMM @ 2133MHz or

2400MHz

• 384GB;8x16GB + 8x32GB RDIMM @
2133MHz or 2400MHz

• 512GB;16x32GB RDIMM @ 2133MHz or
2400MHz

Power Supply
Units

Interfaces

Deduplication
and
Compression

Hot
swappable,
integrated
fans

Embedded 2 x 10GbE SFP+ and 2 x 1GbENetwork

VM Network
(optional)

Accelerator

• 768GB;24x32GB RDIMM @ 1866MHz or
2133MHz

Contact your SimpliVity sales representative to
learn about memory sizes greater than 768GB.

2 x 750W 2 x 1100W

Not applicable for single CPUs

2 x 10GbE or 2 x 1GbE

Contact your SimpliVity sales representative to learn about the
vendor-specific interface cards currently supported for your
platform.

Hardware components 7

Component CN-1400

CN-2400 and
CN-2400-E

CN-3400

CN-5400 and
CN-5400-E

Remote
System

IPMI processor and network port for remote, out-of-band, web-based
management.

Management

Table 2: Hardware components by All Flash model (All Flash models contain SSD physical
drives only)

Component

CPU

Model Intel Xeon E5-2600 V4 series

CN-2400-F, CN-3400-F, CN-5400-F

CPU Count 1 or 2

CPU Core

8 or greater

Count

Speed in GHz 2.3GHz or greater

Wattage 145W or less

Front SSD
Drives

Quantity CN-2400-F: 5

CN-3400-F: 10

Rear SSD
Drives

CN-5400-F: 14

Capacity 1.6TB

Interface SATA

Dimension 2.5" (2.5" carrier)

RAID Type CN-2400-F: RAID5

CN-3400-F: RAID6

CN-5400-F: RAID6

Self-

No
Encrypting
Drives

Quantity 2

Capacity 480GB

Dimension 2.5"

RAID Type RAID1

8 Hardware components

Component

CN-2400-F, CN-3400-F, CN-5400-F

Effective
Storage
Capacity

Memory
Size and
Frequency

Total storage
capacity for
user data.
Omits storage

CN-2400-F: 4.4TB

CN-3400-F: 9.3TB

CN-5400-F: 14.4TB
reserved by
SimpliVity.

Single CPU • 128GB;4x32GB RDIMM @ 2133MHz or 2400MHz

• 192GB;4x32GB + 4x16GB RDIMM @ 2133MHz or 2400MHz

• 256GB;8x32GB RDIMM @ 2133MHz or 2400MHz

• 384GB;12x32GB RDIMM @ 1866MHz or 2133MHz

Contact your SimpliVity sales representative to learn about

memory sizes greater than 384GB.

Dual CPU • 256GB;8x32GB RDIMM @ 2133MHz or 2400MHz

• 384GB;8x16GB + 8x32GB RDIMM @ 2133MHz or 2400MHz

• 512GB;16x32GB RDIMM @ 2133MHz or 2400MHz

• 768GB;24x32GB RDIMM @ 1866MHz or 2133MHz

Contact your SimpliVity sales representative to learn about

memory sizes greater than 768GB.

Power Supply
Units

Interfaces

Deduplication
and
Compression

Remote
System
Management

Hot

2 x 1100W
swappable,
integrated
fans

Embedded 2 x 10GbE SFP+ and 2 x 1GbENetwork

VM Network
(optional)

Not applicable for single CPUs

2 x 10GbE or 2 x 1GbE

Contact your SimpliVity sales representative to learn about the

vendor-specific interface cards currently supported for your

platform.

Accelerator

IPMI processor and network port for remote, out-of-band, web-based
management.

Hardware components 9

About the front panel components

The front panel of each OmniCube server provides system controls, diagnostic indicators, USB and video
ports, and contains a different number of solid state drives (SSD) and hard disk drives (HDD).

Figure 1: OmniCube CN-3400 and CN-5400 front panel

Table 3: Front panel component descriptions

Callout Component Description

1 Power button Controls power to the system and indicates whether

there is power to the system. If the indicator is green,
the system is receiving power.

2 Diagnostic indicators Shows hardware error conditions.

3 System identification

button

4 Retention latches Locks the enclosure in the rack. You can push a latch

System identification button and system identification
connector.

The system identification button helps you locate
a system within a rack. If you push the system
identification button on the back panel or the front
panel, the system identification buttons on the front
panel and the back panel flash blue. Push a system
identification button a second time to stop it from
flashing.

The system identification connector, located to the
right of the system identification button, connects the
optional system status indicator assembly through the
optional cable management arm.

to release the enclosure and slide it out.

10 Hardware components

Callout Component Description

5 Storage 2.5" drives, numbered 0 to 23, left to right, with power

(right) and activity (left) LED indicators.

The system models contain different drive
configurations:

• CN-1400: Contains 6 drives. Drives 0 and 1 are
SSDs and drives 3 to 5 are HDDs. Drives 6 to 23
are empty.

• CN-2400 and CN-2400-E: Contains 10 drives.
Drives 0 and 1 are SSDs and drives 2 to 9 are
HDDs. Drives 10 to 23 are empty.

• CN-3400, CN-5400 and CN-5400-E: Contains 24
drives. Drives 0 to 3 are SSDs and drives 4 to 23
are HDDs.

• CN-2400-F: Contains 5 drives. Drives 0 to 4 are
SSDs. Drives 5 to 23 are empty.

• CN-3400-F: Contains 10 drives. Drives 0 to 9 are
SSDs. Drives 10 to 23 are empty.

• CN-5400-F: Contains 14 drives. Drives 0 to 13 are
SSDs. Drives 14 to 23 are empty.

6 Video input Enables you to connect a monitor as part of a

7 USB connector USB 2.0-compliant connector. Enables you to connect

8 Service tag Provides identification information that you can use

About the back panel components

The back panel of an OmniCube server contains the Accelerator, network ports, rear boot drives, and the
power supplies.

If you pull the enclosure from the rack, the disk
numbering scheme appears on a label attached to the
top of the enclosure.

keyboard, video, and mouse (KVM) setup, for local
administration.

a USB device, such as a keyboard, as part of a KVM
for local administration.

when contacting Customer Support.

Hardware components 11

Figure 2: Back panel of an OmniCube server with a single CPU

Figure 3: Back panel of an OmniCube server with two CPUs

Table 4: Back panel component descriptions

Callout Component Description

1 Riser 1 Contains PCIe slots 1-3. You can install optional

2x10GbE or 2x1GbE network cards in these slots, as
shown in slot 2, used by guest VMs only.

A system with a single CPU does not contain riser 1. A
plate is installed in place of riser 1.

2 Accelerator Installed in PCIe slot 5 of riser 2, but also occupies

3 RAID controller RAID Controller for the rear boot drives installed in

12 Hardware components

slot 4. The card has two LEDs that continuously glow
green to indicate normal operation.

PCIe slot 6 of riser 3. The RAID Controller for the front
data disks is a mezzanine card.

Callout Component Description

4 System identification

button

System identification button and system identification
connector.

The system identification button helps you locate
a system within a rack. If you push the system
identification button on the back panel or the front
panel, the system identification buttons on the front
panel and the back panel flash blue. Push a system
identification button a second time to stop it from
flashing.

The system identification connector, located to the
right of the system identification button, connects the
optional system status indicator assembly through the
optional cable management arm.

5 IPMI port Dedicated IPMI port for remote, out-of-band, web-

based management.

6 Serial port Serial port that you can use to connect a serial device.

7 Video connector Video connector that enables you to connect a monitor

or keyboard, video, monitor (KVM) device.

8 USB connectors Two USB 3.0 compliant ports for connecting USB

devices to the system.

9 10GbE ports Two 10GbE network interfaces, numbered 1 and

2. Each 10GbE interface has link (top) and activity

(bottom) round LEDs. These interfaces are dedicated
to SimpliVity Storage and Federation networks.

10 1GbE ports Two 1GbE network interfaces, numbered 3 and 4,

from left to right. Each 1GbE interface has link (left)
and activity (right) square LEDs. These interfaces are
dedicated to the Management network and, optionally,
VM traffic.

11 Power supplies Two redundant, 750W or 1100W power supplies

with fans, numbered 1 and 2, from left to right. Each
power supply has a status indicator light in the handle.
Disconnect the power cords before removing a power
supply. Wattage depends on the CPU requirements
(number of cores).

12 Boot drives Two hot-swappable 2.5" hard drives. Reserved

for system use and are not available for user data
storage.

Hardware components 13

Environmental and technical specifications

There are specific environmental and technical specifications for each hardare platform. The
specifications help you when planning the appropriate installation location, environmental conditions, and
resources, such as power and cooling.

Enclosure size and weights

OmniCube servers have specific size dimensions and weights. This information helps you when planning
to install the enclosure in a rack.

Dimension Centimeters Inches

Enclosure width 48.2 17.5

Maximum height 8.73 3.44

Maximum depth (from rack
flange)

The maximum weight of a system with all storage drives installed is 30.4 kg, or 67.02 lbs.

Power and thermal

OmniCube servers have two redundant power supplies with specific power and thermal specifications.

Table 5: OmniCube Power and Thermal Specifications

Specification Description

Current consumption 10A-5A

Supply voltage 100–240V AC (autoranging). Make sure each

Frequency 50/60Hz

Heat dissipation 4100 BTU/hr max

Maximum inrush current 55A

75.58 29.75

power source has sufficient electrical overload
protection.

Energy efficiency Energy Star, spec version 1.0

Power supply efficiency 90-96% efficient (load dependent)

Temperature and humidity

OmniCube servers have limits for temperature and humidity under operating and storage conditions.

14 Environmental and technical specifications

Specification Description

Humidity and
Temperature
(continuous operation)

Temperature (storage) -40°C to 65°C (-40°F to 149°F) with a maximum temperature gradation

Vibration and shock

OmniCube servers have limits for vibration and shock under operating and storage conditions.

Specification Description

Vibration
(operating)

Vibration
(storage)

Shock
(operating)

Shock
(storage)

10°C to 35°C (50°F to 95°F) at 10% to 80% relative humidity with 26°C
(78.8°F) maximum dew point (maximum wet bulb temperature). De-rate
maximum allowable dry bulb temperature at 1°C per 300m above 950m
(1°F per 547 ft above 3117 ft).

of 20°C per hour.

0.26Grms at 5-350Hz in all orientations.

1.88Grms at 10-500Hz for 15 minutes (all six sides tested).

Six consecutively executed shock pulses in the positive and negative x, y, and z
axes of 40 G for up to 2.3 ms.

Six consecutively executed shock pulses in the positive and negative x, y, and z
axes (one pulse on each side of the system) of 71 G for up to 2 ms.

Altitude and airborne contaminants

OmniCube servers have limits for altitude and airborne contaminants under operating and storage
conditions.

Specification Description

Altitude (operating) -15.2m to 3048m (–50 ft to 10,000 ft)

Altitude (storage) -15.2m to 12,000m (–50 ft to 39,370 ft)

Contaminant level (operating) Class G1 or lower as defined by ISA-

Agency compliance standards

OmniCube servers meet agency compliance standards.

An OmniCube host complies with the following standards:

• CNS14436-1, CNS13438

• UL 60950-1, 2nd Edition, 2011-12-19; CSA C22.2 No. 60950-1-07, 2nd Edition

• EK1-ITB 2000:2014

• EMC EMCA41269-EM i EMCA41269-IM od 14.07.2014

S71.04-1985

Environmental and technical specifications 15

• EMC EN 55022:2010/CISPR 22:2010 EN 55024:2010/CISPR 24:2010 EN 61000-3-2:2006 +A1:2009

• +A2:2009/IEC 61000-3-2:2005 +A1:2008 +A2:2009 (Class D) EN 61000-3-3:2008/IEC 61000-3-3:2008

• SAFETY EN 60950-1:2006 +A1:2010 +A2:2013 +A11:2009 +A12:2011/IEC 60950-1:2005 ed2
+A1:2009 EN 62311:2008

• RoHS EN 50581:2012

• IEC 60950-1/A2:2013

• PTI-1406324-000 od 09.07.2014

• US CFR Title 47, FCC Part 2, 15 ANSI C63.4 2009 Canadian ICES-3(A)/NMB-3(A), Issue 5

• SM SR EN 60950-1:2010/A1:2012,GOST 30805.22:2002

• GB17625. 1-2012;GB4943. 1-2011;GB9254-2008 (CLASS A)

• ZEK 01.4-08

About hardware upgrades

If you need to upgrade the server hardware components, contact Customer Support.

WARNING:

Never install additional options other than those approved for installation by Customer
Support. Doing so will void your warranty and might cause serious server instability and

potential data loss.

About firmware revisions

The OmniStack software requires that each supported platform is running a specific firmware revision.

To avoid compatibility issues, contact Customer Support before making any firmware changes.

NOTE:

If your server, or any management software, has automatic software updates enabled, disable
this feature to avoid installing unsupported firmware revisions.

16 About hardware upgrades

Chapter 2: Install the server hardware

This section contains the following topics:

• About electrostatic discharge

• Unpack the shipping carton

• Install the server enclosure in a rack

• Mount the enclosure in the rails

• Connect the network cables

• Connect the power cables

• Organize the cables

• Power on the system

• Attach the OmniCube bezel

To install the server hardware, you must unpack all hardware components, install the enclosure in a rack, connect
the power and network cables, and power on the server.

About electrostatic discharge

You must protect sensitive hardware from electrostatic discharge (ESD), which can damage electronic
components.

To protect hardware from ESD:

• Ensure the server hardware is fully grounded at all times to prevent damage from electrostatic
discharge.

• When not installed in a rack, store server hardware in its original packaging or place on a sturdy
surface that is protected from electrostatic discharge.

• When handling server hardware components, always use the electrostatic wrist strap provided or a
similar form of ESD protection.

Unpack the shipping carton

You unpack the shipping carton to prepare the system hardware components for installation.

Before you begin

• The OmniCube servers are heavy. You must have at least one other person to help you lift and unpack
the carton, and SimpliVity recommends the use of a datacenter equipment lift.

• You have cut the pallet shipping straps, which might have considerable tension, using an appropriate
tool and safety wear.

Procedure

1. Remove the shrink wrap from the palleted cartons and carefully cut any straps that hold the cartons to

the pallet.

2. To orient the carton for ease of unpacking and racking, locate the black circle printed on the side of the
carton. This is the front of the system enclosure.

About electrostatic discharge 17

3. Use a boxcutter to cut the sealing tape. Be careful that you do not cut into the carton. Retain the carton

and packaging in case you need to return the system.

4. Remove the rail kit (callout 1), which contains the rails and the installation instructions.

Figure 4: OmniCube Shipping Carton Contents

5. Remove the cable management arm (CMA) kit, (callout 2) which contains the CMA assembly, a

signal LED extension cable, and the installation instructions. Do not open this box until the end of the
installation procedure, when you are ready to organize the system cables.

6. Remove the accessory pack (callout 3), which contains:

• SimpliVity bezel.

• Power and network cables.

• Software and documentation flash drive.

• Quick Start posters and international Product Information Guide.

7. If you are not ready to install the system in a rack, keep it in the shipping box or place it on a sturdy
surface that is protected from electrostatic discharge.

Shipping carton contents

The shipping carton contains standard items and other items based on your configuration.

18 Unpack the shipping carton

Part Description

Server enclosure Provides processing power and storage

capacity.

Bezel Protects the SSD and HDD drives in the front

panel.

Power cords (locale specific) • Two standard power cords.

• Two rack power distribution unit (PDU)
cords.

Sliding rail kit Contains the left and the right rails, two hook

and loop straps, and detailed installation
documentation.

Cable Management Arm (CMA) kit (optional) Contains the CMA assembly and installation

documentation.

Printed documentation • Hardware Installation Quick Start

• Configuration and Deployment Quick Start

• Product Information Guide (safety and

regulatory notices)

• End User License Agreement

Hardware not supplied in the shipping carton

Your network environment might require additional hardware components not supplied in the shipping
carton.

Hardware Description Application

Rack 19 inch (48.3 cm), four-post,

toolless rack.

1 GbE data cables Two Category 5E or Category 6

cables with RJ45 connectors.

An optional third cable is required
to use the IPMI port for remote
console access.

10 GbE data cables 2SFP+ Direct Attach active

cables.

Provides easy access to
the server hardware in your
computing environment.

Connects the 1 GbE network
interfaces on each server to a
1 GbE switch. This is required
only if you are connecting the 1
GbE network interfaces on each
server to a switch, such as in
a direct connected or switch­connected network configuration,
for example.

Connects the 10 GbE interfaces
on one server to a 10 GbE
switch.

Unpack the shipping carton 19

Hardware Description Application

Redundant network switches Required number of switches. Connects devices to a network.

The number of switches depends
on your network configuration.

Redundant Uninterruptible Power
Supply (UPS)

Rack requirements

Each server ships with a sliding rail kit. The sliding rails allow you to fully extend the enclosure out of the
rack for service.

Caution:

See the Rack Installation Instructions supplied with the rail kit for safety and installation
instructions.

The racks you use for each server must meet these requirements:

• The sliding rails support tool-free mounting in 19-inch, EIA-310-E compliant square-hole, 4-post racks,
and also support tooled mounting in threaded 4-post racks.

• Each enclosure is 2U. Ensure the rack has sufficient space for all enclosures.

• For full power redundancy across all servers, you need a rack with two power distribution units (PDU)
feeding separate outlet strips, with sufficient vacant outlets on each strip.

• Ensure the rack is installed and stabilized or bayed according to the manufacturer's instructions.

WARNING:

When servicing an enclosure in a rack, extend only one enclosure at a time to prevent the
rack from tipping.

Required number of UPS
devices.

Provides temporary power to the
server in the event of a complete
power outage.

Rack installation guidelines

There are guidelines to help you successfully install each server in a rack.

• Follow all safety guidelines stated in the documentation that came with the rack, particularly when
installing components into the locations at the top of the rack.

• Ensure the rack meets the requirements.

• Install the servers in the same rack when possible.

• Install the servers in a rack starting from the bottom of the rack.

• Always install the servers in a horizontal position, or you void your warranty and support contract.

Install the server enclosure in a rack

You install the rails, which are included in the shipping carton, at the lowest available U space in the rack
enclosure. You then work up from the bottom of the rack to add additional rails.

Before you begin

• You have read the safety instructions in the Product Information Guide supplied with your system.

20 Install the server enclosure in a rack

• For first time installers, you have read the instructions included in the rail kit. The rail kit instructions
also explain stabilizing the rack, installing devices, and power distribution.

• You have identified the rack location for the right rail. The system requires 2U of rack space.

Caution:

Two people are required to safely install the system hardware in a rack. The Rack Installation
instructions included in the rail kit box contain important safety and procedural information.

Procedure

1. Pull apart the front and rear rail brackets, lengthening the rails to the correct distance for your rack.

2. Align the top of the rail brackets with the U space markers on the front and rear rack columns (callouts

1 and 2).

Figure 5: Rail kit installation

3. Firmly push the brackets onto the rack columns so that the blue latches (callout 4) engage and lock.

4. Make sure that both the front and rear bracket latches are closed and the rails are secure.

5. Repeat Step 1 through Step 4 for the left rail.

NOTE:

The blue bracket latches will not close properly if the front and rear rail brackets are not level.
Make sure that both rails are level, and that they occupy the same U location in the rack.

Next steps

You can now mount the system enclosure in the rails.

Mount the enclosure in the rails

It takes two people to install each system into the rails, one person on either side, each holding the
system enclosure at the front and rear.

Before you begin

Mount the enclosure in the rails 21

You have read all supplied rack and safety information. This is important if you are installing the enclosure
into the upper U locations of tall racks, where you need to use steps or platforms.

Procedure

1. Extend each rail from the rack until it locks into place (callout A).

Figure 6: Enclosure installation

2. Identify the location of the four lugs (callout B) on each side of the enclosure, and the corresponding J-

slots in the rails.

3. Hold the enclosure over the rails, aligning the lugs with the J-slots.

4. Starting at the back two lugs, gently rotate the enclosure down (callout C), engaging the lugs in the J-

slots.

5. Ensure all eight lugs on the enclosure are seated firmly in the J-slots in the rails and that the lug lock
(callout D) engages.

6. Press the rail lock button (callout A) and slide the enclosure into the rack (callout E).

7. Ensure the enclosure retention lock (callout F) closes completely.

Next steps

You can now connect the power cables to the OmniCube servers.

Connect the network cables

An OmniCube host includes four network interfaces, located on the back panel of the system enclosure,
which are required for the Federation networks. These interfaces are labeled 1 to 4, from left to right.
Network interfaces 1 and 2 are 10GbE and network interfaces 3 and 4 are 1GbE.

Procedure overview

Read the following information before performing the procedure.

22 Connect the network cables

For information about the ports required by SimpliVity servers, see the SimpliVity OmniStack Host
Deployment Guide.

Figure 7: OmniCube host network ports

The other networking interfaces are:

• A separate 1GbE IPMI network interface that you can use for the initial system setup and remote out­of-band management.

• An optional 1GbE or 10GbE network interface for guest VM use.

Procedure

1. Obtain the network cables needed for the network configuration.

2. Connect the cables according to the guidelines for the SimpliVity networks only.

3. Ensure that no other network interfaces, such as optional 10GbE interfaces, are connected to

your network before deploying the system to a Federation. You can connect these interfaces after
deployment.

NOTE:

If the optional interfaces are connected when you deploy the system, the ports for the
Federation network might not be configured correctly. For help with resolving this error,
contact Customer Support.

Next steps

You can now, optionally, use the Cable Management Arm (CMA) to organize the cables.

Connect the power cables

An OmniCube server includes two, hot-swappable, 750W or 1100W power supplies, labeled 1 and 2, from
left to right. You connect both power supplies to power sources.

Procedure overview

For high availability, you can connect each power supply to a different circuit. In addition, SimpliVity
recommends that you use redundant uninterruptible power supply (UPS) systems to protect against a
complete power outage.

Procedure

1. Obtain the two power cables from the shipping carton.

2. Use the power cables to connect each power supply to a source of power, preferably on different

circuits.

Connect the power cables 23

Figure 8: Connect the power cables

3. Use the cable strain relief (hook and loop fastener) on each power supply to secure the power cable

and prevent an accidental disconnection.

Figure 9: Securing the power cables

Next steps

You can now connect the network cables.

Organize the cables

Procedure overview

If you do not want to use the cable management arm (CMA), use the two hook and loop straps provided in
the rail kit to organize the power and network cables.

NOTE:

Make sure you have sufficient slack in the cables to fully extend the enclosure from the rack until
the rails are safely locked in the extended position.

Procedure

1. Insert the outer CMA brackets on the interior sides of both rack flanges.

24 Organize the cables

2. Gather the cables on each side of the enclosure into bundles.

3. Thread the hook and loop straps through the tooled slots on the outer CMA brackets on each side of

the enclosure and secure the cable bundles.

For more information, see the Cable Management Arm Installation Instructions supplied in the cable
management kit.

Power on the system

Press the power button on the front panel of each OmniCube server to apply power to the device.

Procedure

1. Go to the front panel of the system.

2. Press the power button to power-on the system.

3. Check that the health indicator on the front panel changes from flashing amber to steady blue within

approximately 4 minutes.

4. Check that the two LEDs on the Accelerator card at the rear of the system are steady green.

Attach the OmniCube bezel

You attach the OmniCube bezel to the front panel of the system to physically secure the front drives,
ensure proper airflow, and to prevent accidental removal of drives.

Procedure overview

Note the following information before performing the procedure.

NOTE:

To avoid damaging the bezel decals, be sure to remove the bezel from the open end of its
protective wrap rather than the taped end.

Procedure

1. Identify the front panel mounting lugs on the right side of the system.

Power on the system 25

Figure 10: OmniCube Bezel Lugs

2. Insert the bezel tabs into the front panel mounting lugs.

Figure 11: OmniCube Bezel Tabs

3. Rotate the left side of the bezel inward toward the front panel and push firmly until you hear the latch

click and engage.

26 Attach the OmniCube bezel

Detach the OmniCube bezel

You can detach the OmniCube bezel from the front panel of the system to gain access to the front drives.

Procedure

1. Hold the blue cube handle to detach the bezel and push up on the release latch.

Figure 12: OmniCube Bezel Latch

2. Rotate the left side of the bezel outward from the front panel and pull to the left, to simultaneously

disengage the tabs on the right side of the bezel.

Attach the OmniCube bezel 27

Chapter 3: Configure the IPMI port for remote
management

This section contains the following topics:

• Connect to IPMI and launch the Virtual Console

• IPMI configuration requirements

You configure the integrated Intelligent Platform Management Interface ( IPMI) port to access the IPMI console
through a web browser. The IPMI console provides out-of-band remote system management and access to
advanced management options.

Before you begin

Your environment meets the requirements for configuring IPMI. See IPMI configuration requirements on page

30.

Procedure overview

This procedure assumes you are using a computer with Microsoft Windows. If you prefer to configure IPMI at a
later time, you can skip this task and proceed with deploying an OmniCube host using Deployment Manager. See
the SimpliVity OmniStack for vSphere Deployment Guide.

Procedure

1. Connect an Ethernet cable from the Ethernet port on the laptop to the IPMI Ethernet port on the rear of the

OmniCube server.

2. If necessary, change the IPv4 address of the Ethernet port on your laptop:

a) Open Network and Sharing Center and select the Ethernet port connection. This is typically Local Area

Connection.

b) Click Properties > Internet Protocol Version 4 (TCP/IPv4).

c) Record the current settings so that you can restore them later.

d) Check the button labeled Use the following IP address.

e) Enter an IP address in the range 192.168.0.[0-255], excluding 192.168.0.120.

f) Enter a subnet mask of 255.255.255.0.

g) Close the dialogs and exit from Network and Sharing Center.

3. Point your browser to the IPMI default IP address: http://192.168.0.120

4. 4. Use the default user name root and the default password calvin to log in.

5. You can optionally change the default IPMI password if prompted to do so, according to your sitespecific

security requirements.

6. Click iDRAC Settings > Network in the left panel.

7. Check the box for Enable IPv4.

8. Do one of the following:

• Check the box for Enable DHCP.

28

• Assign a static IP address, gateway, subnet mask and [optional] DNS servers, if used.

9. Verify the VLAN settings at the bottom of the screen comply with your network settings. If you are not using
VLANs, this must be unchecked.

10. Click Apply.

11. Click Logout to exit IPMI.

12. Remove the Ethernet cable from the IPMI port in the OmniCube server and replace it with a cable that is
connected to a rack switch. This switch must be in the network that you specified in Step 8 on page 28.

13. Reset the IPv4 properties for your laptop, reversing the changes that you made in Step 2 on page 28.

Next steps

You can now connect to IPMI from any remote location. See Connect to IPMI and launch the Virtual Console
on page 29.

Connect to IPMI and launch the Virtual Console

You connect to the Intelligent Platform Management Interface (IPMI) web GUI to launch the Virtual
Console, which you use to access advanced system options.

Before you begin

You have configured the IPMI port. See Configure the IPMI port for remote management on page

28.

NOTE:

You can use the Virtual Console to power-cycle the OmniCube host and access System Setup.
From System BIOS > System Security, you can enter a new setup password, to prevent
unwanted system access, and save the password to a secure location. Contact Customer

Support before changing any BIOS settings.

Tip:

The Virtual Console is compatible with different browsers and versions of Java. If you see errors
while launching or using the Virtual Console, you might need to try a different browser or Java
version.

Procedure

1. Log in to any computer in the same network as your IPMI.

2. Type the IPMI IP address into your browser. For example: http://110.150.0.12.

3. Log in with the default user name root and the default password calvin.

NOTE:

Enter the new password if you changed the default when configuring IPMI.

4. Select Server > Virtual Console.

Connect to IPMI and launch the Virtual Console 29

IPMI configuration requirements

You require certain items and information to properly configure the Intelligent Platform Management
Interface (IPMI) port for out-of-band remote system management over the web.

• IPMI uses the DNS Remote Access Controller (RAC) name to identify an OmniCube host. The default
DNS RAC name is the system serial number, as shown on the pullout tab in the front panel. You
can change the DNS RAC name to specify a rack location, your own asset number, or any other
identifiable reference, but the name must be unique.

• If you use DHCP to assign an IP address instead of using a static IP, SimpliVity recommends that you
check the option Register RAC on DNS and use the DNS RAC to reference the OmniCube host. This
prevents problems if the DHCP lease is renewed and a different IP address is assigned to the IPMI
port.

• You have ensured that the ports required for network communication are open.

• You have the following information and items:

◦ An IP address. The address can be static or assigned by DHCP.

◦ A static address for the gateway, subnet mask, and, optionally, up to two DNS servers, which can

be static or assigned by DHCP.

• An Ethernet cable to connect to the rack-mounted switch that can reach your network (as specified in
the preceding network address requirements).

• The default address of 192.168.0.120 to access the IPMI software and reconfigure its network settings.

• A laptop computer with a Web browser.

◦ You might need to temporarily change the IP address used by the laptop's physical Ethernet port.

◦ You might need to temporarily disconnect the laptop from wireless networks.

30 IPMI configuration requirements

Chapter 4: About OmniCube CN-2400-E and
CN-5400-E drive encryption

This section contains the following topics:

• Access the PERC BIOS Configuration Utility

• Check drive security in the BIOS

• Check drive security in the IPMI web interface

• Create a Security Key

• Secure disk groups with a Security Key

• Delete disk groups

• Change the passphrase for a Security Key

• Delete a Security Key

• Erase a drive that supports encryption

You can use Data At Rest Encryption to secure the data on the front SSD and HDD drives in the event that these
drives are lost or stolen. The drive encryption uses Local Key Management (LKM) to prevent unauthorized access
to the data on the physical disks. You create a Security Key with a passphrase on the RAID controller and then
specify the disk groups and virtual disks that you want to secure on the drives. You manage Security Keys on a
per system basis. There is no central key management for all secured systems.

If a secured drive is physically removed from the system (Data at Rest) and then inserted into a different system,
its data is inaccessible without the passphrase used to secure it. You typically create a unique passphrase for
each RAID controller on which you create a Security Key.

The front drives, which are controlled by the H730P Mini Adapter RAID controller, store user data and data for the
OmniStack software. You cannot encrypt the rear boot drives, which are controlled by the PERC H330 Mini RAID
controller. Since the rear boot drives do not contain user data, you do not need to encrypt them.

You use the PERC BIOS Configuration Utility to manage Security Keys on the PERC H730P RAID controller,
including:

Verify if drives are secured You can use the IPMI web interface or the PERC BIOS Configuration Utility

to confirm whether physical and virtual disks are currently secured with a
Security Key. If disks are secured, you do not need to create a key. You must
configure the IPMI port before you can access the IPMI web interface or the
Virtual Console, which you use to access the BIOS.

Create a Security Key You create a Security Key on the RAID controller to encrypt its physical disks

and disk groups.

Secure the disk groups After creating a Security Key, you then secure the disk groups, which also

secures the virtual disks, on the controller.

Delete disk groups You can delete the disk groups, which also deletes the virtual disks, on the

controller. You are required to delete all secured virtual disks before you can
erase a drive.

31

Caution:

When you delete a disk group all of its data on the underlying
physical disks is lost.

Change a Security Key You can change the passphrase for a Security Key. Changing the passphrase

requires that you enter the current passphrase.

Delete a Security Key Deleting a Security Key involves deleting the secured disk groups and their

virtual disks, which erases all data on the disks, and then deleting the Security
Key from the controller. You specify the passphrase when deleting the key.

Erase a drive that supports
encryption

You can erase a drive to permanently delete all of its data and security
attributes, such as a lost or forgotten passphrase. You cannot erase a drive
that contains secured virtual drives.

Access the PERC BIOS Configuration Utility

Before you begin

You have completed these tasks:

• Backed up all virtual machines on the OmniCube host. The system is in a safe state so that you can
restart it and load the BIOS to access the BIOS Configuration Utility.

• Configured the IPMI port for accessing the IPMI web interface, which you use to launch the Virtual
Console. You access the BIOS through the Virtual Console. See Configure the IPMI port for remote

management on page 28.

Procedure

1. Reboot the system.

2. Watch the boot-up messages for the PERC BIOS Configuration Utility.

3. Press Control+R when you see the prompt to display the PERC BIOS Configuration Utility.

Check drive security in the BIOS

32 Access the PERC BIOS Configuration Utility

Before you begin

You have displayed the PERC BIOS Configuration Utlity on the computer connected to the OmniCube
host. See Access the PERC BIOS Configuration Utility on page 32.

Procedure overview

If you do not want to reboot the system, you can check drive security in the IPMI web interface. See

Check drive security in the IPMI web interface on page 34.

Procedure

1. Select the PERC H730P Mini controller and press Enter. The Virtual Disk Management screen

appears for the selected controller.

2. For virtual disks:

a) Select Disk Group: 0, RAID 1 for the CN-2400-E or Disk Group: 0, RAID 5 for the CN-5400-E and

review the Secured field to the right. "Yes" indicates that the virtual disk is secure.

b) Select Disk Group: 0, RAID 6 for the CN-2400-E or Disk Group: 0, RAID 60 for the CN-5400-E

and review the Secured field to the right.

c) If the secured field is "No," it means the disk group is not secured. Follow the steps in Secure disk

groups with a Security Key on page 35 to secure the disk.

3. For physical disks:

a) Press Control+N to display the Physical Disk Management screen.

b) Select a disk and review the Secured field to the right. "Yes" indicates that the disk is secure. The

Encryption Capable field indicates whether the disk supports encryption.

c) If the secured field is "No," it means the disk group is not secured. Follow the steps in Secure disk

groups with a Security Key on page 35 to secure the disk.

Check drive security in the BIOS 33

Check drive security in the IPMI web interface

Before you begin

You have configured the IPMI port. See Configure the IPMI port for remote management on page 28.

Procedure

1. Select Storage > Physical Disks and review the Security Status column.

2. Select Storage > Virtual Disks and review the Secured column.

Create a Security Key

Before you begin

You have displayed the PERC BIOS Configuration Utlity on the computer connected to the OmniCube
host. See Access the PERC BIOS Configuration Utility on page 32.

Procedure

1. Select the PERC H730P Mini controller on the Virtual Disk Management screen.

2. Press F2.

3. Select Security Key Management > Create Key.

34 Check drive security in the IPMI web interface

4. Type a Security Key identifier in the Identifier field. The identifider is only a label for the Security Key.

5. Type a passphrase in the Passphrase field.

6. Record the passphrase in a secure location in case you need to recover it.

Caution:

You are required to specify the current passphrase when changing the passphrase or
when replacing the RAID controller. If you lose the passphrase, you must erase the disk
groups, which destroys all data on the underlying disks, and create a new Security Key.

7. Select OK to create the key and then select Yes to confirm.

Next steps

You can now secure the disk groups on the RAID controller. See Secure disk groups with a Security
Key on page 35.

Secure disk groups with a Security Key

Before you begin

You have completed these tasks:

• Created a Security Key for the RAID controller that is connected to the disk groups. See Create a
Security Key on page 34.

• Displayed the PERC BIOS Configuration Utility on the computer connected to the OmniCube host. See
Access the PERC BIOS Configuration Utility on page 32.

• Ensured that the virtual disks are configured on the PERC H730P Mini RAID controller.

Procedure overview

The PERC H730P Mini RAID controller in an OmniCube CN-2400-E or a CN-5400-E system contains two
disk groups: The RAID1 (CN-2400-E) or RAID5 (CN-5400-E) disk group is on the SSD drives, which are
reserved for SimpliVity, and the RAID6 (CN-2400-E) or RAID60 (CN-5400-E) disk group is on the HDD
drives, which store user data.

Secure disk groups with a Security Key 35

Procedure

1. Use the arrow keys to select the RAID 1 (CN-2400-E) or RAID 5 (CN-5400-E) disk group under the
PERC H730P Mini controller.

2. Press F2.

3. Select Secure Disk Group and then select Yes to confirm.

4. Select the RAID 6 (CN-2400-E) or RAID 60 (CN-5400-E) disk group.

5. Press F2.

6. Select Secure Disk Group and then select Yes to confirm.

Results

Both disk groups and all virtual disks inside them are now secured with the Security Key.

Delete disk groups

Before you begin

36 Delete disk groups

You have completed these tasks:

• Migrated all virtual machines (VM) off of the OmniCube host.

• Displayed the PERC BIOS Configuration Utlity on the computer connected to the OmniCube host. See

Access the PERC BIOS Configuration Utility on page 32.

Procedure overview

The PERC H730P Mini RAID controller in an OmniCube CN-2400-E or a CN-5400-E system contains two
disk groups: The RAID1 (CN-2400-E) or RAID5 (CN-5400-E) disk group is on the SSD drives, which are
reserved for SimpliVity, and the RAID6 (CN-2400-E) or RAID60 (CN-5400-E) disk group is on the HDD
drives, which store user data.

You delete a disk group to delete all of its virtual disks. You can also delete individual viritual disks from a
disk group.

Caution:

When you delete a disk group all data on the underlying physical disks is lost.

Procedure

1. Use the arrow keys to select the PERC H730P Mini controller.

2. Select the PERC H730P Mini controller on the Virtual Disk Management screen.

3. Select one of the disk groups.

4. Press F2 and select Delete Disk Group.

Delete disk groups 37

5. Press Enter and select Yes to confirm.

6. Select the other disk group and repeat Step 4 on page 37 and Step 5 on page 38 to delete it.

The disk groups and their virtual disks are deleted.

Change the passphrase for a Security Key

Before you begin

You have completed these tasks:

• Created a Security Key for the RAID controller on which you want to change the passphrase. See
Create a Security Key on page 34.

• Obtained the passphrase for the current Security Key.

• Displayed the PERC BIOS Configuration Utlity on the computer connected to the OmniCube host. See

Access the PERC BIOS Configuration Utility on page 32.

Procedure

1. Select the PERC H730P Mini controller on the Virtual Disk Management screen.

2. Press F2.

3. Select Security Key Management > Change Key.

38 Change the passphrase for a Security Key

4. Select Yes to confirm that you want to change the Security Key for the selected controller.

5. Type a new passphrase and then type the old passphrase.

6. Record the new passphrase in a secure location in case you need to recover it.

7. Select OK.

8. Select Yes to confirm.

Delete a Security Key

Before you begin

You have completed these tasks:

• Migrated all virtual machines (VM) off of the OmniCube host.

• Displayed the PERC BIOS Configuration Utlity on the computer connected to the OmniCube host. See

Access the PERC BIOS Configuration Utility on page 32.

Procedure

1. Use the arrow keys to select the PERC H730P Mini controller.

2. Select the PERC H730P Mini controller on the Virtual Disk Management screen.

Delete a Security Key 39

3. Select one of the disk groups.

4. Press F2 and select Delete Disk Group.

5. Press Enter and select Yes to confirm.

6. Select the other disk group and repeat Step 4 on page 40 and Step 5 on page 40 to delete it.

7. Select the PERC H730P Mini controller.

8. Press F2 and select Delete Key.

9. Select Yes to confirm deleting the key.

The key is deleted and the disks are now erased.

Erase a drive that supports encryption

Before you begin

You have completed these tasks:

40 Erase a drive that supports encryption

• Displayed the PERC BIOS Configuration Utlity on the computer connected to the OmniCube host. See
Access the PERC BIOS Configuration Utility on page 32.

• Confirmed that the drive you want to erase does not contain secured virtual disks. See Check drive
security in the BIOS on page 32.

• Deleted all secured disk groups and virtual disks on the drive you want to erase. See Delete disk

groups on page 36.

Procedure overview

You erase a secured drive to permanently remove all security attributes from the drive, including a lost
or forgotten passphrase. For example, if you replace a drive and the replacement drive is secured with a
passphrase for a Security Key on a different controller, the new RAID controller cannot access or secure
the drive. You must erase the replacement drive to remove the security attributes and then secure it using
the key from the current RAID controller.

Caution:

When you erase a drive all of its data is lost.

Procedure

1. Select the PERC H730P Mini controller on the Virtual Disk Management screen.

2. Press Control+N to display the Physical Disks.

3. Select the drive to be erased.

4. Press F2 and select Instant Secure Erase.

Erase a drive that supports encryption 41

5. Press Enter and select Yes to confirm.

The drive is erased and its security attributes are deleted.

42 Erase a drive that supports encryption

Chapter 5: Server troubleshooting

This section contains the following topics:

• About diagnostic indicators

• About drive monitoring

• About power supply monitoring

• Accelerator card monitoring

• About network interface monitoring

You can use the diagnostic indicators and LEDs to identify problems with the server hardware. For assistance
with resolving hardware problems, such as a component failing, contact Customer Support.

About diagnostic indicators

The left side of the front panel displays diagnostic indicators that glow when the system is functioning
properly and when a hardware-related error occurs. The indicators can help you correct problems before
they affect service levels.

Figure 13: Diagnostic indicator LEDs

Table 6: Diagnostic indicator descriptions

Callout Description

1 Health indicator. If no errors exist, the indicator is steady blue. The health

indicator flashes amber during startup or if a system component, such as a fan
or disk, fails.

2 Temperature indicator. The indicator flashes amber if the system experiences a

thermal error. For example, a temperature is out of range or fan fails.

3 Memory indicator. The indicator flashes amber if a memory error occurs.

About diagnostic indicators 43

Callout Description

4 Drive indicator. The indicator flashes amber if a drive fails. Green indicates

normal operation.

5 Electrical indicator. The indicator flashes amber if the system experiences an

electrical error. For example, voltage is out of range or a power supply or voltage
regulator fails.

6 PCIe indicator. The indicator flashes amber if a PCIe card experiences an error

About drive monitoring

The LEDs on the front of each drive indicate when there is a problem, such as a failed or failing drive. If
a drive fails or is failing, contact Customer Support to obtain a replacement drive of the same type, size,
and speed.

The drives in the front panel store user and Federation data and are protected by RAID, which provides
different protection for each model:

• A CN-2200, CN-2400, or CN-2400-E model can tolerate up to two hard disk drive (HDD) failures and
one solid state drive (SSD) failure simultaneously without data loss.

• A CN-2400-F, containing all flash drives can tolerate a single solid state drive (SSD) failure without
data loss.

• A CN-3400-F, containing all flash drives can tolerate up to two solid state drive (SSD) failures
simultaneously without data loss.

• A CN-3400, CN-5400 or CN-5400-E can tolerate up to 4 HDD failures and one solid state drive (SSD)
failure simultaneously without data loss. Of the four HDDs, two of the drives must be in one drive set
and the other two drives must be in a different drive set.

• A CN-5400-F, containing all flash drives can tolerate up to 2 solid state drive (SSD) failures
simultaneously without data loss.

44 About drive monitoring

Figure 14: Disk drive LEDs

Each hard drive carrier has two LEDs that indicate the state of the physical disk. The green activity LED
(callout 1) flashes whenever the drive is accessed. The bicolor (green/amber) LED (callout 2) provides
drive status information as detailed below.

Table 7: Drive status LED

LED Pattern Drive Status Description

Flashes green two times per second Identifying the drive or preparing the

drive for removal.

Off Drive ready for removal, or all drives

are initializing. The drive status LED
remains off while the drives are
initializing after the system is turned on.
Do not remove a drive during this time.

Flashes green, amber, and off Predicted drive failure.

Flashes amber four times per second Drive failed.

Flashes green every 2 seconds Drive is rebuilding.

Steady green Drive is online.

About drive monitoring 45

LED Pattern Drive Status Description

Table 8: Drive activity LEDs

LED Pattern Drive Activity Description

Flashes green three seconds, amber
three seconds, and off six seconds

Off Not lit—No disk activity.

Flashing or steady green Read/Write (I/O) activity is occurring.

About front drive numbering

The front drives are numbered for identification purposes.

Rebuild aborted.

Figure 15: CN-1400 drive numbering

The drives are numbered 0 to 23. Drives 0 to 1 are SSDs and drives 2 to 5 are HDDs.

Figure 16: CN-2400 drive numbering

The drives are numbered 0 to 23. Drives 0 and 1 are SSDs and drives 2 to 9 are HDDs. Drives 10 to 23
are empty.

46 About drive monitoring

Figure 17: CN-3400 and CN-5400 drive numbering

The drives are numbered 0 to 23. Drives 0 to 3 are SSDs and drives 4 to 23 are HDDs.

Figure 18: CN-2400-F drive numbering

The drives are numbered 0 to 23. Drives 0 to 4 are SSDs and drives 5 to 23 are empty.

Figure 19: CN-3400-F drive numbering

The drives are numbered 0 to 23. Drives 0 to 9 are SSDs and drives 10 to 23 are empty.

Figure 20: CN-5400-F drive numbering

The drives are numbered 0 to 23. Drives 0 to 13 are SSDs and drives 14 to 23 are empty.

About drive monitoring 47

About power supply monitoring

The LEDs on the front of each power supply indicate when there is a problem, such as a failed or failing
power supply. If a power supply fails, contact Customer Support for a replacement of the same type and
wattage.

Figure 21: Power supply LED

In the image above, the green arrow shows the power supply handle. Each power supply has an
illuminated translucent handle that indicates whether power is present or whether a power fault has
occurred.

Table 9: Power supply LED States

LED State

Off: Indicates no power present.

Steady green: Indicates the power supply is connected to a power
source, is operational, and is supplying power to the system.

Flashing yellow: Indicates a problem with the power supply.

Flashing green: When performing a hot swap of a power supply, with the
system powered on, this LED indicates that the newly-installed power
supply is not compatible with the installed power supply.

Accelerator card monitoring

The LEDs on an Accelerator card indicate when there is a problem with the card. If an Accelerator card
fails, contact Customer Support to have it replaced.

Figure 22: Accelerator card LEDs

An Accelerator card has two LEDs:

48 About power supply monitoring

• LED 1 glows or flashes green or yellow.

• LED 2 glows or flashes green or red.

Table 10: Accelerator card LED states

Server state LED 1 LED 2 Description

Power up

POST

Off Off

Off Steady red

Off Flashing red (1

on, 1 off)

Off Steady green

Off Flashing red

(2 on, 2 off)

Flashing yellow

Steady yellow

Steady green

Steady red

PCIe 12 V power is not present.

Configuration Programmable Logic
Device (CPLD) detected power failure
or CPLD is not configured.

Field Programmable Gate Array
(FPGA) configuration error detected
or configuration failed.

FPGA configuration is complete.

Firmware is not responding to health
check.

Power-on self test (POST) is
executing.

POST failed.

Steady green Steady green

State save

Steady yellow

State restore

Flashing yellow

Upgrade

Flashing green Flashing green

HostCtrl

Flashing yellow

Accelerator card not detected

If the server is unable to detect or communicate with an Accelerator card after you power on the server or
perform a server firmware upgrade, you see error conditions.

Flashing green

Flashing green

Flashing red

Normal operation (passed POST).

NVRAM state save is in progress.

NVRAM state restore is in progress.

Firmware upgrade is in progress.

Not in service. Contact Customer
Support for a replacement.

Accelerator card monitoring 49

Table 11: Accelerator card error conditions

LED number Initial state Error state (Host Ctrl)

After power on After software upgrade1

Off

Steady green Off

2

Off

A firmware load error on the Accelerator card might have caused the problem. You can try to correct this
problem:

1. Shut down the server.

2. Wait three minutes for the server to fully shutdown.

3. Restart the server.

This prompts the Accelerator card to revert to its backup firmware.

Steady yellow Flashing yellow

Revert an Accelerator card to its backup firmware

Procedure overview

A firmware load failure on the Accelerator card can prevent the card from communicating with the
OmniStack server. You can try to correct this problem by reverting to the backup firmware. Shutting down
the server, waiting 3 minutes for the server to fully shutdown, and then restarting the server, prompts the
Accelerator card to fail and use its backup firmware. If both LEDs on the Accelerator card are not glowing
steady green or the server fails to return to normal operation, contact Customer Support.

Procedure

1. In your hypervisor management interface, locate the OmniCube host or OmniStack host with the

problem Accelerator card.

2. Shut down and power off the server as explained in the SimpliVity OmniStack Administrator Guide.

3. Wait three minutes until both LEDs have stopped glowing, which indicates that the capacitors on the

Accelerator card have fully discharged.

4. Power on the server.

5. Wait for the server to fully boot.

6. Verify that both LEDs on the Accelerator card are glowing steady green.

7. Verify that there are no error conditions reported for the host in the hypervisor management interface.

About network interface monitoring

The LEDs on the network interface cards (NIC) indicate when there is a problem with the NIC or one of its
ports. If a network interface fails, contact Customer Support to have it replaced.

50 About network interface monitoring

Figure 23: Network interface LEDs

The image above displays the following interfaces:

• Network interfaces 1 and 2 are 10GbE (callout 1).

• Network interfaces 3 and 4 are 1GbE (callout 2).

Table 12: 10GB interface LED states

Link Status (top LED) Activity Status (bottom LED) Description

Off Off

Off Flash green

Steady green Off

Table 13: 1GB interface LED states

Link Status (left LED) Activity Status (right LED) Status Description

No network connection.

Sending or receiving network
data.

Connected to the network.

Off Off

Green Off

Amber

Off Flash green

Off

No network connection.

Connected to the network at
maximum port speed.

Connected to the network at
less than maximum port speed.

Sending or receiving network
data.

About network interface monitoring 51

Chapter 6: Drive maintenance

This section contains the following topics:

• Drive maintenance guidelines

• Remove a drive

• Remove a secured drive

• Install a drive

• Install and secure a drive

If a disk drive fails, replace it as soon as possible to avoid data loss.

Drive maintenance guidelines

• You can replace a single failed or failing drive without disrupting operations.

• When replacing an encrypted disk drive, the replacement drive must be unsecured. When installed,
the replacement drive is secured automatically using the existing Security Key. If the replacement drive
is secured with a key not used in the server, you must erase the drive, which destroys all data on the
physical disk, before the server can use it.

• Do not remove a drive until you are ready to replace it.

• Replace drives only with drives of the same size, speed, and type. For information on supported
replacement drives and the required firmware revision, contact Customer Support.

• Store drives properly. Store replacement drives in the packaging in which they were shipped. Do not
stack drives or place anything on top of a drive.

• Protect drives from electrostatic discharge. Wear an electrostatic wrist strap when handling a drive,
unless it is protected from electrostatic discharge.

• Handle drives carefully. Hold a drive only by the plastic part of the carrier or the handle. Do not drop or
jolt a drive or force a drive into a drive slot.

• Do not leave a drive slot empty. Each drive slot must contain a drive or a blank carrier. Operating the
server with an empty drive slot voids your warranty and support contract.

• Do not remove a drive from its carrier unless instructed by Customer Support.

• Keep shipping material. Return a failed drive to Customer Support in the packaging in which the
replacement drive was shipped. Shipping drives in unauthorized packaging may void your warranty.

Drive replacement requires a RAID rebuild, which might take some time to complete on a server that
contains many GB or TB of data. The rebuild might proceed faster if you complete these tasks:

• Quiesce I/O or do the replacement operation at a time when I/O is minimal.

• Shut down VMs.

• Migrate VMs to an alternate host.

NOTE:

You can use the LEDs to monitor the RAID rebuild status.

For more information about how to complete the tasks, see the SimpliVity OmniStack Administrator Guide.

52 Drive maintenance guidelines

Remove a drive

You remove a hard disk drive (HDD) or solid state drive (SSD) that has failed, or is failing, to replace it
with a new drive. Replace a problem drive as soon as possible.

Before you begin

You have completed these tasks:

• Obtained a replacement drive of the same type, speed, and capacity of the drive you are removing.

• Read the guidelines for maintaining disk drives.

• Read the guidelines for protecting hardware from electrostatic discharge.

Procedure overview

• Do not leave a drive slot empty. Do not remove a failed drive unless you have a replacement drive or
blank carrier ready to install.

• If the system is in a Federation, using incompatible drives might cause your Federation to function
incorrectly. Also, performance might be degraded while a drive is defective or missing.

Procedure

1. Remove the bezel, if necessary.

2. Examine the drive LEDs to identify the failed drive.

3. Press the release button to release the drive handle.

Figure 24: Drive removal

4. Rotate the handle downward, disengaging the drive from the slot.

5. Grasp the edge of the plastic drive carrier and slowly remove the drive from the slot.

6. Place the drive on a surface that is protected from electrostatic discharge.

7. Install the replacement drive or a drive filler.

Remove a drive 53

Remove a secured drive

Before you begin

You have completed these tasks:

• Obtained an unsecured replacement drive of the same type, speed, and capacity of the drive you are
removing. You cannot replace a secured drive with a drive that does not supported encryption or a
drive that is currently secured by a different controller. If the drive is currently secured, you must erase
the drive to delete its security attributes. See Erase a drive that supports encryption on page 40.

• Read the guidelines for maintaining disk drives. See Drive maintenance guidelines on page 52.

• Read the guidelines for protecting hardware from electrostatic discharge. See About electrostatic

discharge on page 17.

Procedure overview

NOTE:

If the system is in a Federation, using incompatible drives might cause your Federation to
function incorrectly. Also, performance might be degraded while a drive is defective or missing.

Procedure

1. Remove the bezel, if necessary.

2. Examine the drive LEDs to identify the failed drive.

3. Press the release button to release the drive handle.

4. Rotate the handle downward, disengaging the drive from the slot.

5. Grasp the edge of the plastic drive carrier and slowly remove the drive from the slot.

If you are monitoring using the SimpliVity interface, the RAID set has a status of Degraded.

6. Place the drive on a surface that is protected from electrostatic discharge.

7. Install the replacement drive.

54 Remove a secured drive

Install a drive

You install a drive to replace a failed, or failing, hard disk drive (HDD) or solid state drive (SSD). You can
also install a drive filler, since the drive bay cannot be empty after the failed drive is removed.

Before you begin

You have completed these tasks:

• Obtained a replacement drive of the same type, speed, and capacity of the drive you are replacing.

• Read the guidelines for maintaining disk drives and verified that all backup operations have completed.

• Read the guidelines for protecting hardware from electrostatic discharge.

• Removed the failed drive.

Procedure overview

NOTE:

Do not leave a drive slot empty. Do not remove a failed drive unless you have a replacement
drive or blank carrier ready to install.

Procedure

1. Carefully remove the replacement drive from its packaging.

2. Hold the drive by the edge of the plastic drive carrier and press the release button to release the drive

handle.

Figure 25: Drive installation

3. Rotate the handle outwards.

4. Orient the drive properly.

5. Grasp the edge of the plastic drive carrier and slowly insert the drive into the slot, stopping when you

feel resistance.

6. Simultaneously rotate the handle upward and press the drive completely into the slot.

7. Examine the LEDs and event messages to ensure the drive is operational.

Install a drive 55

Install and secure a drive

Before you begin

You have completed these tasks:

• Obtained an unsecured replacement drive of the same type, speed, and capacity of the drive you are
removing. You cannot replace a secured drive with a drive that does not support encryption or a drive
that is currently secured by a different controller. If the drive is currently secured, you must erase the
drive to delete its security attributes. See Erase a drive that supports encryption on page 40.

• Read the guidelines for maintaining disk drives. See Drive maintenance guidelines on page 52.

• Read the guidelines for protecting hardware from electrostatic discharge. See About electrostatic
discharge on page 17.

• Removed the failed drive. See Remove a secured drive on page 54.

Procedure

1. Carefully remove the replacement drive from its packaging.

2. Hold the drive by the edge of the plastic drive carrier and press the release button to release the drive

handle.

3. Rotate the handle outwards.

4. Orient the drive properly.

5. Grasp the edge of the plastic drive carrier and slowly insert the drive into the slot, stopping when you

feel resistance.

6. Simultaneously rotate the handle upward and press the drive completely into the slot.

NOTE:

The RAID set begins rebuilding to configure the new drive and to ecrypt it with the existing
Security Key.

7. Examine the LEDs on the drive and event messages to ensure the drive is operational.

56 Install and secure a drive

Chapter 7: Power supply maintenance

This section contains the following topics:

• Power supply maintenance guidelines

• Remove a power supply

• Install a power supply

Each server has two hot-swappable power supplies. If a power supply fails, replace it as soon as possible.

Power supply maintenance guidelines

Follow these guidelines for maintaining power supplies:

• You can replace a power supply without disrupting operations if an alternate, functioning power supply
is installed and connected to power.

• For proper cooling, do not leave a power supply slot open. Do not remove a power supply until you are
ready to replace it.

• A server can operate with only one functioning power supply. However, replace a failed or failing power
supply as soon as possible.

• Replace a power supply only with a power supply of the same type and wattage. Contact Customer

Support for replacement power supplies.

Remove a power supply

You replace a failed, or failing, power supply as soon as possible.

Before you begin

You have completed these tasks:

• Obtained a replacement power supply of the same type and wattage.

• Read the guidelines for maintaining power supplies.

• Read the guidelines for protecting hardware from electrostatic discharge.

Procedure overview

Please note the following information before you begin the procedure.

NOTE:

Do not leave a power supply slot empty. Do not remove a failed power supply unless you have a
replacement power supply that is ready to install.

Procedure

1. Identify the failed power supply.

2. Disconnect the power cable from the power supply.

3. Grasp the power supply handle and the orange release latch and press the release latch to the right.

Power supply maintenance guidelines 57

4. Gently pull the power supply from the slot.

Install a power supply

You install a power supply to replace a failed or failing power supply.

Before you begin

You have completed these tasks:

• Obtained a replacement power supply of the same type and wattage.

• Read the guidelines for maintaining power supplies.

• Read the guidelines for protecting hardware from electrostatic discharge.

Procedure

1. Carefully remove the replacement power supply from its packaging.

2. Orient the power supply so that the release latch is in the appropriate location, depending on the

model.

3. Slide the power supply into the empty slot until you hear the latch engage.

58 Install a power supply

4. Ensure that the power supply is fully inserted and locked in by the orange, spring-loaded clip.

5. Connect and secure the power cable to the new power supply.

6. Ensure that the power cables are fully inserted at both ends.

7. Ensure that the new power supply is operational.

8. Examine the LEDs and event messages to ensure the power supply is operational.

Install a power supply 59

Chapter 8: Network cabling options

This section contains the following topics:

• About the 10GbE-only network configuration

• About the direct-connected network configuration

• About the switch-connected network configuration

There are different options for cabling the 10 GbE and 1 GbE interfaces used for the SimpliVity networks:
Storage, Federation, and Management. You select the configuration that best meets the needs of your
environment.

About the 10GbE-only network configuration

The minimum network configuration for a Federation with two OmniCube servers uses redundant 10GbE
connections to two 10GbE switches. This configuration uses VLANs to separate the SimpliVity Storage,
Federation, and Management networks.

Figure 26: 10GbE-only network configuration

Configuration guidelines:

• For each system, use two SFP+ Direct Attach active cables (or Fiber Optic cables) to connect the
10GbE ports to different 10GbE switches.

60 About the 10GbE-only network configuration

• Separate the SimpliVity Storage, Management, and Federation networks by using VLANs on each
switch.

About the direct-connected network configuration

A direct-connected network configuration for a Federation with two OmniCube servers uses the 10GbE
connections for the SimpliVity Storage and Federation networks. It uses redundant 1GbE connections to
1GbE switches for the Management network.

Figure 27: Direct-connected Storage network configuration

Configuration guidelines:

• You cannot use direct connections for the Storage and Federation networks if you have three or more
systems in a Federation datacenter or cluster.

• For each system, you can use two SFP+ Direct Attach (Twinax) cables (or Fiber Optic cables) to
directly connect the 10GbE network interfaces.

• For each system, you use two network cables to connect the 1GbE network interfaces to different
1GbE switches. 1GbE cables are not provided in the shipping carton.

• Port 1 on system A must connect to port 1 on system B and port 2 on system A must connect to port 2
on system B.

About the direct-connected network configuration 61

About the switch-connected network configuration

The switch-connected network configuration for a Federation with two OmniCube servers uses redundant
connections to 10GbE switches for the SimpliVity Storage and Federation networks. It uses redundant
1GbE connections to 1GbE switches (shown below) or, optionally, 10GbE connections to 10GbE switches
for the Management network.

Figure 28: Switch-connected Storage network configuration

Configuration guidelines:

• For each system, use two SFP+ Direct Attach active cables (or Fiber Optic cables) to connect the
10GbE network interfaces to different 10GbE switches.

• For each system, use two network cables to connect the 1GbE network interfaces to different 1GbE
switches. 1GbE cables are not provided in the shipping carton.

62 About the switch-connected network configuration

Appendix A: Additional information

This section contains the following topics:

• SimpliVity documentation conventions

• SimpliVity terminology

• Websites

• Regulatory information

• Documentation feedback

SimpliVity documentation conventions

SimpliVity documentation uses the following conventions to assist your reading.

General formatting

Monospace font represents a command line syntax, file path, system output, or similar code.

Italic font represents a user-defined name or variable.

Bold font represents a user interface element, such as a button or tab, with which a user interacts.

Command Line formatting

SimpliVity documentation uses the following format for CLI commands:

command --option variable

where

• command is the name of the command and should be typed exactly as shown.

• --option is a command option and should be typed exactly as shown.

• variable is an option variable and should be replaced with the required value.

Informational Alerts

WARNING:

Alerts you to the risk of bodily injury, damage to hardware or software, loss of
warranty, or loss of data.

Caution:

Alerts you to the risk of data unavailability or possible issues with regard to security,
performance, or configuration.

NOTE:

Indicates information that is supplemental or that may require additional attention.

SimpliVity documentation conventions 63

Tip:

Provides helpful information such as best practices.

SimpliVity terminology

The following table contains SimpliVity terms and definitions.

Term Definition

Arbiter SimpliVity software that runs on the computer hosting the hypervisor

management server or a different Windows computer that the OmniStack hosts
can access. It is required in every SimpliVity Federation. The arbiter provides
the tie-breaking vote when a cluster contains an even number of OmniStack
hosts. For example, if a cluster contains two OmniStack hosts and one of those
OmniStack hosts loses connectivity with the cluster, the arbiter acts as the
tie breaker. (Note that an arbiter must not run on any host within a cluster for
which it is acting as a tie breaker.) (Previously referred to as an OmniCube
Arbiter.)

cluster A collection of OmniStack hosts that share resources and provide high

availability and load-balancing services.

datastore A container for virtual machine files, including compute and storage resources.

For more information, refer to your hypervisor documentation.

failure domain A collection of OmniStack hosts that serve as potential high availability failover

targets for each other for purposes of high availability and disaster recovery.

Federation A collection of SimpliVity OmniStack hosts and clusters managed in a single

globally-unified management domain.

guest operating
system

host A generic term referring to either an OmniStack host or a standard host.

OmniCube host See OmniStack host.

OmniStack Accelerator A SimpliVity PCI card that provides non-volatile memory, accelerated

OmniStack host A host (server) containing an OmniStack Accelerator card that communicates

The operating system that runs inside a virtual machine.

compression, and cryptographic hashing. The Accelerator card communicates
with the OmniStack software.

with the OmniStack software and some supported virtualization software. An
OmniStack host uses a dedicated virtual machine called the OmniStack Virtual
Controller, which runs the OmniStack software. (Previously referred to as an
OmniCube host.)

64 SimpliVity terminology

Term Definition

OmniStack software The SimpliVity software running on the OmniStack Virtual Controller.

(Previously referred to as OmniCube software.)

OmniStack Virtual
Controller

(OVC)

SimpliVity Arbiter See Arbiter.

standard host A host that does not contain OmniStack software.

virtual machine

(VM)

Websites

General websites

• Hewlett Packard Enterprise Information Library:

http://www.hpe.com/info/EIL

• Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix:

http://www.hpe.com/storage/spock

A virtual machine dedicated to the OmniStack host that runs the OmniStack
software. This software in turn communicates with the OmniStack Accelerator
card inside the host. (Previously referred to as an OmniCube Virtual Controller.)

A virtual computer environment that runs a guest operating system and
associated application software. Multiple virtual machines can operate
concurrently on the same physical host machine.

• Storage white papers and analyst reports:

http://www.hpe.com/storage/whitepapers

• Customer Self Repair:

http://www.hpe.com/support/selfrepair

• Insight Remote Support:

http://www.hpe.com/info/insightremotesupport/docs

Regulatory information

To view the regulatory information for your product, view the Safety and Compliance Information for
Server, Storage, Power, Networking, and Rack Products, available at the Hewlett Packard Enterprise
Support Center:

http://www.hpe.com/support/Safety-Compliance-EnterpriseProducts

Additional regulatory information

Hewlett Packard Enterprise is committed to providing our customers with information about the chemical
substances in our products as needed to comply with legal requirements such as REACH (Regulation EC
No 1907/2006 of the European Parliament and the Council). A chemical information report for this product
can be found at:

http://www.hpe.com/info/reach

Websites 65

For Hewlett Packard Enterprise product environmental and safety information and compliance data,
including RoHS and REACH, see:

http://www.hpe.com/info/ecodata

For Hewlett Packard Enterprise environmental information, including company programs, product
recycling, and energy efficiency, see:

http://www.hpe.com/info/environment

Documentation feedback

Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us
improve the documentation, send any errors, suggestions, or comments to Documentation Feedback
(mailto:[e-mail]). When submitting your feedback, include the document title, part
number, edition, and publication date located on the front cover of the document. For online help content,
include the product name, product version, help edition, and publication date located on the legal notices
page.

66 Documentation feedback