JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Fire X4640 Server Product Documentation     Sun Fire X4640 Server Documentation Library
search filter icon
search icon

Document Information

Using This Documentation

Product Downloads

Get Software and Firmware Downloads

About This Documentation (PDF and HTML)

We Welcome Your Comments

Change History

Hardware Installation and Product Notes

Hardware Installation

Installation Overview

Sun Fire X4640 Server Front and Back Panel Features and Components

Installing the Server Hardware

Removing the Server From the Rack

Cabling and Power

Getting Service for Your Server

Sun Fire X4640 Server Specifications

Managing Your Server

Communicating With the ILOM and the System Console

Setting Up Your Operating System

Product Notes

Overview of the Sun Fire X4640 Server Product Notes

Supported Software and Firmware

Hardware Issues

Solaris Operating System Issues

Linux Operating System Issues

Windows Operating System Issues

VMware ESX and VMware ESXi Issues

Sun Installation Assistant Issues

MegaRAID Storage Manager (MSM) Issues

Integrated Lights Out Manager (ILOM) Issues

BIOS Issues

Documentation Issues

Operating System Installation

Sun Installation Assistant

Introduction to Sun Installation Assistant

Getting Started With Sun Installation Assistant

SIA Version 2.3 Through 2.4 Features and Benefits

SIA Task List

Supported Servers and SIA Media Availability

Supported Operating Systems

Starting SIA and Preparing for Deployment or Recovery Tasks

Local and Remote Media Options

How to Start SIA and Prepare for Tasks Using Local or Remote Media

Configuring RAID

RAID Support Using SIA

How to Create a RAID Volume Using SIA

How to Delete a RAID Volume Using SIA

Installing Windows With SIA

How to Install Windows With SIA Using Local or Remote Media

Installing Linux With SIA

How to Install Linux With SIA Using Local or Remote Media

Using SIA to Upgrade System Firmware

How to Upgrade the System BIOS and ILOM Firmware

How to Upgrade Expander Firmware

How to Upgrade HBA Firmware

Using SIA to Recover a Service Processor

How to Recover a Service Processor

Performing an SIA PXE-Based Attended Installation

Set Up the PXE Infrastructure

Obtain the SIA PXE Image Files

How to Create the SIA Image and Prepare for PXE Boot

How to Boot SIA From a PXE Server for an Attended Installation

Performing an SIA PXE-Based Unattended Installation

Set Up the PXE Infrastructure

Obtain the SIA PXE Image Files

Contents of the SIA State File

How to Prepare for an Unattended SIA Installation of Linux

How to Prepare for an Unattended SIA Installation of Windows Server

How to Prepare for an Unattended SIA Firmware Upgrade

How to Create the SIA Image and Prepare for PXE Boot

How to Boot SIA From a PXE Server and Perform an Unattended Installation

Observing an SIA PXE-Based Unattended Installation

Set Up Passwords for Root and Virtual Access

Using a System Console

Using a Virtual Console or Secure Shell (SSH) Connection

Using a VNC Viewer

How to Establish Connection Using a VNC Viewer

Using a Serial Console

How to Establish a Connection Using a Serial Console

Troubleshooting SIA

SIA Error Messages

SIA Installation Log File

Debugging Unattended Installation Problems

How to Debug a PXE Image That Does Not Boot

Creating a Bootable SIA USB Flash Drive

Requirements

Getting the Software

How to Get the Syslinux and SIA Software

Preparing the USB Flash Drive

How to Prepare the USB Flash Drive on a Windows XP System

How to Prepare the USB Flash Drive on a Linux (Red Hat/SUSE) System

Setting BIOS Parameters and Booting Off the SIA USB Flash Drive

How to Set the BIOS Parameters and Boot Off the SIA USB Flash Drive

Identifying a Linux Boot Device on a Sun Fire X4500 Server

How to Identify a Linux Boot Device on a Sun Fire X4500 Server

Installing Service Tags

How to Install Service Tags in Linux

How to Install Service Tags in Windows

Solaris Operating System

Introduction to Solaris OS and OpenSolaris Installation

Installing the Solaris 10 Operating System

Installing the OpenSolaris Operating System

Booting From OS Distribution Media

Identifying Logical and Physical Network Interface Names for Solaris OS Installation

Preliminary Tasks Before Installing An OS

Linux

Introduction to Linux Installation

Sun Installation Assistant (SIA)

Installing Red Hat Enterprise Linux

Installing and Updating SUSE Linux Enterprise Server

Configuring a Linux Server to Support PXE Installation

Booting From OS Distribution Media

Preliminary Tasks Before Installing An OS

Identifying Logical and Physical Network Interface Names for Linux OS Configuration

Windows

Introduction to Windows Installation

Sun Installation Assistant (SIA)

Getting Started With Windows Server 2008 Installation

Downloading Server Software

Selecting a Media Delivery Method

Configuring a Remote Console

Installing Windows Server 2008

Updating Critical Drivers and Installing Supplemental Software

Incorporating Sun Fire Drivers Into a WIM Image

Identifying Network Interfaces in Windows

ESX

Introduction to ESX Installation

Installing VMware ESX 4

Installing VMware ESXi 4.0 Installable

Booting From OS Distribution Media

Preliminary Tasks Before Installing An OS

Administration, Diagnostics, and Service

Administration Using ILOM

Overview of the ILOM Supplement

Introduction to ILOM Software

Communicating With the ILOM and the System Console

Updating Firmware

Using ILOM to Monitor the Host

Diagnostics

Overview of the Diagnostics Guide

Introduction to System Diagnostics

Troubleshooting the Server

Troubleshooting DIMM Problems

Using the ILOM to Monitor the Host

Using SunVTS Diagnostics Software

Creating a Data Collector Snapshot

Resetting the SP

Service

Sun Fire X4640 Server Service Manual Overview

Controlling Power and Performing Hardware Reset

Removing and Installing Components

Configuring the System Using the BIOS Setup Utilities

Sun Fire X4640 Server References and Specifications

Index

Contents of the SIA State File

The SIA state file provides the scripting variables required for carrying out an unattended session of SIA and performing the specified SIA tasks automatically without user intervention. A copy of the state file with all of the possible parameters can be found at the root level on the SIA CD and is accessible by command prompt during an SIA session.

To access the command prompt from SIA, do the following:

  1. Boot SIA (locally or through the remote console).

  2. At the first screen, press Ctrl-Alt-F2.

    A command prompt will be displayed.

  3. At the command prompt enter the command:

    # cd /root# ls

    Look for the externalStateVariables.txt file.

    The following table describes the state file variables for the automated tasks that may be performed.


    Note - Each variable with its value must be on a separate line in the state file without line breaks. Due to width restrictions in the table below, some examples might show variables breaking across multiple lines.


Table 5 SIA State File Variables

Variable
Description (Defaults in Bold)
Required for Windows Install
Required for Linux Install
Required for Firmware Upgrade
apit.unattended
Tells SIA to run in unattended mode. Values supported: true | false

Example: apit.unattended=true

X
X
X
apit.welcome.acceptlicense
Accepts the SIA license agreement. Values supported: true | false

Example: apit.welcome.acceptlicense=true

X
X
X
apit.remoteUpdate
Tells SIA to look for SIA software updates. You should always perform an update to ensure you install the latest software and firmware. Values supported: true | false

Example: apit.remoteUpdate=true

X
X
X
apit.remoteUpdateURL
If you specified “true” for remoteUpdate, tells SIA where to look for SIA software updates. Values supported: Any URL with updated SIA content files. You only need to specify this variable if you are not using the default url.

Default url: http://sia-updates.sun.com/remoteUpdate

X (if remote Update is true and default url is not used)
X (if remote Update is true and default url is not used)
X (if remote Update is true and default url is not used)
apit.networking
Tells SIA it has permission to work over the network. If true, SIA will configure network settings based on networkconfig variables. Values supported: true | false

Example: apit.networking=true

X
X
X
apit.networkconfig.needNetwork
If you specified “true” for network, tells SIA whether network access is required for a particular task. Values supported: true | false

Example: apit.networkconfig.needNetwork=true

X (if networking is true)
X (if networking is true)
X (if networking is true)
apit.networkconfig.activeNic
If you specified “true” for network, tells SIA which network interface is connected to the active network. Values supported: eth0 | eth1 | eth2 | eth3 ... etc.

Example: apit.networkconfig.activeNic=eth0

X (if networking is true)
X (if networking is true)
X (if networking is true)
apit.networkconfig.NetworkType
If you specified “true” for network, tells SIA the configuration of the active network interface. Values supported: static | dhcp

Example: apit.networkconfig.NetworkType=dhcp

X (if networking is true)
X (if networking is true)
X (if networking is true)
apit.networkconfig.useDHCP
If you selected “dhcp” as the NetworkType, tells SIA to obtain the server’s address from the DHCP server. Values supported: true | false

Example: apit.networkconfig.useDHCP=true

X (if networking is true)
X (if networking is true)
X (if networking is true)
apit.networkconfig.ipfield
If you selected “static” as the NetworkType, tells SIA to use the server’s IP address value you provide.

Example: apit.networkconfig.ipfield=n.n.n.n

X (if static IP is used)
X (if static IP is used)
X (if static IP is used)
apit.networkconfig.gatewayField
If you selected “static” as the NetworkType, tells SIA to use the IP address value you provide.

Example: apit.networkconfig.gatewayfield=n.n.n.n

X (if static IP is used)
X (if static IP is used)
X (if static IP is used)
apit.networkconfig.netmaskedField
If you selected “static” as the NetworkType, tells SIA to use the IP address value you provide.

Example: apit.networkconfig.ipfield=n.n.n.n

X (if static IP is used)
X (if static IP is used)
X (if static IP is used)
apit.http_proxy
If, for example, you specified “true” for remoteUpdate, tells SIA to use a proxy server for internet access.

Examples:

apit.http_proxy=n.n.n.n (IP address)

apit.http_proxy=file://web-proxy-configfile

apit.http_proxy=http://web-proxy-server

apit.http_proxy=http://internal-host:portnumber

X (if proxy used)
X (if proxy used)
X (if proxy used)
apit.taskList.selectedTask
Tells SIA which task to perform (only one task can be run per unattended session). This variable is required in the state file. Values supported: SP/Bios Firmware Upgrade | Operating System Installation | HBA Firmware Upgrade | Expander Firmware Upgrade | SP Recovery

Example: apit.taskList.selectedTask=Operating System Installation

X
X
X
apit.osid.installLoc
Tells SIA where the network image of the Linux operating system to be installed is located. The path is to the directory containing the image (ISO or extracted ISO), not the image itself. The directory cannot contain more than one image.

Example: apit.osid.installLoc=http://path_to_imagedirectory

X
apit.osid.installMedia
Tells SIA where the CD or .iso file for the OS installation software is located. Values supported: cdrom | networkLinux | networkWindows

Example: apit.osid.installMedia=cdrom

X
X
apit.osid.installMethod
Tells SIA which file transfer protocol to use during the installation. Values supported: http | ftp | nfs

Example: apit.osid.installMethod=http

X
X
apit.osid.kickstart
Tells SIA where the kickstart file is located for a Linux installation. This could be the URL to the Red Hat kickstart file or the SUSE autoyast file.

Examples:

apit.osid.kickstart=http://url_to_kickstart

apit.osid.kickstart=ftp://url_to_kickstart

apit.osid.kickstart=nfs://url_to_kickstart

X
apit.windows2008.imageName
Specifies the version of Windows Server 2008 to be installed. Values determine whether this is a full or core–only Windows installation. Core installations allow you to install Windows with only the components needed to run a small set of core network roles. Supported values:
  • WINDOWS LONGHORN [R2] SERVERSTANDARD

  • WINDOWS LONGHORN [R2] SERVERENTERPRISE

  • WINDOWS LONGHORN [R2] SERVERDATACENTER

  • WINDOWS LONGHORN R2 SERVERWEB

  • WINDOWS LONGHORN [R2] SERVERSTANDARDCORE

  • WINDOWS LONGHORN [R2] SERVERENTERPRISECORE

  • WINDOWS LONGHORN [R2] SERVERDATACENTERCORE

  • WINDOWS LONGHORN R2 SERVERWEBCORE

Note: The R2 value is only required for Windows Server 2008 R2. Windows Server 2008 SERVERWEB/CORE is only supported with R2.

Example for pre-R2:

apit.windows2008.imageName=WINDOWS LOGHORN SERVERENTERPRISE

Example for R2:

apit.windows2008.imageName=WINDOWS LONGHORN R2 SERVERENTERPRISE

X (2008 only)
apit.osid.windows.iso.url1
Based on the installMethod you chose (http, ftp or nfs), tells SIA where the location of the first Windows OS install disk .iso image file is located.

Examples:

apit.osid.windows.iso.url1=http://path_to_disk1.iso

apit.osid.windows.iso.url1=ftp://path_to_disk1.iso

apit.osid.windows.iso.url1=nfs://path_to_disk1.iso

X
apit.osid.windows.iso.url2
Based on the installMethod you chose (http, ftp or nfs), tells SIA where the location of the second Windows OS install disk .iso image file is located (if on two disks).

Examples:

apit.osid.windows.iso.url2=http://path_to_disk2.iso

apit.osid.windows.iso.url2=ftp://path_to_disk2.iso

apit.osid.windows.iso.url2=nfs://path_to_disk2.iso

X
apit.enclosureID.oldEnclosureID
Used as part of a two-step process that allows you to replace a Sun Blade 6000 disk module. The value for this variable must be the old enclosure ID number (also called WWN) that can be found on the circuit board of the blade being replaced.
apit.enclosureID.newEnclosureID
Used as part of a two-step process that allows you to replace a Sun Blade 6000 disk module. This value for this variable must be the new enclosure ID number (also called WWN) that can be found on the circuit board of the replacement blade.
apit.firmware.enabled
Tells SIA to enable or disable its firmware update function. Values supported: true | false

Typically used in a test environment, this variable is not required to upgrade firmware.

apit.firmware.spIP
Part of a firmware upgrade task. Tells SIA the IP address of the server’s service processor.

Example: apit.firmware.spIP=n.n.n.n

X
apit.firmware.spPasswd
Part of a firmware upgrade task. Tells SIA the password of the server’s service processor.

Example: apit.firmware.spIP=changeme

X
apit.windows.acceptEula
Tells SIA to accept the EULA (End User License Agreement), as required when installing the Windows OS.

Example: apit.windows.acceptEula

X (2003 only)
apit.windows.adminPasswd
Tells SIA the password you wish to use for the administrator account set up during the installation of the Windows OS. Password must comply with Windows password standards.

Example: apit.windows.adminPasswd=myadminpassword

X (2003 only)
apit.windows.computerName
Tells SIA the computer name you wish to use for the server set up during the installation of the Windows OS.

Example: apit.windows.computerName=mycomputername

X (2003 only)
apit.windows.key
Tells SIA the product key for your retail copy of the Windows OS. Required during Windows installation.

Example: apit.windows.key=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

X (2003 only)
apit.windows.orgName
Tells SIA the organization name you wish to use for the server set up during the installation of the Windows OS.

Example: apit.windows.orgName=myorganization

X (2003 only)
apit.windows.userName
Tells SIA the user name you wish to use for the initial user account set up during the installation of the Windows OS.

Example: apit.windows.userName=myusername

X (2003 only)
apit.done.notifyUrl
Tells SIA to access the specified URL following the completion of enabled SIA tasks. This is currently only supported for Sun N1 System Manager.

Example: apit.done.notifyUrl=http://my_destination_url