About the Installation Procedure
Installation Procedure Overview
About Server Features and Components
Front Panel Status Indicators, Connectors, and Drives
Back Panel Status Indicators, Connectors, and PCIe Slots
Preparing for Server Installation
Tools and Equipment Needed for Installation
Installing the Server Into a Rack
Safety Precautions When Rackmounting the Server
Stabilize the Rack for Installation
Attach Tool-less Slide-Rail Assemblies
Install the Server Into the Slide-Rail Assemblies
Install the Cable Management Arm
Remove the Cable Management Arm
Verify Operation of Slide-Rails and CMA
Rear Cable Connections and Ports
Connect Data Cables to the Server
Connect to Oracle DE2 Disk Shelves
Powering On and Initially Configuring the Server
Power on the Oracle Disk Shelves and Servers
Configure the Primary Network Interface
Troubleshooting Installation Issues
Oracle ILOM Hardware and Interfaces
Logging In to Oracle ILOM Using a Local Serial Connection
Logging In to Oracle ILOM Using a Remote Ethernet Connection
Troubleshooting the Service Processor Connection
Resetting the Service Processor Using Oracle ILOM
Reset the Service Processor From the Server Back Panel
Emergency Server Power Down Using the Power Button
Emergency Server Power Down Using the Oracle ILOM CLI
Emergency Server Power Down Using the Oracle ILOM Web Interface
Use the Oracle ILOM Command-Line Interface to Reset the Server
Use the Oracle ILOM Web Interface to Reset the Server
Technical Support Information Worksheet
Locating the System Serial Number
Getting Server Firmware and Software
Firmware and Software Access Options
Use the following guidelines to ensure a successful clustered environment.
After the system is initially configured, you should lock the management interfaces, which makes them private network interfaces, to enable administration via either server over the network (BUI or CLI) regardless of the cluster state. If interfaces are not locked and cluster takeover occurs, there is no way to access diagnostic information on the failed server because interfaces are taken over by the other server. A locked interface displays a lock icon next to its name in the BUI Configuration > Cluster screen. To lock interfaces, in the BUI, navigate to Configuration > Cluster. In the Resource list, choose the management interface for the server and set it to a private, locked interface by clicking the unlock icon. The interface then displays a lock icon next to its name in the Resource list.
Important: If routes are needed, be sure to create a route on each interface that is assigned to a server.
Each storage pool can be taken over, along with the network interfaces clients use to reach that storage pool, by the cluster peer when takeover occurs.
If you create two storage pools, each server normally provides access to the pool assigned to it. If one of the servers fails, the other server provides clients with access to both pools.
If you create a single pool, the server that is not assigned a pool provides service to clients only when its peer has failed.
Storage pools are assigned to servers at the time of creation; the Storage configuration screen offers the option of creating a pool assigned to each server independently.
If you create two pools, they do not have to be the same size. Any subdivision of storage is permitted.
After completing basic configuration, you can assign resources to each server. Typically, you assign only network interfaces because storage pools are automatically assigned during the storage configuration step.
For more information, especially clustering considerations, see the Oracle ZFS Storage Appliance Administration Guide.