Seagate Lyve Rack R1 Operating instructions

Page 1of 7Seagate PN 1104485-01_rD
Lyve Rack R1
Lyve Rack R1 Installation Site Requirements Checklist
Contents
1. Introduction ............................................................................................................................................... 1
2. Lyve Rack R1 Networking & Physical Checklist........................................................................................... 1
3. Lyve Pilot to CORTX Interface (optional) requirements.............................................................................. 5
4. CORTX Manager and S3 Client to CORTX Interface requirements .............................................................. 5
5. S3 Client and CORTX Interface requirements ............................................................................................. 5
6. Example Information Sheet (provided with Lyve Rack R1)......................................................................... 7
1. Introduction
Lyve Rack R1 is shipped from the Factory or Distributor with the majority of the hardware and software
configuration completed to enable rapid deployment. However, certain configuration elements are necessarily
site specific and must be completed BEFORE powering on the hardware. This checklist is intended to provide an
overview of those requirements along with the critical information needed to enable the onsite set up of Lyve
Rack R1 products. Multiple networking configuration elements are required coupled with physical installation
dependencies. Please review the entire document before working through the sections in order. The following is
the high-level installation sequence for the Lyve Rack R1:
Preboarding –set up of networking configuration and other elements pertaining to operational configuration.
Unboxing –unpacking of the hardware components, racking, cabling, Object Store initialization.
Onboarding –Configuration of the Object Store for use in your environment.
To facilitate network IP setup based on Reserved Addresses, an information sheet is provided with each Lyve
Rack R1 product in the accessories kit showing network device MAC addresses. Seagate recommends that you
retrieve the Information Sheet and the Installation Guide from the kit and use the documentation in conjunction
with this checklist to plan and define your configuration before physically unboxing and racking the hardware.
An example of the sheet is shown at the end of this checklist.
2. Lyve Rack R1 Networking & Physical Checklist
Item
Requirement
Comment
Check
Networking
Management
Networking
On the Management Switch: 1GbE or 10GbE
RJ45 ports.4 ports are required.
The management interfaces and management
virtual IP must be on a different subnet to the
High Speed Data interfaces and the High Speed
Data virtual IP.
Some of the cables must be procured by
you.
All ports must be ‘pingable’ from the
management console (i.e any system
used to communicate with the LR).

Page 2of 7Seagate PN 1104485-01_rD
The management interfaces and the BMC
interfaces on both servers could be on different
subnets or VLANs (should higher protection for
the BMC interface be desired). If this approach
is used, the Management network must be
routable to the BMC network and there must
not be any IPMI filtering between these two
subnets.
The Management Virtual IP must be on the
same subnet as the physical interfaces for the
Management network.
1 x static IP is required for the Management
Virtual IP.
Physical interfaces for each server are
configured using DHCP static allocation (aka
DHCP reservation). The Information sheet
supplied with each Lyve Rack R1 unit
documents the pertinent MAC addresses.
High Speed
Data
Networking
(Public data
interface)
IEEE 802.3bg (QSFP28) compatible switch
25GbE, 50GbE, or 100GbE.
1 port required if supplied Y-cable is used and
the port must be configured in breakout mode.
Alternatively, if it is desired to connect the
servers to two separate High Speed Data
Switches for redundancy, direct connect cables
(not supplied) may be used. In this scenario,
the ports on both switches must be configured
on the same subnet.
The Data Virtual IP must be on the same
subnet as the physical interfaces for the Data
network.
The High Speed Data interfaces and the High
Speed Data virtual IP must be on a different
subnet to the management interfaces and
management virtual IP.
1 x static IP is required for the Data Virtual IP.
Physical interfaces for each server are
configured using DHCP static allocation (see
Information sheet for MAC addresses).
S3 data sources and clients must be routable to
the subnet on which the data VIP is configured.
Anything that supports QSFP28
connections.
You must procure the 100GbE to dual
50GbE Y-cable or two 100GbE to
100GbE separate cables.
DHCP server
(Optional if
static IP
configuration
is used)
Lyve Rack R1 currently supports DHCP server
and static IP configurations.
The DHCP server configuration supports:
•IP allocation (static DHCP lease) based on
configuring Reserved Addresses to
correspond to MAC addresses (provided
on information sheet).

Page 3of 7Seagate PN 1104485-01_rD
Lyve Rack R1 does not yet support
configuration of Static IPs on the CORTX
servers.
DHCP Server must also provide the IP address
of the Gateway and Domain Name Server
(DNS) to be used.
All IP addresses related to the same type of
network including its Virtual IP address, should
be configured for the same subnet.
The DHCP statically assigned Management
Interface address of each server and the
Management VIP (floating IP) must be on the
same subnet.
The DHCP statically assigned Public Data
Interface address of each server and the Data
VIP (floating IP) must be on the same subnet,
but the subnet can be different to the
management Interface group subnet.
Static IP
You must be aware of IP addresses, subnet
masks, and IP of the gateway.
DNS
Fully Qualified Domain Names (FQDN) must be
configured for:
1. Management VIP
2. Data VIP
3. Server A Management Interface IP
4. Server B Management Interface IP
Firewall
Configuration
Following are the firewall configurations:
Service
Service
Name
Direction
Protocol
Port
Network
Interface
Purpose
CORTX
Manager
Web Server
Incoming &
Outgoing
HTTPS
28100
Public Management
Network
CORTX
Manager GUI
webserver port
CORTX
Manager
SSH
Incoming &
Outgoing
TCP/UDP
22
Public Management
Network
Execution of
CORTX CLI or
generating
Support bundles
S3
HA proxy
Incoming &
Outgoing
HTTPS
443
Public Data
Network
External S3
Endpoint port
S3
HA proxy
Incoming &
Outgoing
HTTPS
9443
Public Data
Network
External IAM
Endpoint port
Lyve Pilot
UDS
Incoming &
Outgoing
TCP/UDP
5000
Public Management
Network
Receive Requests
from Lyve Pilot
DHCP Client
DHCPC
Outgoing
UDP
68
Public Management
Network
Receives IP from
DHCP server
Physical
Rack
1.0M depth, 600mm wide Industry Standard
rack.
HW min U = 7
Rack U = 19 to 48U acceptable
Custom configured or specialized racks
may need a verification check to ensure
HW fit.
Be aware that, If fitted, inward facing
vertical PDUs may cause interference

Page 4of 7Seagate PN 1104485-01_rD
Must be operated with low pressure rear
exhaust installation. Back pressure not to
exceed 5Pa (~0.5mm H20)
with the 5U84 chassis. Please check
clearances and tolerances carefully.
Power
Input Power
Requirements:
Input Power
Requirements:
Max Input
Power:
Heat
Dissipation:
Each Server:
2x 110-120vAC
OR
2x 220-240vAC (750W ea).
5U84 Storage enclosure:
2x 200-240V AC 50-60Hz (2200W ea)
1047W maximum continuous
3572 BTUs/hour
PDUs in rack strongly recommended.
4x C13-NEMA 5-15 1.5M and 4x C13-C14
1.5M cables are provided.
2x C19-C20 1.5M power cords are
provided.
Weights & Dimensions
Servers (2)
Height
Width
Depth
18.6kg / 41lb each
43mm / 1.7”
437mm / 17.2”
754mm / 29.7”
Follow racking instructions carefully.
Refer to Lyve Rack R1 Installation Guide
on www.seagate.com/support/lyve-
rack/installation-guide/ and server
documentation at:
1. Go to
https://www.supermicro.com/
2. Hover over Support, and then
click Manuals.
3. In the Select Category
dropdown list, select
SuperServers.
4. In the Select Product Type
dropdown list, select 1U.
5. Click Submit Request.
6. Locate and refer to the
documents for 1U servers
SYS6019P-WTR or SYS-5019P-
WTR.
5U84
Storage
Enclosure
Empty
Loaded
Height
Width
Depth
64kg / 141lb
135kg / 298lb
222.3mm / 8.75”
444.5mm / 17.5” (w/ear 483mm / 19.01”)
981mm / 38.63”
Follow racking instructions carefully –
See Lyve Rack R1 Installation Guide on
www.seagate.com/support/lyve-
rack/installation-guide/ and Hardware
Installation & Maintenance Guide on
www.seagate.com/support/lyve-
rack/maintenance-guide/
Only fit HDDs after the enclosure is
installed in the rack. Refer the Lyve Rack
R1 Installation Guide for details.
Operating
System
Cent OS 7.8 will be pre-installed during the
manufacturing process.

Page 5of 7Seagate PN 1104485-01_rD
3. Lyve Pilot to CORTX Interface (optional) requirements
Item
Requirement
Comment
Check
Lyve Pilot
Must have a routable connection to the
Management VIP and Data VIP described
in the networking section above.
Make sure you have the link and the
login credentials for Lyve Pilot.
4. CORTX Manager and S3 Client to CORTX Interface requirements
Item
Requirement
Comment
Check
SSL Certificate
CORTX Manager Web interface uses
https to encrypt the web browser traffic.
This is achieved by using a certificate
which can be either a CORTX Manager
self signed certificate or a user provided
certificate, which can be user self signed
or certificate authority (CA) signed
Certificate.
Note: S3 client and the CORTX Manager
uses the same SSL Certificate.
If the CORTX Manager self signed
certificate is used, the user is asked to
accept this self signed certicate upon first
connection to CORTX Manager.
Optionally, the user is provided the
ability to upload a user provided self
signed or user provided certificate
authority (CA) signed Certificate using
CORTX Manager.
5. S3 Client and CORTX Interface requirements
Item
Requirement
Comment
Check
Data VIP (“S3 Endpoint”)
Must have a routable bi-directional
connection to the S3 client(s) in use that
supports all required ports (see list
above).
S3 “Access Key”and “Secret
Key”
S3 Clients require the Access key and
Secret Key to create a signature for S3
Client requests to Lyve Rack R1.
“S3 Account” creation can be performed
by the CORTX “admin” user or a CORTX
“user” with the “manage” role assigned.
“Access Key”and “Secret Key”are
created as a set in CORTX Manager when
a “S3 Account”is created. These are
shown one time and there is an
oportunity to download this credential as
a .csv file. The user creator must store
this information securely as this
information is never shown again,
consistent with industry standards.
The S3 Client can then use this credential
when submitting a S3 Request e.g.
creating a bucket associated with this
credential.
SSL Certificate
S3 Client Requests across https must be
secured with a certificate.The certificate
can be a CORTX Manager provided self
signed certificate, or a user provided self
signed certificate or a user provided
certificate authority (CA) signed
Certificate.
Note: S3 client and the CORTX Manager
uses the same SSL Certificate.
If the CORTX Manager self signed
certifcate is not used by the S3 Client, the
S3 Client can use a self signed or a
certificate authority (CA) signed
certificate providing it has been
previously uploaded to CORTX Manager.
By default AWS CLI verifies SSL
cerificates as being signed by a certificate
authority (CA) when communicating.

Page 6of 7Seagate PN 1104485-01_rD
Using the following option overrides the
verification when self signed certificates
are used or otherwise, the S3 request is
rejected.
“aws --no-verify-ssl"
S3 Signature Version
AWS Signature Version 2 or 4
S3 Client Requests must be signed using
AWS Signature Version 2 or 4.
NTP
Lyve Rack R1 and any S3 Clients must be
time synchronised via a NTP server.
The NTP server address setting for Lyve
Rack R1 is configured in CORTX Manager.
This is then configured on the underlying
Operating System on both servers once
applied via CORTX Manager.
Any S3 Clients attaching to Lyve Rack R1
must also have a NTP server address set
using the underlying Operating System.
Refer to S3 Client underlying Operatiing
System User Guide on how to set up NTP
server address.
The S3 Request has a timestamp
component in the signature to help
prevent third parties from intercepting
the request.

Page 7of 7Seagate PN 1104485-01_rD
6. Example Information Sheet (provided with Lyve Rack R1)