JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Server CLI Tools and IPMItool 2.1 User's Guide
search filter icon
search icon

Document Information

Preface

Documentation and Feedback

About This Documentation (PDF and HTML)

Change History

Oracle Hardware CLI Tools Overview

Installing Components Using the Oracle Hardware Management Pack Installer

Getting Started

Prerequisites

Installation Issues

Getting the Software

Installing Hardware Management Pack Components Using Installer

CLI Tools Command Syntax and Conventions

CLI Tools Command Syntax

CLI Tools Device-Naming Convention

Using the biosconfig Tool

biosconfig Dependencies

biosconfig Terminology

Using biosconfig

biosconfig for Solaris OS

biosconfig for Windows

biosconfig Command Overview

What Changes the Boot List

Important Notes on Devices

Configuring the Device Boot Order

BIOS CMOS Configuration

Commands That Produce Unrelated, Innocuous, Extra Output

Using the fwupdate Tool

fwupdate Command-Line Interface

update Subcommand

list Subcommand

reset Subcommand

Device-Naming Convention

Execution Summary

Using the raidconfig Tool

raidconfig Overview

raidconfig Command Overview

list Subcommand

create raid Subcommand

delete raid Subcommand

add spare Subcommand

remove spare Subcommand and Options

modify Subcommand

export Subcommand

raidconfig export Options

import Subcommand

Using the ilomconfig Tool

ilomconfig Overview

ilomconfig Commands

Using ipmitool for Windows

ipmitool Overview

Sun IPMI System Management Driver 2.1

Using ipmitool for Configuration Tasks

CLI Tools Error Codes

Common Error Codes

biosconfig Error Codes

raidconfig Error Codes

ilomconfig Error Codes

fwupdate Error Codes

Index

biosconfig Dependencies

You must run biosconfig as root (Linux, Solaris) or Administrator (Windows) because it needs to use drivers that are in read— and write-protected physical address space.

For more on biosconfig for Solaris, see: biosconfig for Solaris OS.

Linux versions of biosconfig also depend on access to /dev/nvram to guarantee serialized access to the CMOS. RHEL4 distributions do not seem to include this device by default, RHEL5 and SLES do. For you to use /dev/nvram, the driver needs to be compiled into the kernel (or loaded as a module), and /dev/nvram must exist (root can create it using mknod /dev/nvram c 10 144).

For information on biosconfig for Windows, see: biosconfig for Windows.

See also: