Skip Navigation Links | |
Exit Print View | |
![]() |
Netra Blade X3-2B (formerly Sun Netra X6270 M3 Server Module) Product Notes |
Getting the Newest Firmware and Software
System Hardware and Software Features
Supported Components with Legacy Chassis
Supported Components with New Chassis
FEMs and REMs Required for NEMs
Integrated Lights Out Manager (ILOM)
Hardware, Firmware, and BIOS Issues
Oracle ILOM restore_status Parameter Shows Partial Status (7167938)
Power Reset Event Entry in Oracle ILOM Log is Incorrect (7165042)
Unable to Change Serial Port Ownership Using BIOS Setup Utility (7168093)
PXE-booting Fails When Using Cisco Switch (7149683)
Blade With Solaris 10 8/11 Fails to Bring Up a Supported NEM After Hot Insertion (7121662)
Physical Storage Drives Listed Twice on the Sun Netra 6000 Storage Module M2 (7116807)
Oracle System Assistant Issues
User Must Have Full Administrator Role Privileges to Update SP (7158820)
Some Operating Systems Do Not Mount the Oracle System Assistant USB Device
Oracle System Assistant Does Not Support Username “user”
The Virtual Ethernet Device is Reported as Not Installed in Windows 2008 (7129124)
“Path too Long” Errors When Unzipping Windows Downloads (7116803)
Oracle System Assistant Assisted-OS Installation of SLES 11 Might Prompt for Root Password (7158471)
Unable to Mount Oracle System Assistant USB Device on Some Versions of Linux
Failure Occurs After Hot-Inserting a SAS-2 RAID Module (SGX-SAS6-EM-Z) (7088969)
Too Many PCI Cards or Modules Can Cause the System to Hang (6899040)
RHEL 6.1 kdump Does Not Work (7133869)
Oracle VM and VMware ESXi Issues
Unable to Mount Oracle System Assistant USB Device on Oracle VM 3.0.x (7149878)
Time of Date Incorrect on Oracle VM 3.0 (7061790)
ESXi Cannot Mount the Oracle System Assistant USB Device (7154313)
Oracle Solaris 10 and Solaris 11 OS Issues
Unable to Mount Oracle System Assistant USB Device on Oracle Solaris 10 8/11 OS
Server With Oracle Solaris 10 8/11 Fails to Bring Up hxge After Hot Insertion (7121662)
Xorg GUI Might Fail to Start With Certain Hardware Configurations Under Oracle Solaris 11 (7112301)
Getting Blade Firmware and Software
Firmware and Software Access Options
Available Software Release Packages
Accessing Firmware and Software
Download Firmware and Software Using My Oracle Support
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 blades. Disks that are internal on most blades are connected by a single port and run at a maximum speed of 3Gbs.
Disks located in storage modules are connected with two ports and run at a maximum speed of 6Gbs. 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 blades 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).
Virtual drives must be contained in a single failure domain. The internal Netra Blade X3-2B disks are considered to be a single-failure domain (single-port connections only). One or more Sun Netra 6000 Storage Modules are also considered a single-failure domain. Any virtual drive created on the blade is limited to 4 drives, including the hot-spare drives. The number of virtual drives on Sun Netra 6000 Storage Modules can be up to eight or more drives, depending on the number of Sun Netra 6000 Storage Modules accessible to the blade.
Use dedicated hot-spares only. Do not use global hot-spares unless they cannot be accessed by another failure domain.
Dedicated hot-spares must 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 Netra 6000 Storage Modules. The chassis Zone Manager does not allow you to zone the drives.
Only SAS drives are supported in Netra blades; however, if used in the blade, the SAS drives do not run at full speed and cannot utilize the second port.