JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Server X2-8 (formerly Sun Fire X4800 M2) Installation Guide     Sun Server X2-8 (formerly Sun Fire X4800 M2) Documentation Library
search filter icon
search icon

Document Information

Using This Documentation

Sun Server X2-8 Name Change

Product Downloads

Documentation and Feedback

About This Documentation

Change History

Installation Overview

Front and Back Features and Components

Front Features and Components

Back Features and Components

Unpacking the Server and Identifying the Rack Mounting Hardware

How to Identify Your Rack Mounting Kit

How to Unpack the Server

Installing the Server In the Rack Using the Standard Rack Mounting Kit

Tools and Staff Required

Installing Optional Equipment

Compatible Racks

Contents of the Standard Rack Mounting Kit

Location of the Rack Mounting Kit and the Shipping Bracket Kit

Installing the Server In a Rack Using the Standard Rack Mounting Kit

Removing and Installing the Standard Rack Mounting Kit Shipping Brackets

Installing the Server in the Rack Using the Universal Rack Mounting Kit

Tools and Staff Required

Installing Optional Equipment

Compatible Racks

Contents of the Universal Rack Mounting Kit

Installing the Server in a Rack Using the Universal Rack Mounting Kit

Installing and Removing the Universal Shipping Brackets

Removing the Server from the Rack

How to Remove the Server from the Rack

How to Remove the Rackmounting Hardware from the Rack

Cabling and Power

Attaching Administration (SP) Cables

Cabling NEMs and PCIe EMs

Powering the Server On and Off

Getting Service for Your Server

How to Find the Server's Serial Number

Determining Your Server Management Strategy

Oracle Integrated Lights Out Manager

Oracle Hardware Management Pack

Oracle Hardware Installation Assistant

Configuring the Preinstalled Solaris Operating System

Configuring the Preinstalled Oracle Solaris OS

Installation Worksheet

How to Connect to the Server Using the Server's IP Address

(Optional) How to Redirect the Console Output to the Video Port

How to Connect to the Server Using a Serial Capture Program

Oracle Solaris OS Information Products and Training

Configuring the Preinstalled Oracle Linux Operating System

Oracle Linux Configuration Worksheet

Configure the Preinstalled Oracle Linux OS

Register and Update Your Oracle Linux OS

Configuring the Preinstalled Oracle VM Software

How to Configure Oracle VM

Configuration Worksheets

Getting Started With Oracle VM

Communicating With Oracle ILOM and the System Console

Server Connections

About Oracle ILOM SP IP Addresses and the Oracle ILOM Interfaces

Determining the SP IP Address

Connecting to Oracle ILOM

Connecting to the System Console

I/O and Interrupt Resource Allocation

Option ROM and I/O Space Allocation

How to Determine Whether You Need to Allocate Option ROM and I/O Space

How to Configure Option ROM and I/O Space Allocation

Allocating MSI Interrupt Space (Oracle Solaris OS Only)

How to Identify and Fix Interrupt Resource Shortages

Sun Server X2-8 Specifications

Physical Specifications for the Sun Server X2-8

Power Specifications for the Sun Server X2-8

Environmental Specifications

Acoustic Specifications

Requesting Physical Media

How to Request Physical Media Online

How To Request Physical Media by Phone

Index

How to Determine Whether You Need to Allocate Option ROM and I/O Space

If you add a PCIe express module or a fabric expansion module to an eight-socket system (with CPU modules in all four slots), when the system boots, the BIOS might not be able to allocate option ROM or I/O space to all the devices that require it.

If this happens, when you boot, POST generates error messages. These identify any devices that have not had option ROM or I/O space allocated.

  1. Power on the system to start the BIOS.
  2. During POST, look for one or more messages, such as these.
    • For option ROM, the messages look like this:

      Warning: Out of option ROM space for device EM0.1 [04:00:01]
    • For I/O space, the messages look like this:

      Warning: Not enough IO address space allocated for device EM0.0 [0A:00:01]
      Warning: Not enough IO address space allocated for device EM0.0 [0A:00:00]
      Warning: Not enough IO address space allocated for device EM0.1 [05:00:01]
      Warning: Not enough IO address space allocated for device EM0.1 [05:00:00]
      Warning: Not enough IO address space allocated for device EM0.1 [04:00:01]
      Warning: Not enough IO address space allocated for device EM0.1 [04:00:00]

    Each slot can generate several messages. This is normal.

    It is possible that the device you added has been assigned option ROM and/or I/O space at the expense of some other device. If this is the case, the device you added does not appear in the list, but the original device does. This depends on the position of each device in the probe order.

  3. Decide whether you need to configure option ROM or I/O space allocation for one of the following reasons.
    • Error messages inform you that a device that you wish boot from has not been allocated option ROM and/or I/O space.

    • You wish to be able to run a configuration utility such as the LSI RAID utility on a device that has not been allocated option ROM.

    • (Optional) You wish to make the error messages go away.


      Note - There is no need to configure option ROM or I/O space allocation simply because of these messages, unless you require the functionality provided by the option ROM and the I/O space.


See Also

How to Configure Option ROM and I/O Space Allocation