ActiveScale P100 Site Survey

ActiveScale™ P100 Site Survey
ActiveScale™ OS Version 5.2.0

Publication 1ET0364 | 5.2 D-2.0 | February 2018
Long Live Data™ | www.hgst.com
22 4
Copyright
Publication Information
One MB is equal to one million bytes, one GB is equal to one billion bytes, one TB equals
1,000GB (one trillion bytes) and one PB equals 1,000TB when referring to storage capacity.
Usable capacity will vary from the raw capacity due to object storage methodologies and other
factors.
The following paragraph does not apply to any jurisdiction where such provisions are
inconsistent with local law: THIS PUBLICATION IS PROVIDED "AS IS" WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
This publication could include technical inaccuracies or typographical errors. Changes are
periodically made to the information herein; these changes will be incorporated in new editions
of the publication. There may be improvements or changes in any products or programs
described in this publication at any time. It is possible that this publication may contain
reference to, or information about, HGST products (machines and programs), programming, or
services that are not announced in your country. Such references or information must not be
construed to mean that Western Digital Corporation intends to announce such HGST products,
programming, or services in your country. Technical information about this product is available
by contacting your local HGST product representative or on the Internet at support.hgst.com.
Western Digital Corporation may have patents or pending patent applications covering subject
matter in this document. The furnishing of this document does not give you any license to these
patents.
© 2016-2018 Western Digital Corporation or its affiliates.
Long Live Data, EasiScale, ActiveScale OS , and the HGST logo are registered trademarks or
trademarks of Western Digital Corporation or its affiliates in the U.S. and/or other countries.
Amazon S3, Amazon Simple Storage Services, and Amazon AWS S3 are trademarks of
Amazon.com, Inc. or its affiliates in the United States and/or other countries. Other trademarks
are the property of their respective owners. References in this publication to HGST-branded
products, programs, or services do not imply that they will be made available in all countries.
Product specifications provided are sample specifications and do not constitute a warranty.
Actual specifications for unique part numbers may vary. Please visit the Support section of our
website www.hgst.com/support/systems-support for additional information on product
specifications. Photographs may show design models. References in this publication to HGST-
branded products, programs or services do not imply that they are to be available in all
countries in which HGST operates.
2
Contents
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Dimensions and weights that affect rack selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Power specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Physical system questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Customer rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Servicing space requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Delivery questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Customer information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Preparation for delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Dock delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Street delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Elevator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Stairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Installation space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Site questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Server room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Power and lighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Single site bring-up, pre-login configuration, networking . . . . . . . . . . . . . . . . . . . . . . . 23
Networking legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Network definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Guidelines for the public networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Guidelines for the system scale-out and storage networks . . . . . . . . . . . . . . . . . 24
Single Site bringup: post-login configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
S3 domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Storage policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
ActiveScale Cloud Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Multi-Site Bringup: pre-login configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3
Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Networking legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Guidelines for the public networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Guidelines for the System (“Scaleout”) and Storage Gateways . . . . . . . . . . . . . . . . 29
Guidelines for the System (“Scaleout”) and Storage Networks . . . . . . . . . . . . . . . . 29
Multi-Site Bringup: post-login configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
S3 Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Storage policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
ActiveScale Cloud Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Points of contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4
ActiveScale™ OS P100 Site Survey Overview
1 Overview
This survey is intended to assist HGST and users of the ActiveScale™ P100 system to determine whether
the user site is prepared to receive an ActiveScale P100 system.
The facility in which an ActiveScale system will be deployed should meet Uptime Institute Tier 3
specifications. It must provide contiguous rack space, adequate site power for the full capacity power
density per system, adequate HVAC, and it must be accessible on a 24/7 schedule in support of SLA
commitments. Due to the lights-out nature of the solution, the facility must provide equipment staging (up
to 30 days) and provide a protocol for accepting shipment on behalf of Solution Provider. The system is
designed to direct all exhaust towards the rear, and blanking plates are installed to cover open space in
between components. All components fit into an ANSI/EIA-310-D-1992 19” Rack with 914 mm minimum
depth.
• General specifications on page 6
• Power specifications on page 7
• Warnings on page 7
5
1.1 General specifications

The following table is a summary of specifications relevant to the ActiveScale P100 system, and relevant
specs are also noted in their respective content categories. The specifications are also provided in context
throughout the survey for convenience.
Condition Non-operating Operating
Temperature -40°C to 70°C or -50°F to 158°F) 10°C to 35°C or 50°F to 95°F)
Temperature gradient 30°C per hour 20°C per hour
Temperature de-rating 1°C per 300 m above 950 m 1°C per 300 m above 950 m
Relative humidity 20% to 95% non-condensing 20% to 85% non-condensing
Relative humidity gradient 30% per hour maximum 30% per hour maximum
Altitude -300 m to 12,000 m -300 m to 3,048 m
-984 ft to 39,3711 ft -984 ft to 10,000 ft
6
1.2 Dimensions and weights that affect rack selection

Component Dimensions Individual weight Total weight
System Interconnect W—17.3 in (438 mm) 20 lbs (9 kg) 40 lbs (18 kg)
D—17 in (431 mm)
H—1U
System Node W—17.2 in (437 mm) 27 lbs (12.2 kg) 81 lbs (36.6 kg)
D—24 in (610 mm)
H—1U
Storage Node W—17.6 in (448.2 mm) 87 lbs (78.6 kg) 522 lbs (471.6 kg)
D—36 in (915 mm)
H—1U
Base system (one column) W—17.6 in (448.2 mm) N/A 665.2 lbs (301.7 kg)
D—36 in (915 mm)
H—12U
Mid system (two columns) W—17.6 in (448 mm) N/A 1197.4 lbs (543.1 kg)
D—36 in (915 mm)
H—18U
Full system (three columns) W—17.6 in (448 mm) N/A 1729.6 lbs (784.5 kg)
D—36 in (915 mm)
H—24U
Single scale up kit (6 Storage W—17.6 in (448 mm) N/A 532.2 lbs (241.4 kg)
Nodes, 6 rail kits, 1 cable kit) D—36 in (915 mm)
H—6U
1.3 Power specifications

The following table is a summary of the power specifications for the ActiveScale P100 system.
Parameter Base configuration Single scale-up kit
Connector Type C13 to C14 C13 to C14
Number of connectors PDU requirement—22 C13 power PDU requirement—12 C13 power
sockets. HGST recommends supplying sockets. HGST recommends
redundant power from two PDUs. supplying redundant power from two
PDUs.
Typical system power required, 1.85 to 2.03 KW 1.38 to 1.51 KW
typical to maximum.
1.4 Warnings
Each ActiveScale P100 multi-site system has a factory-assigned designation as Site 1, Site 2, or Site 3. If
you are ordering scale-up/out kits for an ActiveScale P100 multi-site system, you must enter the correct
system serial number, factory-assigned site number, and address of each site in the Delivery questions
section. You can find this information in the administrator interface ActiveScale SM. This information
ensures that the scale-up/out kits for Site 1, Site 2, and Site 3 are shipped to the correct site and that when
7
the system provisions the scale-up/out kits, the site numbers for the existing system and the new scale-up/
out kit match.
8
ActiveScale™ OS P100 Site Survey Physical system questions
2 Physical system questions

2.1 Customer rack
The ActiveScale P100 system is to be installed in a customer provided rack. Answer the following
questions about the rack that has been chosen for the system.
Specification Measurement
Rack manufacturer
Rack model number
Rack dimensions, internal rack inches millimeters
post width
Rack dimension, internal rack inches millimeters
post minimum depth
Rack dimensions, internal rack inches millimeters
post maximum depth
Rack weight lbs kgs
Rack available space - 12U Yes No
contiguous.
Notes
2.2 Servicing space requirement

The ActiveScale P100 system requires space in the front and in the rear of the rack for installation and
servicing. The front space requirement allows for the length of the longest system component and for
technicians handing those components. The rear space requirement allows for the space a technician would
need to service CRUs and FRUs.
Rack spacing Measurement
Minimum front space 1220 mm or 48 in
Minimum rear space 560 mm or 22 in
Notes
9
ActiveScale™ OS P100 Site Survey Delivery questions
3 Delivery questions
3.1 Customer information
The following table contains questions about the customer.
Site 1 Site 2 Site 3
Site and System serial number
If you are ordering scale-up kits for a multi-site
deployment you must enter the correct value here. You
can find the site number and system number in the
administrator interface ActiveScale SM.
Address
If you are ordering scale-up kits for a multi-site
deployment, the site address is needed to ensure that
new kits' factory-assigned designations match the
equipment already at the site.
Organization name
Contact name
Phone
Email
Notes
10
3.2 Preparation for delivery

The following table contains questions about preparing for delivery.
What are the hours the
facility is open for
deliveries?
Are appointments Yes No Yes No Yes No
required?
Are there any security Yes No Yes No Yes No
or building access
requirements?
On what floor in the
building will the
equipment be
installed?
If equipment is not Yes No Yes No Yes No
going on the first
floor, is there an
elevator?
Note: For elevator
specifics, please see
the Elevator section
below.
Customer PO
Delivery address
Is the path from the Yes No Yes No Yes No
loading dock to the
server room robust
enough to support the
weight of the
configured system?
Does the facility have Yes No Yes No Yes No
proper floor covering
for delivery?
11
3.3 Dock delivery

The following table contains questions about dock delivery.
Is the dock large Yes No Yes No Yes No
enough for a
semitrailer?
What side of the North South East West North South East West North South East West
building is the
dock on?
What is the
street name, if
different than
company
address?
Is a forklift Yes No Yes No Yes No
required to reach
the dock?
What are the in mm in mm in mm
dimensions of
the loading dock
door(s)?
Notes
12
3.4 Street delivery

The following table contains questions about street delivery.
What side of the North South East West North South East West North South East West
building is the
access door on?
What is the
street name, if
different than
company
address?
Is a forklift Yes No Yes No Yes No
required to reach
the dock?
What are the in mm in mm in mm
dimensions of
the loading dock
door(s)?
Notes
13
3.5 Elevator
The following table contains questions about the elevator.
What is the lbs kgs lbs kgs lbs kgs
weight capacity
of the elevator?
What is the
depth of the
elevator
What is the Yes No Yes No Yes No
height of the
elevator?
What is the in mm in mm in mm
width of the
elevator?
Notes
3.6 Stairs
The following table contains questions about the stairs.
How many
flights of stairs
are there?
What is the in mm in mm in mm
width of the
stairwells
Notes
14
3.7 Installation space

The following table contains questions about the installation space.
Is there a Yes No Yes No Yes No
delivery/
unpacking/
staging area?
Is there a raised Yes No Yes No Yes No
floor or any
threshold(s) of
concern?
If there is a in mm in mm in mm
raised floor, how
high/deep is it?
What sort of
equipment
maneuvering is
required for
installation
(ramps, spreader
plates, and so
on)?
Is any special Yes No Yes No Yes No
equipment
needed to place
the system in the
server room?
Notes
15
ActiveScale™ OS P100 Site Survey Site questions
4 Site questions
This section contains questions
• Facilities on page 17
• Server room on page 18
• Power and lighting on page 19
• Safety on page 20
• Cooling on page 20
16
4.1 Facilities
The following table contains questions about the facilities.
Site
Will the system be Yes No
unpacked in a different
location than it is installed?
Is the floor or raised floor Yes No
on-site capable of
supporting the weight of
the system?
Will installation Yes No
technicians be required to
move the packed system
through the facility?
Does the system need to be Yes No
unpacked before entering
the data center?
Does the data center have Yes No
the proper equipment and
personnel to move the
unpacked system to the
installation location?
Notes
Relevant specifications
Base Configuration: 274 kg / 605 lbs.
Single Scale Up Kit: 191 kg / 421 lbs.
17
4.2 Server room

The following table contains questions about the server room.
Site
Is there adequate space for an installation? Yes No
Is access to the site or server room restricted? Yes No
Are customer-supplied network cables Yes No
available and of the proper type?
Are rack anchors and stabilizers located in the Yes No
space in which the system will be installed?
Notes
System Dimensions:
Base Configuration
Height: 12U
Width: 17.6in. / 448mm
Depth: 35in. / 881mm
Scale Up Kit
Height: 6U
Width: 17.6in. / 448mm
Depth: 35in. / 881mm
18
4.3 Power and lighting

The following table contains questions about the power and lighting.
Site
Are lighting levels adequate for maintenance? Yes No
Are A/C outlets available for servicing needs (such as laptops)? Yes No
Do the input power specifications correspond to equipment Yes No
specifications?
Is power conditioning equipment installed? Yes No
Does the site mains power contain a breaker that is rated to Yes No
support the system configuration that is being powered?
Notes
Power Requirements (Typical/Max):
Base Configuration:
1.85 to 2.03 KW
PDU requirement is 22 C13 power sockets. HGST recommends using two PDUs, supplying redundant power to the
11 components from each PDU.
Scale Up Kit:
1.38 to 1.51 KW
PDU requirement is 12 C13 power sockets. HGST recommends using two PDUs, supplying redundant power to the
six components from each PDU.
19
4.4 Safety
The following table contains questions about the safety.
Site
Is there an emergency shutoff switch? Yes No
Is a fire protection system installed in the server room? Yes No
Is antistatic flooring installed? Yes No
Do any equipment servicing hazards exist? If any hazards exist, Yes No
please list them in the Notes section below.
Notes
4.5 Cooling
The following table contains questions about cooling.
Site
Can the system operating temperature be maintained? Yes No
Can temperature changes be maintained according to Yes No
equipment specifications?
Can humidity levels be maintained? Yes No
Are air conditioning filters installed and clean? Yes No
Notes
Operating Temperature: 10°C to 35°C (50°F to 95°F)
Temperature Gradient: 20°C/hour
Temperature De-rating: 1°C per 300m over 950m
Relative Humidity: 20% to 85% non-condensing
Humidity Gradient: 30% per hour maximum
Thermal Output:
Base System: 6.31/6.92 K BTU/hr
Scale-Up Kit: 4.70/5.15 K BTU/hr
20
ActiveScale™ OS P100 Site Survey Software
5 Software
This section contains questions about software.
• Encryption on page 22
• Replication on page 22
21
5.1 Encryption
The following table contains questions about encryption.
Site
Do you plan to enable encryption-at-rest? Yes No
Have you requested an encryption license key? Yes No
Notes
You can only enable encryption-at-rest after you obtain an encryption license key from HGST Support. The
encryption license key is a unique per-deployment key. In addition, you must specify a master encryption phrase at
initial bring-up when prompted by the configuration wizard.
5.2 Replication
The following table contains questions about replication.
Site
Do you plan to enable replication? Yes No
Is the network latency between sites less than 500 milliseconds? Yes No
Is packet loss rate less than or equal to 0.01%? Yes No
Notes
22
5.3 Single site bring-up, pre-login configuration, networking

The following table contains questions about networking.
Site
Is NIC bonding required on the public Yes No
networks?
If Yes, what mode; LACP, Round
Robin, or ALB?
If Yes, what link monitoring interval in
milliseconds? The default is 100ms
What are your network settings? Using
the guidelines in the Legend, please edit
the table below with your network
settings.
Notes
5.3.1 Networking legend

The legend below shows default settings for a single site base/mid/full ActiveScale P100 system. You must
change the green settings (public networks). You should only change the yellow settings (for system and
storage networks) if you have conflicts.
5.3.1.1 Network definitions

• Public Network 1 and Public Network 2 connect System Nodes to the public networks for S3 client
traffic. They are the system interface with the cloud. These networks must be physically deployed on
your own switches.
• System Network 1 and System Network 2 carry traffic between System Nodes and Storage Nodes.
• Storage Network 1 and Storage Network 2 are used solely within a Column for back-end traffic.
• IPMI IP addresses are assigned from System Network 1; there is no separate IPMI network. Remote
access to system hardware through IPMI is restricted to HGST Support and is strictly controlled by
you, through your hgstsupport passcode.
5.3.1.2 Guidelines for the public networks

• For a single-site deployment, you need to implement both public networks, and 3 IP addresses on
each. The public networks must be separate subnets. You have the following two options.
– Implement Public Network 1 and Public Network 2 as two different subnets on two different
public NIC ports.
– Implement a single public network as a single subnet spanning two bonded public NIC ports.
• You must specify a gateway IP address, and this IP address must be on either Public Network 1 or
Public Network 2.
23
5.3.1.3 Guidelines for the system scale-out and storage networks

• You are free to change 1st and 2nd octet.
• To aid readability and troubleshooting, do not change the 3rd octet. It adheres to the following VLAN
ID convention.
– For storage networks, <StorageInterconnect #><Site #><Column #>. Following is an
example.
172.16.111.0–Storage Network 1 for Column 1 at Site 1.
172.16.233.0–Storage Network 2 for Column 3 at Site 3.
– For system scale-out networks, <StorageInterconnect #><Site #> 0. Following is an
example.
172.16.110.0–System Network 1 at Site 1.
172.16.230.0–System Network 2 at Site 3.
• The system automatically generates the 4th octet.
Note: The 3rd digit of the 3rd octet is always 0 because system networks span all
columns and are column-independent.
Name Network Netmask Site 1 Site 2 Site 3 Gateway
Site1_Public
Network1
24
(continued)
Name Network Netmask Site 1 Site 2 Site 3 Gateway
Site1_Public
Network2
Site1_Scaleout 255.255.255.0
Network1
Site1_Scaleout 255.255.255.0
Network2
Site1_Column1 255.255.255.0
_Storage
Network1
Site1_Column1 255.255.255.0
_Storage
Network2
Site1_Column2 255.255.255.0
_Storage
Network1
Site1_Column2 255.255.255.0
_Storage
Network2
Site1_Column3 255.255.255.0
_Storage
Network1
Site1_Column3 255.255.255.0
_Storage
Network2
5.4 Single Site bringup: post-login configuration

5.4.1 Security
Note: The configuration wizard will prompt you for 3 security strings. You do not need to disclose these in
this survey, but you should plan for them ahead of time:
• Password for admin
• Master encryption phrase
• HGST Support passcode
Email address for admin
25
5.4.2 Notifications
DNS server (IP)
NTP server (IP or FQDN)
Do you want the system to notify HGST Support about CRITICAL system events? Yes No
SMTP server (IP or FQDN):
SMTP server username:
SMTP server password:
SMTP administrator email
address:
System administrator email
address (sender of system alerts):
Send test email? Yes No
Enable SNMP traps? Yes No
Enable SNMP polling? Yes No
SNMP trap port:
SNMP trap community string:
5.4.3 S3 domain
What are the S3 domain names? Default: HGST-S3
Do you have security certificates? Yes No
Note: You need two SSL certificates in PEM format: one for S3 and one for ActiveScale SM.
The PEM files must contain (in this order):
A public SSL certificate
A private SSL key
All necessary intermediate certificates all the way up to the intermediate or root certificates that are
included in standard web browsers
5.4.4 Location
Company name:
Street address:
City:
State:
Zip code:
Time zone:
26
5.4.5 Storage policy

Chosen storage policy: Balanced, single site
Note: The options on the left are a This policy provides balance between usable capacity, durability, and
summary of storage policy options throughput. It provides a usable capacity of 67% of the raw disk capacity. The
as they function with the default system will self-heal up to four simultaneously failed drives.
small file threshold. The average Large files: 13/4
object size is predefined for each
policy and is calculated to avoid • Small files: 6/4 with a threshold of 524,288 bytes to 8,388,608 bytes
stranded capacity. For details, see • Average object size: 800KB
the Active Scale OS Software • Overhead: Large files: 1.5x, Small files: 3.11x
Specification.
• Durability: Up to 11 nines
• Availability: Data is available even if one Storage Node is unavailable and one
additional drive fails.
Capacity optimized, single site
This policy provides highest usable capacity. It provides a usable capacity of
70% of the raw disk capacity. The system will self-heal up to four
simultaneously failed drives.
Large files: 15/4
• Small files: 6/4 with a threshold of 524,288 bytes to 8,388,608 bytes
• Average object size: 847KB
• Overhead: Large files: 1.42x, Small files: 3.11x
• Availability: Data is available even if one Storage Node is unavailable and one
additional drive fails.
Small file threshold:
5.4.6 ActiveScale Cloud Management

Enable ActiveScale CM (daily telemetry and logs sent to HGST)? Yes No
Note: If you will be using cloud
management, and your datacenter
uses a firewall, you will need to
open port 443 on the firewall.
What is the ActiveScale CM super

user email address?
Note: The email address should be
an individual enterprise address
and not an alias.
Does your data center require a proxy to connect to the internet? Yes No
What is the proxy server?
What is the proxy port?
What is the proxy username?
What is the proxy user password?
27
5.5 Multi-Site Bringup: pre-login configuration

This section contains questions related to the deployment of three ActiveScale P100 systems located in
three different data centers. This information is only for multi-site installations and should be skipped
otherwise.
5.5.1 Networking
Are the VLANs going to be trunked to reduce the number of uplink cables? Yes No
If No, skip the next two questions.
If Yes, you will need HGST Support to reconfigure the multi-site uplink ports on the Storage
Interconnects into a single VLAN trunk port to reduce the number of uplink cables.
Are the following VLAN ID ranges available on your routers? Yes No
For Column 1
Site 1: 110-111, 210-211
Site 2: 120-121, 220-221
Site 3: 130-131, 230-231
For Column 2
Site 1: 112, 212
Site 2: 122, 222
Site 3: 132, 232
For Column 3
Site 1: 113, 213
Site 2: 123, 223
Site 3: 133, 233
If No, what VLAN ID ranges are available on Site 1: Site 2: Site 3:
your routers for each site?
Are your routers at each site able to access your routers at the remote sites? Yes No
Is the latency (round trip time or “RTT”) between each of the system storage network locations no Yes No
more than 200ms?
Note: Run the latency test in both direction between each system.
Is the bandwidth and latency the same in both directions? Yes No
What are your network settings?
Using the guidelines in the Legend, please edit the table below with your network settings.
5.5.2 Networking legend

The legend below shows default settings for a multi-site base/mid/full ActiveScale P100 system. You must
change the green settings (public networks). You should only change the yellow settings (for system and
storage networks) if you have conflicts. Do not edit the red settings.
A summary of network definitions:
• Public Network 1 and Public Network 2 connect System Nodes to the public networks for s3 client
traffic. They are the system's interface with the cloud. These networks must be physically deployed on
your own switches.
28
• System Network 1 and System Network 2 carry traffic between System Nodes and Storage Nodes.
• Storage Network 1 and Storage Network 2 are used solely within a Column for back-end traffic.
• IPMI IP addresses are assigned from System Network 1; there is no separate IPMI network. Remote
access to system hardware through IPMI is restricted to HGST Support and is strictly controlled by
you, through your
• hgstsupport passcode.
5.5.3 Guidelines for the public networks

For a multi-site deployment, you need to implement the following at each site:
• 2 separate public networks, with 3 IP addresses on each
Tip: You can create Public Network 1 and Public Network 2 at each site, OR you
can spread Public Network 1 and Public Network 2 across all three sites (in other
words, you can use the same values for Public Network 1 and Public Network 2
across all three sites). In either case, you must assign unique IP addresses to each
System Node.
Important: You must specify a gateway IP address, and this IP address must be
on either Public Network 1 or Public Network 2.
• 2 uplink ports on your router for each Storage Interconnect; in other words, 4 uplink ports for a base
ActiveScale P100. For additional Column, you need 1 additional port on your router for each Storage
Interconnect; in other words, 2 additional ports per Column.
• 4 /24 subnets for internal networks; for each additional Column, 2 additional /24 subnets for
internal networks.
5.5.4 Guidelines for the System (“Scaleout”) and Storage Gateways

• You must create one gateway for each System/Storage Network, with IP address x.x.x.241-254. On
your router, you must remove any other gateway IP address within each System/Storage Network.
5.5.5 Guidelines for the System (“Scaleout”) and Storage Networks

• 1st and 2nd octet: you are free to change
• 3rd octet: to aid readability and troubleshooting, do not change the 3rd octet. It adheres to the
following VLAN ID convention:
– For Storage Networks: <StorageInterconnect #><Site #><Column #>.
Example:
172.16.111.0 – Storage Network 1 for Column 1 at Site 1.
172.16.233.0 –Storage Network 2 for Column 3 at Site 3.
– For System (“Scaleout”) Networks: <StorageInterconnect #><Site #>0
Important: The 3rd digit of the 3rd octet is always 0 because System Networks
span all Columns and are Column-independent.
Example:
172.16.110.0 – System Network 1 at Site 1.
172.16.230.0 – System Network 2 at Site 3.
29
• 4th octet: the system automatically generates this value.
Site Name: Site1

Rack serial #: ########
Name Network Netmask System System System Gateway

Node 1 Node 2 Node 3
Site1_PublicNetwork1
Name Network Netmask Gateway (MUST be

x.x.x.241-254)
Site1_ScaleoutNetwork1 255.255.255.0
Site1_Column1_StorageNetwork1 255.255.255.0
30
Site Name: Site2



x.x.x.241-254)
Site Name: Site3



x.x.x.241-254)
31
5.6 Multi-Site Bringup: post-login configuration

5.6.1 Security
Note: The configuration wizard will prompt you for 3 security strings. You do
not need to disclose these in this survey, but you should plan for them ahead of
time:
• Password for admin
• Master encryption phrase
• HGST Support passcode
Email address for admin
32
5.6.2 Notifications
DNS server (IP)
NTP server (IP or FQDN)
Do you want the system to notify Yes No
HGST Support about CRITICAL
system events?
SMTP server (IP or FQDN):
SMTP server username:
SMTP server password:
SMTP administrator email
address:
System administrator email
address (sender of system alerts):
Send test email? Yes No
Enable SNMP traps? Yes No
Enable SNMP polling? Yes No
SNMP trap port:
SNMP trap community string:
5.6.3 S3 Domain
What are the S3 domain names? Default:
HGST-S3
Do you have security certificates? Yes No
Note: You need two SSL certificates in PEM format: one for S3 and one for ActiveScale SM.
The PEM files must contain (in this order):
A public SSL certificate
A private SSL key
All necessary intermediate certificates all the way up to the intermediate or root certificates that are
included in standard web browsers
5.6.4 Location
Company name:
Street address:
City:
State:
Zip code:
Time zone:
33
5.6.5 Storage policy

Chosen storage policy: Availability optimized, multi-site
Note: The options on the left are a This policy has the highest availability. When a single site is offline and up to
summary of storage policy options two drives fail in the remaining sites, all data is still available. It provides a
as they function with the default usable capacity of 53% of the raw disk capacity. The system will self-heal up to
small file threshold. The average eight simultaneously failed drives.
object size is predefined for each Large files: 18/8
policy and is calculated to avoid
stranded capacity. For details, see • Small files: 10/8 with a threshold of 524,288 bytes to 8,388,608 bytes
the Active Scale OS Software • Average object size: 693KB
Specification. • Overhead: Large files: 1.88x, Small files: 5.87x
• Availability: Data is available even if one site is unavailable and two additional
drives fail.
Balanced, multi-site
This policy provides balance between usable capacity and availability. When a
single site is offline and one drive fails in the remaining sites, all data is still
available. It provides a usable capacity of 58% of the raw disk capacity. The
system will self-heal up to seven simultaneously failed drives.
Large files: 18/7
• Small files: 9/7 with a threshold of 524,288 bytes to 8,388,608 bytes
• Average object size: 698KB
• Overhead: Large files: 1.72x, Small files: 4.67x
• Availability: Data is available even if one site is unavailable and one additional
drive fails.
Small file threshold:
5.6.6 ActiveScale Cloud Management

Enable ActiveScale CM (daily telemetry and logs sent to HGST)? Yes No
Note: If you will be using cloud
management, and your datacenter
uses a firewall, you will need to
open port 443 on the firewall.
What is the ActiveScale CM super

user email address?
Note: The email address should be
an individual enterprise address
and not an alias.
Does your data center require a proxy to connect to the internet? Yes No
What is the proxy server?
What is the proxy port?
What is the proxy username?
34
What is the proxy user password?
35
Points of contact
Contact HGST Support with your rack serial number or deployment ID.
Support website www.hgst.com/support/systems-support
Telephone number 1-844-717-7766 or 1-408-717-7766
Company website www.hgst.com
36

ActiveScale P100 Site Survey

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ActiveScale P100 Site Survey

Încărcat de

Drepturi de autor:

Formate disponibile

ActiveScale™ P100 Site Survey

ActiveScale™ OS Version 5.2.0

Long Live Data™ | www.hgst.com

© 2016-2018 Western Digital Corporation or its affiliates.

Physical system questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1.1 General specifications

1.2 Dimensions and weights that affect rack selection

1.3 Power specifications

2 Physical system questions

2.2 Servicing space requirement

3.2 Preparation for delivery

3.3 Dock delivery

3.4 Street delivery

3.7 Installation space

4.2 Server room

4.3 Power and lighting

Power Requirements (Typical/Max):

5.3 Single site bring-up, pre-login configuration, networking

5.3.1 Networking legend

5.3.1.1 Network definitions

5.3.1.2 Guidelines for the public networks

5.3.1.3 Guidelines for the system scale-out and storage networks

Name Network Netmask Site 1 Site 2 Site 3 Gateway

5.4 Single Site bringup: post-login configuration

Email address for admin

5.4.5 Storage policy

5.4.6 ActiveScale Cloud Management

What is the ActiveScale CM super

5.5 Multi-Site Bringup: pre-login configuration

5.5.2 Networking legend

5.5.3 Guidelines for the public networks

5.5.4 Guidelines for the System (“Scaleout”) and Storage Gateways

5.5.5 Guidelines for the System (“Scaleout”) and Storage Networks

• 4th octet: the system automatically generates this value.

Site Name: Site1

Name Network Netmask System System System Gateway

Name Network Netmask Gateway (MUST be

Site Name: Site2

Name Network Netmask System System System Gateway

Name Network Netmask Gateway (MUST be

Site Name: Site3

Name Network Netmask System System System Gateway

Name Network Netmask Gateway (MUST be

5.6 Multi-Site Bringup: post-login configuration

Email address for admin

5.6.5 Storage policy

5.6.6 ActiveScale Cloud Management

What is the ActiveScale CM super

What is the proxy user password?

S-ar putea să vă placă și