1. Payloads Network Attached Storage (NAS) for International Space Station (ISS)
Sponsoring Org/Office Code: MSFC/EO30
Name of Forum: POIWG
Date: 07/21/2015

2. Agenda Describe Payloads NAS Capability
Examples of how Payloads can use the NAS
Implementation Phases

3. Payloads NAS Capability
The Payloads NAS is a file server developed by Quality Network Appliance Provider (QNAP)
There will be a total of two NASs
Systems NAS (SSC NAS) resides on the OPS LAN
Payloads NAS resides on the Payload LAN
Currently the NAS hardware is scheduled to be located in the USL near LAB1D1 or Aft Bulkhead with network connections to PEHG 1 and 2
See Appendix 1 and 2 for more details
Communication between the ground and the NAS takes place through the Ku IP Service (Ku Forward)
The NAS has 5 hard drive bays that provides a total of 20 terabytes of raw disk space when used with 4 terabyte hard drives
The drives are swappable and redundant when used in a RAID 6 (Redundant Array of Independent Disks) configuration making the usable storage ≈ terabytes for Payload use
RAID 6 allows the NAS to function in a degraded state (read-only) on 3 hard drives if 2 have failed

4. Payloads NAS Capability (cont.)
The NAS provides the following methods for data storage and retrieval.
HTTPS Session
Allows users to transfer files from their machine via a web browser (IE, Firefox, etc.)
Users can also RDP from an onboard system and use the HTTPS interface
Internet Small Computer System Interface (iSCSI) Protocol by onboard Payloads
Storage space made available over an IP Network
Microsoft Networking or NFS (LINUX) by onboard Payloads
Allows onboard systems to access a shared folder location on the NAS
The NAS also has a USB One Touch Copy function
Copies an entire USB Flash Drive, inserted by the Crew, onto the NAS
POIF Cadre member will have access to the USB One Touch volume to downlink this data

5. Payloads NAS Capability (cont.) QNAP TS-569L Specifications
Model
TS-569L
Segment
Home/SOHO OS
Embedded Linux
CPU
Intel® Atom™ 2.13 GHz (Dual-Core)
Memory
1GB RAM
Flash
512MB (DOM)
Max. number of HDDs/SSDs supported
5 x 2.5" or 3.5” SATA 3Gb/s
Gigabit LAN Ports 2
LED Indicators
HDD 1-5, Status, LAN, USB, eSATA, Power
LCD Display/ Button -
Buttons
Power, Reset, USB Auto Copy
Dimensions (DxWxH) mm
185 x x 235.5
Weight (Net/ Gross) kg
4.2kg/ 5.6kg
Temperature °C
Humidity
0 - 90% R.H
Power Supply Specification
ATX 250W, Input: Vac~, 50-60Hz, 5A
Power Consumption: Sleep Mode
29.1W
Power Consumption: In Operation
48.5W

6. Provide some examples of how Payloads can use the NAS
HTTPS session through the HPEG to login and transfer files from that local machine to the NAS onboard
Payloads can also Remote Desktop Protocol (RDP) from an on board system and use the https interface for file transfers

7. Provide some examples of how Payloads can use the NAS
What is iSCSI?: Simply put, it’s storage that is made available over an IP network to payloads
Payloads can use the NAS to increase the storage capacity of an onboard system using iSCSI protocol
The data stored can only be retrieved from the device with the iSCSI target or initiator

8. Provide some examples of how Payloads can use the NAS
Payload can map directly to an assigned shared folder on the NAS using Microsoft Networking or NFS for LINUX systems
The user can then perform file transfers and access the data simultaneously with an active https session

9. Provide some examples of how Payloads can use the NAS
USB One Touch Copy
Copies an entire USB Flash Drive, inserted by the Crew, on to the NAS
Files can then be downlinked or moved to another folder location on the NAS

10. Payload NAS Implementation Phases
Payloads NAS is currently scheduled for Orbital 4 December 2015
Phase I NET ~ January 2016 (The install date is not determined.)
POIC Cadre use of the Payload NAS
DMC NAS Specialist
Setup the Payload Configuration
Perform file transfers
Create PRO user account
Utilize NAS as a boot device
Preboot eXecution Environment (PXE)
Trivial File Transfer Protocol (TFTP)
Payload Rack Officer (PRO)
RDP into an Express Laptop and access the NAS
Upload Payload Application Files to the NAS via the Ku IP Service
Transfer Payload Application Files from the NAS to the EXPRESS Laptop
Save Crew Time
Map to a shared folder on the NAS

11. Payload NAS Implementation Phases
Payload Users should request Payloads NAS use as a part of their Payload Integration Agreement (PIA)
Phase II ~ April Tentative
Create Payload accounts on the NAS
The following Payloads have expressed interest in using the Payloads NAS: MSG, AMS, SAMS, Cold Atom Lab (CAL), TReK, and BioChip
Phase III ~ May 2016 Tentative
Full use of the NAS to the Payload Community
Including International Payloads with access to the Payload LAN

12. Acronyms CDP CCSDS Data Processor EHS Enhanced HOSC System
eFDP external Functional Data Processor
EXPRESS Expedite the Processsing of Experiments to Space Station
ePVT external PriVaTe LAN
HPEG HOSC Payload Ethernet Gateway
HRDL High Rate Data Link
HTTPS Hypertext Transfer Protocol Secure
IP Internet Protocol
JSL Joint Station LAN
LAN Local Area Network
NET No Earlier Than
PD Payload Developer
PEHG Payload Ethernet Hub Gateway
PIA Payload Integration Agreement
PDSS Payload Data System Services
RDP Remote Desktop Protocol
SGTRC Space to ground transmit Receive Controller
TBD To Be Determined
WSC White Sands Complex

13. Appendix 1

14. Appendix 2

15. Back-up Charts

16. Payloads NAS Connectivity
User Actions for HTTPS Session from ground
Authenticates to EHS
If authorized for Ku IP Service, user will connect to the HOSC Payload Ethernet Gateway (HPEG)
A list of user destinations and their respective protocols is returned to the user interface
User will select Payloads NAS destination and start the session
Using the Proxy IP Address returned the user will input the address into a web browser and log into the NAS
Sessions are preserved across LOS windows
When finished user will stop session
HPEG checks for inactivity and will prompt user to reply. No reply will lead to a disconnect from HPEG
Data Downlink
Data Uplink