Skip Navigation Links | |
Exit Print View | |
Sun Blade X3-2B (formerly Sun Blade X6270 M3) Administration Guide |
Sun Blade X3-2B Model Name Change
Getting the Latest Firmware and Software
About the User Administration Guide
Planning the System Management Environment
Choosing Tools for Single System Management
Choosing Tools for Multiple System Management
System Management Tools Overview
Common System Management Tasks
Common System Administrative Tasks
Evaluating the Server Environment
Accessing System Management Tools
Access Oracle System Assistant
Access Oracle Hardware Management Pack
Setting Up Oracle System Assistant and Updating the Server
Setting Up Oracle System Assistant
Provisioning the Server for Operation
Oracle System Assistant Administrative Tasks
Troubleshooting and Verifying Oracle System Assistant
Performing Advanced Maintenance, Security, and Configuration Tasks
Setting Up Software and Firmware
Set Up Software and Firmware Using Oracle System Assistant
Set Up Software and Firmware Using Oracle ILOM
Set Up Software and Firmware Using Oracle Hardware Management Pack
Managing Server Policies Using Oracle ILOM
Oracle ILOM Features for x86 Sun Servers
Service Processor Power-On Policies
Power Management Policies Supported
Diagnostics Using Pc-Check and NMI
Switch Serial Port Output to Host Management Console
Back Up and Restore BIOS Configuration
Configure Management Policies Using Oracle ILOM Web Interface
Configure Management Policies Using Oracle ILOM CLI
Creating a RAID Volume Before Installing an Operating System
Creating a RAID Volume After Installing an Operating System
Setting Up the Server With BIOS Setup Utility
Access BIOS Setup Utility Menus
Navigate BIOS Setup Utility Menus
BIOS Setup Utility Menu Overview
Selecting Legacy and UEFI BIOS
Configuring the UEFI BIOS Boot Mode
Selecting Legacy BIOS or UEFI Boot Mode
Configuration Utilities for Add-In Cards
Select UEFI or Legacy BIOS Boot Mode
Common BIOS Setup Utility Tasks
Verify BIOS Factory Default Settings
Legacy BIOS Option ROM Allocation Considerations
Configuring Option ROM Settings
Enable or Disable I/O Resource Allocation
Configuring iSCSI Virtual Drives
BIOS Setup Utility Screen Reference
BIOS UEFI Driver Control Menu Selections
BIOS Save & Exit Menu Selections
BIOS LSI MegaRAID Configuration Utility Screen Reference
Accessing BIOS LSI MegaRAID Configuration Utility Controller Management Menus
BIOS LSI MegaRAID Configuration Utility Controller Management Selections
BIOS LSI MegaRAID Configuration Utility Drive Management Menu Selections
BIOS LSI MegaRAID Configuration Utility Virtual Drive Management Menu Selections
BIOS LSI MegaRAID Configuration Utility Enclosure Management Menu Selections
Identifying Hardware Components and SNMP Messages
Identifying System Hardware Components
System Board Components (Sensors)
Field Replaceable Units (FRUs)
Getting Server Firmware and Software
Firmware and Software Access Options
Available Software Release Packages
Because of the unique architecture of blade servers, there are a number of important things to keep in mind when configuring your disk sub-system. These include both drive type selection (SAS, SSD) and location of these drives in the server modules. Disks that are internal on most server modules are connected by a single port and run at a maximum speed of 3 Gbs.
Disks located in storage modules are connected with two ports and run at a maximum speed of 6 Gbs. Dual port drives provide additional fault tolerance that keep a drive online if the primary port fails. Currently SAS drives support two ports. SATA and SATA SSD drives are single ported.
In consideration of the differences between server modules and drive types, you should take the following into account when configuring your system:
Virtual drives must be composed of drives using the same interface only (for example: SAS only or SATA SSD only).
Virtual drives must be contained in a single failure domain. The internal Sun Blade X3-2B disks are considered to be a single failure domain (single port connections only). One or more Sun Blade 6000 Storage Modules are also considered a single failure domain. Any virtual drive created on the Sun Blade X3-2B is limited to 4 drives, including the hot-spare drives. The number of virtual drives on Sun Blade 6000 Storage Modules can be up to 8 or more drives depending on the number of Sun Blade 6000 Storage Modules accessible to the server module.
Use dedicated hot-spares only. Do not use global hot-spares unless they cannot be accessed by another failure domain.
Dedicated hot-spares should only include drive groups that reside in the same failure domain. Using this method, you can create a "virtual" global hot-spare for any domain.
SATA/SATA-SSD drives are not supported in Sun Blade 6000 Storage Modules. The chassis Zone Manager does not allow you to zone the drives.
Both SAS and SATA drives are supported in Sun Blade X3-2B; however, if used in the server module, the SAS drives do not run at full speed and cannot utilize the second port.
SAS and SATA drives can be mixed in the server module, but not amongst virtual drives. For example you could have a two drive SAS RAID 1 and a two drive SATA-SSD RAID 1 in a Sun Blade X3-2B.