System Components

An Oracle Flash Storage System consists of Pilots, Controllers, and Drive Enclosures. Replication Engines can also be added to the system for replication purposes.

The following table summarizes the components that comprise the Oracle FS System along with their model name, quantity, and description.

Table 1 Oracle FS System component descriptions
Component name	Model	Quantity and description
Pilot	1U	An Oracle FS System supports two Pilot management controllers. The Pilot nodes are designated as Pilot-1 and Pilot-2. One Pilot node actively performs management functions while the other Pilot node is in standby mode. The Pilot in an Oracle FS System operates separately from the user data and the command paths and thus provides out-of-band management.
Controllers	2U	An Oracle FS1-2 supports two storage Controllers. The Controllers are designated as Controller-1 and Controller-2. Both Controllers actively process I/O on the data path. Note: Controllers are identified in the CLI as CONTROLLER-01, CONTROLLER-02 and in the Oracle FS System Manager as CONTROLLER 01, CONTROLLER 02.
Drive Enclosures	DE2-24P (2U), 24 SFF, 2.5 inches (6.35 centimeters) SAS-2 drives or 7, 13, 19 SSDs for each Drive Enclosure DE2-24C (4U), 24 LFF, 3.5 inches (8.89 centimeters) SAS-2 drives	An Oracle FS1-2 supports between 1- 30 Drive Enclosures. Both DE2-24P and DE2-24C can coexist in the same system.
MaxRep Replication Engines (optional)	2U	An Oracle FS System supports a total of eight Replication Engines. The number of Replication Engines depends on customer requirements and the type of replication. While a single engine is sufficient for replication, Oracle recommends having at least two engines for redundancy purposes.
Filler panels (optional)	1U 2U	The number of filler panels depends on how many empty rack unit (RU) slots exist in the rack.
Power distribution units (PDUs)	Unless using Oracle PDUs, PDUs are the responsibility of the customer or third party rack vendor.	Oracle PDUs are integrated into the rack. Non-Oracle PDUs might or might not be integrated into the rack.
Racks	Standard four-post racks (42U).	The number of racks depends on the number and the distribution of the hardware components. A minimum of 1 rack and a maximum of 4 racks can be used.

The PDUs used in a not-racked Oracle FS System installation must provide redundancy for both external AC power source and internal AC power distribution to the components. The PDUs must provide sufficient current to meet the sum of the requirements for the Oracle FS System components.

Oracle PDUs might be purchased for use with non-Oracle racks. The Oracle FS System component power cords have been designed to work with vertical style Oracle or third party PDUs. Non-Oracle PDUs must be compatible with Oracle component power cord lengths and plug types. Non-Oracle PDUs must be mounted in a manner such that the power cords provided by Oracle might be used and the PDUs do not obstruct the ability to replace field replaceable units (FRUs) and customer serviceable units (CRUs).

While planning rack-space, ensure that adequate space is also allocated for the PDUs, if using non-Oracle PDUs.

Note: Typically, enterprise class products like the Oracle FS System do not use a UPS and rely on generator backed power supply in the data centers. However, if you use a UPS, it must be based on the maximum wattage requirements of the sum total of all the Oracle FS System components. The UPS, if used, should conform to the APC PowerNet MIB specifications so that it can send SNMP traps to the Oracle FS System to indicate that it is operating in battery mode or in normal mode and that the Oracle FS System should be configured to receive the traps. For more information about managing APC products that can be monitored and configured with SNMP, see the Schneider Electric MIB Reference Guide (http://www.apcmedia.com/salestools/JGAY-83UPH9/JGAY-83UPH9_R0_EN.pdf). In short, a UPS system must be based on the maximum wattage requirements of the sum total of all the Oracle FS System components.