Oracle SPARC, Netra SPARC Administration Manual

Download

Page 1

SPARC and Netra SPARC T5 Series Servers Administration Guide

Part No: E29502-10

August 2016

Page 2

Page 3

SPARC and Netra SPARC T5 Series Servers Administration Guide

Part No: E29502-10

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS. Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?

ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Page 4

Référence: E29502-10

Ce logiciel et la documentation qui l’accompagne sont protégés par les lois sur la propriété intellectuelle. Ils sont concédés sous licence et soumis à des restrictions d’utilisation et de divulgation. Sauf stipulation expresse de votre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire, diffuser, modifier, breveter, transmettre, distribuer, exposer, exécuter, publier ou afficher le logiciel, même partiellement, sous quelque forme et par quelque procédé que ce soit. Par ailleurs, il est interdit de procéder à toute ingénierie inverse du logiciel, de le désassembler ou de le décompiler, excepté à des fins d’interopérabilité avec des logiciels tiers ou tel que prescrit par la loi.

Les informations fournies dans ce document sont susceptibles de modification sans préavis. Par ailleurs, Oracle Corporation ne garantit pas qu’elles soient exemptes d’erreurs et vous invite, le cas échéant, à lui en faire part par écrit.

Si ce logiciel, ou la documentation qui l’accompagne, est concédé sous licence au Gouvernement des Etats-Unis, ou à toute entité qui délivre la licence de ce logiciel ou l’utilise pour le compte du Gouvernement des Etats-Unis, la notice suivante s’applique:

Ce logiciel ou matériel a été développé pour un usage général dans le cadre d’applications de gestion des informations. Ce logiciel ou matériel n’est pas conçu ni n’est destiné à être utilisé dans des applications à risque, notamment dans des applications pouvant causer des dommages corporels. Si vous utilisez ce logiciel ou matériel dans le cadre d’ applications dangereuses, il est de votre responsabilité de prendre toutes les mesures de secours, de sauvegarde, de redondance et autres mesures nécessaires à son utilisation dans des conditions optimales de sécurité. Oracle Corporation et ses affiliés déclinent toute responsabilité quant aux dommages causés par l’utilisation de ce logiciel ou matériel pour ce type d’applications.

Oracle et Java sont des marques déposées d’Oracle Corporation et/ou de ses affiliés. Tout autre nom mentionné peut correspondre à des marques appartenant à d’autres propriétaires qu’Oracle.

Intel et Intel Xeon sont des marques ou des marques déposées d’Intel Corporation. Toutes les marques SPARC sont utilisées sous licence et sont des marques ou des marques déposées de SPARC International, Inc. AMD, Opteron, le logo AMD et le logo AMD Opteron sont des marques ou des marques déposées d’Advanced Micro Devices. UNIX est une marque déposée d’The Open Group.

Ce logiciel ou matériel et la documentation qui l’accompagne peuvent fournir des informations ou des liens donnant accès à des contenus, des produits et des services émanant de tiers. Oracle Corporation et ses affiliés déclinent toute responsabilité ou garantie expresse quant aux contenus, produits ou services émanant de tiers, sauf mention contraire stipulée dans un contrat entre vous et Oracle. En aucun cas, Oracle Corporation et ses affiliés ne sauraient être tenus pour responsables des pertes subies, des coûts occasionnés ou des dommages causés par l’accès à des contenus, produits ou services tiers, ou à leur utilisation, sauf mention contraire stipulée dans un contrat entre vous et Oracle.

Accessibilité de la documentation

Pour plus d’informations sur l’engagement d’Oracle pour l’accessibilité à la documentation, visitez le site Web Oracle Accessibility Program, à l'adresse http://www.oracle.com/

pls/topic/lookup?ctx=acc&id=docacc.

Accès au support électronique

Les clients Oracle qui ont souscrit un contrat de support ont accès au support électronique via My Oracle Support. Pour plus d'informations, visitez le site http://www.oracle.com/

pls/topic/lookup?ctx=acc&id=info ou le site http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs si vous êtes malentendant.

Page 5

Using This Documentation ................................... .............................................. 9

Product Documentation Library . ..................................................................... ... 9

Feedback ................................... .................................................................... 9

Understanding System Administration Resources ........................................... 11

Oracle ILOM Overview .............................................. .................................... 11

Oracle Solaris OS Overview ......................................... .................... ............... 12

OpenBoot Overview ................................................................ ...................... 13

Oracle VM Server for SPARC Overview ......................... .................................. 13

Multipathing Software Overview ................................ .................... .................. 14

Oracle Hardware Management Pack Overview ................................................... 15

Oracle Enterprise Manager Ops Center Overview .............................. .................. 16

Accessing the Server .. ..................................................................... ................. 17

▼ Log In to Oracle ILOM ................ ............................................................. 17

▼ Log In to the System Console ................................ .................... ................ 18

▼ Obtain the OpenBoot Prompt Under Various Conditions ................... ............... 19

▼ Display the Oracle ILOM Prompt ................ ............................................... 20

▼ Redirect the System Console to a Local Graphics Monitor ............................... 21

Oracle ILOM Remote Console ............................................................... ......... 22

Controlling the Server .......................................... .................... ......................... 23

Powering the Server On and Off .............................................. ........................ 23

▼ Power On the Server (Oracle ILOM CLI) .................................... ......... 24

▼ Power Off the Server (Oracle ILOM CLI) ............................... ............. 24

▼ Power On the Server (Oracle ILOM Web Interface) ....................... ......... 25

▼ Power Off the Server (Oracle ILOM Web Interface) ............................... 26

Page 6

Contents

▼ Power On a Server With Multiple Active Domains (Oracle VM Server for

SPARC) ........................ ..................................................................... .. 27

▼ Power Off a Server With Multiple Active Domains (Oracle VM Server for

SPARC) ........................ ..................................................................... .. 28

Resetting the Server and SP ... .................... ..................................................... 29

▼ Reset the Server (Oracle Solaris) ........................................................ 30

▼ Reset the Server (Oracle ILOM) ......................................................... 30

▼ Reset the SP ............................. ....................................................... 31

Booting and Shutting Down the OS ................................... ............................... 33

Booting and Shutting Down Oracle Solaris ........................................................ 33

Boot Sequence ................................. ..................................................... 34

▼ Boot the OS (Oracle ILOM) .............................. ................................ 35

▼ Boot the OS Manually (OpenBoot) ...................................................... 35

▼ Shut Down the OS (init Command) ................ ................................... 36

▼ Shut Down the OS (shutdown Command) ........ ..................................... 37

Obtaining the OpenBoot Prompt ............................................. ......................... 38

OpenBoot Prompt ............................................ ...................................... 38

▼ Obtain the OpenBoot Prompt (Oracle Solaris) ....................................... 39

▼ Obtain the OpenBoot Prompt (Oracle ILOM CLI) .................... .............. 40

▼ Obtain the OpenBoot Prompt (Oracle ILOM Web Interface) ..................... 41

Configuring Boot and Restart Behavior ..................................... .................... ... 43

Configuring Boot Parameters .......... ................................................................. 43

▼ Change the Default Boot Device (OpenBoot) ................ .................... .... 44

▼ Enable or Disable Automatic Booting (OpenBoot) .................................. 45

▼ Enable or Disable Automatic Booting (Oracle Solaris) ............ ................ 46

▼ View All OpenBoot Parameters ............... ........................................... 47

OpenBoot Configuration Parameters ........................................................ . 47

printenv Output .... ..................................................................... .......... 48

Boot Mode Overview (Oracle ILOM) ...... ......................................................... 49

▼ Configure the Host Boot Mode (Oracle VM Server for SPARC) ........................ 50

▼ Change the Host Boot Mode Behavior at Reset (Oracle ILOM) ................. ........ 51

▼ Manage the Host Boot Mode Script (Oracle ILOM) ........................................ 51

▼ Display the Host Boot Mode Expiration Date (Oracle ILOM) ........................... 52

▼ Override OpenBoot Settings to Reset the Server .... ........................................ 52

Server Restart Behavior Configuration (Oracle ILOM) ......... ................................ 53

6 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 7

Contents

Changing Server Identification Information .......................... ............................ 55

▼ Change Customer Data on FRU PROMs ....... .................... ........................... 55

▼ Change Server Identifier Information .................................... ....................... 56

Configuring Policy Settings ................. ............................................................. 57

▼ Specify Cooldown Mode .............. ............................................................. 57

▼ Restore the Host Power State at Restart ................................................... .... 58

▼ Specify the Host Power State at Restart ................................................... .... 59

▼ Disable or Reenable the Host Power-On Delay .............................................. 59

▼ Specify Parallel Boot of the SP and Host ... .................... ............................... 60

▼ Specify Host Virtual Keyswitch Behavior ............................................ ......... 61

▼ Reset the Values in the SP to Default Values ......... .................... .................... 61

Configuring SP and Host Network Addresses ................................... ............... 63

SP Network Address Options .................................................... ...................... 63

▼ Disable or Reenable Network Access to the SP ..................... ......................... 64

▼ Display the SP Network Parameters .................... .................... .................... 64

▼ Display the Host MAC Address ................................ .................... .............. 65

Connecting to the SP (In-band) ........................... .................... ......................... 65

Oracle ILOM In-band (Sideband) Management ................................. .......... 66

▼ Configure SP In-band (Sideband) Access .............................................. 67

Matching Devices to Device Names ............................... ................................... 69

Importance of Matching a Physical Device to a Name ....................................... ... 69

WWN Syntax .......................................... .................... ................................. 70

▼ Display Server Components (Oracle ILOM) .................................... .............. 71

▼ Locate Device Paths (OpenBoot) ....................................... .................... ..... 72

▼ Correlate WWN Device Names With Physical Locations (diskinfo

Command) ................................... ................................................................ 72

probe-scsi-all Device Naming (OpenBoot) ................................................ ..... 74

▼ Correlate WWN Device Names With Physical Locations (probe-scsi-all

Command) ................................... ................................................................ 75

▼ Identify a Disk Slot (Oracle Solaris) ................. ........................................... 76

WWN Syntax in an Oracle Solaris 10 Installation on an Individual Drive ................. 78

WWN Syntax in an Oracle Solaris 10 Installation on a RAID Volume ..................... 79

Page 8

Contents

Configuring Hardware RAID ................. ............................................................. 81

Hardware RAID Support ................. ............................................................... 81

FCode-Based RAID Utility .......... ........................................................... 82

sas2ircu Utility .... ..................................................................... ........... 82

raidconfig Commands .............................................. ............................ 83

RAID Capabilities in Oracle Enterprise Manager Ops Center ......................... 83

Hardware RAID Guidelines ................... ......................................................... 84

FCode-Based RAID Utility Commands ...................... .................... ................... 84

▼ Prepare to Create a RAID Hardware Volume (FCode-based RAID Utility) .......... 85

▼ Create a Hardware RAID Volume ............. .................................................. 86

Hot-Spare Drives in RAID Volumes (LSI) ....................................................... .. 88

Determining if a Drive Has Failed ....................................................... ............. 88

Service Required Drive LEDs ......................... .................... ..................... 89

▼ Locate Error Messages Related to Drives in a RAID Volume .................... 89

▼ Display Status (FCode-Based RAID Utility) .... ...................................... 90

▼ Display Status (sas2ircu Utility, LSI) ................................................. 91

RAID Drive Replacement Strategies ................................................. ................ 91

Monitoring the Server ...................... ................................................................. 93

▼ Turn On the Locator LED ................................................ ......................... 93

▼ Turn Off the Locator LED ....................... .................................................. 94

▼ Display the Locator LED State of the Server .... ............................................. 94

Updating the Firmware ............. ..................................................................... .... 97

▼ Display the Firmware Versions ................... ................................................ 97

▼ Update the Firmware .................................................................... ............ 98

Glossary ................................... ..................................................................... .... 99

Index ................................... ..................................................................... ........ 105

8 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 9

Using This Documentation

■

Overview – Describes how to configure and administer the SPARC and Netra SPARC T5series servers and server modules from Oracle.

■

Audience – System administrators of SPARC and Netra SPARC T5-series servers and server modules.

■

Required knowledge – Working knowledge of computer network concepts and terms, and advanced familiarity with the Oracle Solaris Operating System (Oracle Solaris OS).

Product Documentation Library

Documentation and resources for this product and related products are available at http://

www.oracle.com/technetwork/documentation/oracle-sparc-ent-servers-189996.html or http://www.oracle.com/goto/nebs-certified-systems/docs.

Feedback

Provide feedback about this documentation at http://www.oracle.com/goto/docfeedback.

Using This Documentation 9

Page 10

10 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 11

Understanding System Administration Resources

These topics provide a summary of common tools used to administer the server.

■

“Oracle ILOM Overview” on page 11

■

“Oracle Solaris OS Overview” on page 12

■

“OpenBoot Overview” on page 13

■

“Oracle VM Server for SPARC Overview” on page 13

■

“Multipathing Software Overview” on page 14

■

“Oracle Hardware Management Pack Overview” on page 15

Related Information

■

“Updating the Firmware” on page 97

Oracle ILOM Overview

Oracle ILOM is system management firmware that is preinstalled on most servers from Oracle. Oracle ILOM enables you to actively manage and monitor components installed in the server. Oracle ILOM provides a browser-based interface and a CLI, as well as SNMP and IPMI interfaces.

In the server's SP, Oracle ILOM runs independently of the server host and regardless of the server power state as long as AC power is connected to the server (or to the modular system that contains the server module). When you connect the server to AC power, the SP immediately starts up and begins monitoring the server. All environmental monitoring and control are handled by Oracle ILOM.

The -> prompt indicates that you are interacting with the Oracle ILOM SP directly. This prompt is the first prompt you see when you log in to the server through the SER MGT port or NET

Understanding System Administration Resources 11

Page 12

Oracle Solaris OS Overview

MGT port, regardless of the host's power state. On a modular system, that prompt is also present when you log in to a server module either directly or through Oracle ILOM on the CMM of the modular system.

You can also access the Oracle ILOM prompt (->) from the OpenBoot ok prompt.

The SP supports concurrent Oracle ILOM sessions per server. Multiple SSH or web connections are available through the NET MGT port, and one connection is available through the SER MGT port.

For more information about how to work with Oracle ILOM features that are common to all platforms managed by Oracle ILOM, refer to the Oracle ILOM documentation at:

http://www.oracle.com/goto/ilom/docs

Oracle ILOM operates on many platforms, supporting features that are common to all platforms. Some Oracle ILOM features belong to only a subset of platforms. For example, CMM features only apply to server modules, such as the SPARC and Netra SPARC T5-1B server modules.

To perform some procedures documented in the Oracle ILOM base documentation, you must create a serial connection to the server and activate the Physical Presence switch on the server. For information about creating a serial connection, refer to the installation guide for the server.

Related Information

■

“Log In to Oracle ILOM” on page 17

■

“Configuring Policy Settings” on page 57

■

“OpenBoot Overview” on page 13

Oracle Solaris OS Overview

The Oracle Solaris OS includes commands and other software resources to use for server administration. For an introduction to these management tools refer to one of the following manuals in the documentation collection for your Oracle Solaris OS release:

■

Oracle Solaris 11 OS – Oracle Solaris Administration: Common Tasks

■

Oracle Solaris 10 OS – Oracle Solaris Administration: Basic Administration

Oracle Solaris software includes Oracle VTS software. Oracle VTS tests and validates Oracle hardware by verifying the connectivity and functionality of hardware devices, controllers, and peripherals.

12 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 13

In addition to the Oracle VTS information in the Oracle Solaris documentation, Oracle VTS documentation collections are available at:

http://www.oracle.com/goto/vts/docs

Related Information

■

“OpenBoot Overview” on page 13

OpenBoot Overview

The OpenBoot firmware starts the OS, validates installed hardware, and can be used for other server administration tasks below the OS level. Some devices contain firmware written in the FCode language that enable additional commands that can be entered at the OpenBoot prompt (ok).

For more details about OpenBoot, refer to the OpenBoot 4.x Command Reference Manual at:

OpenBoot Overview

http://docs.oracle.com/cd/E23824_01

Related Information

■

“Oracle Solaris OS Overview” on page 12

Oracle VM Server for SPARC Overview

A logical domain is a discrete logical grouping with its own operating systems, resources, and identity within a single computer system. Application software can run in logical domains. Each logical domain can be created, destroyed, reconfigured, and rebooted independently.

Oracle VM Server for SPARC software enables you to create and manage numerous logical domains on a server, depending on the hardware configuration of the server. You can virtualize resources and define network, storage, and other I/O devices as services that can be shared between domains.

The Oracle VM Server for SPARC configurations are stored on the SP. Using Oracle VM Server for SPARC CLI commands, you can add a configuration, list the configurations on the

Understanding System Administration Resources 13

Page 14

Multipathing Software Overview

SP, and specify a configuration to be used. You can also specify an Oracle VM Server boot configuration with an Oracle ILOM command, as explained in “Configure the Host Boot Mode

(Oracle VM Server for SPARC)” on page 50.

Oracle VM Server for SPARC is included in Oracle Solaris 11.1. If you use Oracle Enterprise Manager Ops Center, you can provision that management environment with a version of Oracle VM Server for SPARC that is compatible with your hardware.

Related Information

■

Oracle VM Server for SPARC documentation at:

http://www.oracle.com/goto/vm-sparc/docs

■

“Oracle Enterprise Manager Ops Center Overview” on page 16

■

“Power On a Server With Multiple Active Domains (Oracle VM Server for SPARC)” on page 27

■

“Power Off a Server With Multiple Active Domains (Oracle VM Server for SPARC)” on page 28

■

“Configuring Boot and Restart Behavior” on page 43

Multipathing Software Overview

Multipathing software enables you to define and control redundant physical paths to I/O devices such as storage devices and network interfaces. If the active path to a device becomes unavailable, the software can automatically switch to an alternate path to maintain availability. This capability is known as automatic failover. To take advantage of multipathing capabilities, you must configure the server with redundant hardware, such as redundant network interfaces or two host bus adapters connected to the same dual-ported storage array.

For the servers, three different types of multipathing software are available:

■

Oracle Solaris IP Network Multipathing software provides multipathing and load-balancing capabilities for IP network interfaces. This software includes commands and other software resources for server administration. For instructions on how to configure and administer Oracle Solaris IP Network Multipathing, refer to one of the following manuals in the documentation collection for your Oracle Solaris OS release:

■

Oracle Solaris 11 OS – Oracle Solaris Administration: Network Services and Network

Virtualization

■

Oracle Solaris 10 OS – System Administration Guide: IP Services

14 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 15

Oracle Hardware Management Pack Overview

■

VVM software includes a feature called DMP, which provides disk multipathing as well as disk load balancing to optimize I/O throughput. For information about VVM and its DMP feature, refer to the documentation provided with the VERITAS Volume Manager software.

■

Oracle Solaris Multiplexed I/O (MPxIO) is an architecture fully integrated within the Oracle Solaris OS that enables I/O devices to be accessed through multiple host controller interfaces from a single instance of the I/O device. (Previously, this functionality was called StorageTek Traffic Manager.) For information about MPxIO, refer to Oracle Solaris Administration: SAN Configuration and Multipathing Guide in Oracle Solaris OS documentation.

Related Information

■

“Oracle Solaris OS Overview” on page 12

■

“Oracle VM Server for SPARC Overview” on page 13

Oracle Hardware Management Pack Overview

The Oracle Hardware Management Pack provides tools to manage and configure Oracle servers from the host operating system. To use these tools, you must install the Oracle Hardware Management Pack software on the server.

Note - Oracle Hardware Management Pack software is included in Oracle Solaris, beginning

with Oracle Solaris 11.2. If you are using that version or later of Oracle Solaris, update the Oracle Hardware Management Pack by updating Oracle Solaris.

You can download the Oracle Hardware Management Pack software at:

https://support.oracle.com

You can read and download documentation for the version of Oracle Hardware Management Pack you are using at:

http://www.oracle.com/goto/ohmp/docs

Related Information

■

“Hot-Spare Drives in RAID Volumes (LSI)” on page 88

Understanding System Administration Resources 15

Page 16

Oracle Enterprise Manager Ops Center Overview

Oracle Enterprise Manager Ops Center is a comprehensive system management solution for managing physical and virtual systems and devices. Through a single user interface, use the Oracle Enterprise Manager Ops Center software to monitor, patch, provision, virtualize, and support assets, such as operating systems, virtualization technologies, Oracle Servers, storage, and networks.

Oracle Enterprise Manager Ops Center can discover a server, its SP, the operating system, and logical domains already created by Oracle VM Server for SPARC. You can use the Oracle Enterprise Manager Ops Center to perform managing tasks on discovered assets, including creating logical domains and setting up RAIDs.

For more information about the software, refer to its product page and documentation library:

■

Oracle Enterprise Manager Ops Center at:

http://www.oracle.com/technetwork/oem/ops-center/index.html

■

Oracle Enterprise Manager Ops Center Documentation at:

http://www.oracle.com/technetwork/documentation/index.html#em

For instructions on deploying and managing the server using this software, refer to the Discovering and Managing an Oracle SPARC T5 Server How To guide. Find this guide, as well as guides on deploying Oracle VM Server for SPARC logical domains and Oracle Solaris Zones, by selecting the Deploy How Tos tab on the documentation library page. For example, this is the Deploy How Tos page for Oracle Enterprise Manager Ops Center 12c Release 2:

http://www.oracle.com/pls/topic/lookup?ctx=oc122&id=deployhowto

Related Information

■

“Hardware RAID Support” on page 81

16 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 17

Accessing the Server

These topics include information on establishing low-level communication with the server using Oracle ILOM and the system console.

■

“Log In to Oracle ILOM” on page 17

■

“Log In to the System Console” on page 18

■

“Obtain the OpenBoot Prompt Under Various Conditions” on page 19

■

“Display the Oracle ILOM Prompt” on page 20

■

“Redirect the System Console to a Local Graphics Monitor” on page 21

■

“Oracle ILOM Remote Console” on page 22

Related Information

■

“Accessing the Server” on page 17

■

“Booting and Shutting Down the OS” on page 33

Log In to Oracle ILOM

This procedure assumes the SP is in the default configuration as described in the server's installation guide.

Note - For a server module, you can either log in directly to the server module's SP or you

can start Oracle ILOM through the modular system's CMM. Refer to the server module's installation guide for instructions on both approaches.

Open an SSH session and connect to the SP by specifying its IP address.

The Oracle ILOM default username is root, and the default password is changeme.

% ssh root@xxx.xxx.xxx.xxx Password: password (nothing displayed as you type) ...

Accessing the Server 17

Page 18

Log In to the System Console

You are now logged in to Oracle ILOM. Perform tasks as needed by entering commands at the Oracle ILOM prompt.

Note - The server is provided with a default Administrator account (root) and a default

password (changeme) to enable first-time login and access to Oracle ILOM. To build a secure environment, you must change the default password of the default Administrator account as soon as possible after your initial login to Oracle ILOM. If you find this default Administrator account has already been changed, contact your system administrator to obtain an Oracle ILOM user account with Administrator privileges.

Related Information

■

“Oracle ILOM Overview” on page 11

■

“Log In to the System Console” on page 18

At the Oracle ILOM prompt, type:

-> start /HOST/console [-option] Are you sure you want to start /HOST/console (y/n) ? y Serial console started. To stop, type #. . . .

where option can be:

■

-f|force – Enables a user with a console (c) role to take the console from any current user and force that user into view mode.

■

-script – Bypasses the prompt for a yes or no confirmation.

When you reach the system console, you will see the OpenBoot prompt (ok) unless Oracle Solaris is running.

Related Information

■

“Display the Oracle ILOM Prompt” on page 20

18 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 19

Obtain the OpenBoot Prompt Under Various Conditions

■

“Redirect the System Console to a Local Graphics Monitor” on page 21

■

“Log In to Oracle ILOM” on page 17

Obtain the OpenBoot Prompt Under Various Conditions

This procedure assumes the default system console configuration. The method you use depends on the state of the OS at the time you attempt to obtain the OpenBoot prompt.

Caution - When possible, reach the OpenBoot prompt by performing a graceful shutdown of

the OS. Any other method used might result in the loss of server state data.

Set the Oracle ILOM bootmode property.

-> set /HOST/bootmode script=”setenv auto-boot? false”

This setting ensures that you will reach the OpenBoot prompt rather than having the OS boot automatically.

Choose the appropriate method to shutdown the OS and reach the OpenBoot prompt.

Refer to the linked procedures after you select a method.

Server State Method Links

OS running and responsive Shut down the server beginning at the host

prompt:

From a shell or command tool window, type an appropriate command (for example, the shutdown or init 0 command), Additional ways of using these commands described in the Oracle Solaris system administration documentation.

Then take one of the following steps:

■ At the Oracle ILOM prompt, type:

-> stop /System

■ Use the server Power button.

OS unresponsive Reset the host.

(Provided the operating system software is not running and the server is already under OpenBoot firmware control.)

“Shut Down the OS (init Command)” on page 36

“Shut Down the OS (shutdown Command)” on page 37

“Obtain the OpenBoot Prompt (Oracle Solaris)” on page 39

“Obtain the OpenBoot Prompt (Oracle ILOM CLI)” on page 40

“Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)” on page 41

Accessing the Server 19

Page 20

Display the Oracle ILOM Prompt

Server State Method Links

At the Oracle ILOM prompt, type:

-> set /HOST send_break_action=break

Then type:

-> start /HOST/console

OS unresponsive and need to prevent auto-boot

Shut down the server from Oracle ILOM.

At the Oracle ILOM prompt, type:

-> set /HOST/bootmode script=”setenv

“Obtain the OpenBoot Prompt (Oracle ILOM CLI)” on page 40

“Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)” on page 41

auto-boot? false”

Press Enter.

Then type:

-> reset /System

-> start /HOST/console

Related Information

■

“Monitoring the Server” on page 93

Display the Oracle ILOM Prompt

Display the Oracle ILOM prompt in one of these ways:

■ From the system console, type the Oracle ILOM escape sequence (#.).

■ Log in to Oracle ILOM directly from a device connected to the SER MGT port

or NET MGT port.

■ Log in to Oracle ILOM through an SSH connection. See “Log In to Oracle

ILOM” on page 17.

Related Information

■

“Oracle ILOM Overview” on page 11

■

“Log In to Oracle ILOM” on page 17

■

“Obtain the OpenBoot Prompt Under Various Conditions” on page 19

20 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 21

Redirect the System Console to a Local Graphics Monitor

You can redirect the system console to a local graphic monitor. You cannot use a local graphics monitor to perform the initial server installation, nor can you use a local graphics monitor to view POST messages.

Connect the monitor video cable to a video port on the server.

Tighten the thumbscrews to secure the connection. Refer to the server's installation guide for any special connection instructions that might apply to the server.

Connect the monitor power cord to an AC outlet.

Connect the USB keyboard cable to one USB port.

Connect the USB mouse cable to another USB port on the server.

Display the OpenBoot prompt.

See “Obtain the OpenBoot Prompt Under Various Conditions” on page 19.

At the OpenBoot prompt, set the following OpenBoot configuration variables:

ok setenv input-device keyboard ok setenv output-device screen

Apply the configuration changes.

ok reset-all

The server stores the parameter changes and boots automatically.

Note - Instead of using the reset-all command to store the parameter changes, you can also

power cycle the server using the Power button.

You can now type system commands and view system messages using your local graphics monitor. To activate the GUI interface, continue to the next step.

Activate the Oracle Solaris GUI interface.

Once Oracle Solaris is installed and booted, type the following commands to display the GUI login screen:

Accessing the Server 21

Page 22

Oracle ILOM Remote Console

# ln -s /dev/fbs/mga0 /dev/fb # fbconfig -xserver Xorg # reboot

Related Information

■

“Obtain the OpenBoot Prompt Under Various Conditions” on page 19.

■

“OpenBoot Configuration Parameters” on page 47

■

“Oracle ILOM Remote Console” on page 22

Oracle ILOM Remote Console

Oracle ILOM Remote Console is a Java application that enables you to remotely redirect and control the following devices on the host server. This group of devices is commonly abbreviated as KVMS.

■

Keyboard

■

Video console display

■

Mouse

■

Serial console display

■

Storage devices or images (CD/DVD)

Oracle ILOM Remote Console is documented in the Configuration and Maintenance Guide for the Oracle ILOM release.

Related Information

■

“Oracle ILOM In-band (Sideband) Management” on page 66

22 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 23

Controlling the Server

These topics include procedures for controlling basic server operations.

■

“Powering the Server On and Off” on page 23

■

“Resetting the Server and SP” on page 29

Related Information

■

“Booting and Shutting Down the OS” on page 33

Powering the Server On and Off

There are several ways to power the server on and off. Use the tasks that best suit your situation.

Description Links

Power the server on or off using the Oracle ILOM CLI. “Power On the Server (Oracle ILOM CLI)” on page 24

“Power Off the Server (Oracle ILOM CLI)” on page 24

Power the server on or off using the Oracle ILOM web interface.

Power the server on or off when the server is running Oracle VM for SPARC.

“Power On the Server (Oracle ILOM Web Interface)” on page 25

“Power Off the Server (Oracle ILOM Web Interface)” on page 26

“Power On a Server With Multiple Active Domains (Oracle VM Server for SPARC)” on page 27

“Power Off a Server With Multiple Active Domains (Oracle VM Server for SPARC)” on page 28

Related Information

■

“Resetting the Server and SP” on page 29

Controlling the Server 23

Page 24

Power On the Server (Oracle ILOM CLI)

Note - By default, the host automatically attempts to boot when the host is reset or

powered on. To learn about the parameters that control this action, see “Configuring Boot

Parameters” on page 43.

See “Log In to Oracle ILOM” on page 17.

Note - If you have a modular system, ensure that you are logged in to the desired server

module.

At the Oracle ILOM prompt, type:

-> start /System

Are you sure you want to start /System (y/n) ? y Starting /System

Note - To skip being prompted for confirmation, use the start -script /System command.

Switch to the host console to view host output.

-> start /HOST/console

Are you sure you want to start /HOST/console (y/n)? y

Related Information

■

“Power On the Server (Oracle ILOM CLI)” on page 24

■

“Reset the Server (Oracle Solaris)” on page 30

■

“Reset the Server (Oracle ILOM)” on page 30

Power Off the Server (Oracle ILOM CLI)

Shut down Oracle Solaris.

24 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 25

Power On the Server (Oracle ILOM Web Interface)

See one of these procedures:

■

“Shut Down the OS (init Command)” on page 36

■

“Shut Down the OS (shutdown Command)” on page 37

Switch from the system console prompt to the SP console prompt.

{0} ok #.

From the Oracle ILOM prompt, type:

-> stop /System Are you sure you want to stop /System (y/n)? y Stopping /System 

Note - To perform an immediate shutdown, use the stop -script /System command. Ensure

that all data is saved before typing this command.

Related Information

■

“Power On the Server (Oracle ILOM Web Interface)” on page 25

■

“Reset the Server (Oracle Solaris)” on page 30

■

“Reset the Server (Oracle ILOM)” on page 30

Power On the Server (Oracle ILOM Web Interface)

Note - By default, the host automatically attempts to boot when the host is reset or

powered on. To learn about the parameters that control this action, see “Configuring Boot

Parameters” on page 43.

See “Log In to Oracle ILOM” on page 17.

Note - If you have a modular system, ensure that you are logged in to the desired server

module.

Controlling the Server 25

Page 26

Power Off the Server (Oracle ILOM Web Interface)

On the Summary page, in the Actions panel, click the Power State Turn On button.

When prompted, click OK to confirm the action.

Related Information

■

“Power On the Server (Oracle ILOM CLI)” on page 24

■

“Reset the Server (Oracle Solaris)” on page 30

■

“Reset the Server (Oracle ILOM)” on page 30

Power Off the Server (Oracle ILOM Web Interface)

Shut down Oracle Solaris.

See one of these procedures:

■

“Shut Down the OS (init Command)” on page 36

■

“Shut Down the OS (shutdown Command)” on page 37

On the Summary page, in the Actions panel, click the Power State Turn Off button.

When prompted, click OK to confirm the action.

Related Information

■

“Power On the Server (Oracle ILOM CLI)” on page 24

■

“Reset the Server (Oracle Solaris)” on page 30

■

“Reset the Server (Oracle ILOM)” on page 30

26 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 27

Power On a Server With Multiple Active Domains (Oracle VM Server for SPARC)

If the server is configured with multiple Oracle VM Server for SPARC domains, use this procedure to power on the server and restart the domains.

See “Log In to Oracle ILOM” on page 17.

Note - If you have a modular system, ensure that you are logged in to the desired server

module.

Power on the host.

-> start /System Are you sure you want to start /System (y/n) ? y Starting /System

-> start /HOST/console Are you sure you want to start /HOST/console (y/n)? y

Start all of the nonprimary domains.

Starting a domain automatically binds the domain.

# ldm start-domain domain-name < . . . >

Boot all of the nonprimary domains.

The method you use to access a domain depends on how you have configured the consoles for your domains.

Boot each domain the same way you boot a server. See “Boot the OS (Oracle

ILOM)” on page 35.

Related Information

■

“Power Off a Server With Multiple Active Domains (Oracle VM Server for SPARC)” on page 28

Controlling the Server 27

Page 28

Power Off a Server With Multiple Active Domains (Oracle VM Server for SPARC)

If the server is configured with multiple Oracle VM for SPARC domains, use this procedure to shut down the domains and power off the server.

If needed, ensure that the domain configurations are saved to the SP.

# ldm add-config config-name

Access and shut down the OS in all of the nonprimary domains.

The method you use to access a domain depends on how you have configured the consoles for your domains. To shut down the OS, see “Shut Down the OS (init Command)” on page 36 or “Shut

Down the OS (shutdown Command)” on page 37.

From the primary domain, list the domains and their states.

# ldm ls

Note which domains are non-I/O domains or active I/O domains.

Stop and unbind all the non-I/O domains.

# ldm stop-domain domain-name < . . . > # ldm unbind domain-name

Stop and unbind any active I/O domains.

# ldm stop-domain domain-name < . . . > # ldm unbind domain-name

Verify that the nonprimary domains are inactive.

# ldm ls

Shut down the primary domain.

28 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 29

Resetting the Server and SP

To shut down the OS, see “Shut Down the OS (init Command)” on page 36 or “Shut

Down the OS (shutdown Command)” on page 37.

Switch from the system console prompt to the Oracle ILOM prompt.

{0} ok #.

From the Oracle ILOM prompt, type:

-> stop /System Are you sure you want to stop /System (y/n)? y Stopping /System 

Note - To perform an immediate shutdown, use the stop -force /System command. Ensure

that all data is saved before typing this command.

Related Information

■

“Power On a Server With Multiple Active Domains (Oracle VM Server for SPARC)” on page 27

Resetting the Server and SP

Use these topics to reset the server or SP.

■

“Reset the Server (Oracle Solaris)” on page 30

■

“Reset the Server (Oracle ILOM)” on page 30

■

“Reset the SP” on page 31

Related Information

■

“Powering the Server On and Off” on page 23

Controlling the Server 29

Page 30

Reset the Server (Oracle Solaris)

It is not necessary to power the server off and on to perform a reset.

Note - By default, the host automatically attempts to boot when the host is reset or

powered on. To learn about the parameters that control this action, see “Configuring Boot

Parameters” on page 43.

To reset the server from the Oracle Solaris prompt, type one of the following commands:

■

# shutdown -g0 -i6 -y

■

# reboot

Related Information

■

“Power Off the Server (Oracle ILOM CLI)” on page 24

■

“Power On the Server (Oracle ILOM Web Interface)” on page 25

■

“Reset the Server (Oracle ILOM)” on page 30

Reset the Server (Oracle ILOM)

The Oracle ILOM reset command generates a graceful or forced hardware reset of the server. By default, the reset command gracefully resets the server.

Note - By default, the host automatically attempts to boot when the host is reset or

powered on. To learn about the parameters that control this action, see “Configuring Boot

Parameters” on page 43.

See “Log In to Oracle ILOM” on page 17.

Note - If you have a modular system, ensure that you are logged in to the desired server

module.

Reset the server.

30 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 31

■ Perform a graceful reset.

-> reset /System

■ If a graceful reset is not possible, perform a forced hardware reset.

-> reset -force /System

Related Information

■

“Power On the Server (Oracle ILOM CLI)” on page 24

■

“Power On the Server (Oracle ILOM Web Interface)” on page 25

■

“Reset the Server (Oracle Solaris)” on page 30

■

“Override OpenBoot Settings to Reset the Server” on page 52

Reset the SP

After the reset, your login session to the SP is terminated.

Reset the SP

See “Log In to Oracle ILOM” on page 17.

Note - If you have a modular system, ensure that you are logged in to the desired server

module.

Reset the SP.

-> reset /SP

Related Information

■

“Log In to Oracle ILOM” on page 17

Controlling the Server 31

Page 32

32 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 33

Booting and Shutting Down the OS

These topics include instructions for booting and shutting down the OS. Instructions for obtaining the OpenBoot prompt are inclucded, because some of these procedures are performed at that prompt.

■

“Booting and Shutting Down Oracle Solaris” on page 33

■

“Obtaining the OpenBoot Prompt” on page 38

Related Information

■

“Controlling the Server” on page 23

Booting and Shutting Down Oracle Solaris

There are several ways to boot and shut down the OS.

Description Links

Learn about the boot sequence. “Boot Sequence” on page 34

Boot a server that is configured to boot at power-on (the default configuration) using Oracle ILOM.

Boot a server that is at the OpenBoot prompt. “Boot the OS Manually (OpenBoot)” on page 35

Shut down the OS using an Oracle Solaris command.

“Boot the OS (Oracle ILOM)” on page 35

“Shut Down the OS (init Command)” on page 36

“Shut Down the OS (shutdown Command)” on page 37

Related Information

■

“Powering the Server On and Off” on page 23

Booting and Shutting Down the OS 33

Page 34

Booting and Shutting Down Oracle Solaris

■

“Obtaining the OpenBoot Prompt” on page 38

Boot Sequence

In addition to controlling the power state of the host, you can also control how and when the OS is booted.

When the host is powered on, it can be in one of these states:

■

Booted – The OS is running in one of these levels:

■

3 – The OS is running in multiuser mode with all resources enabled.

■

S – The OS is running in singer-user mode, and some resources are not enabled.

■

At the OpenBoot prompt – The OS is not running. You communicate with the OpenBoot firmware on the host. See “OpenBoot Prompt” on page 38.

By default, the host automatically attempts to boot when the host is reset or powered on. The host first seeks a local boot drive. If the host cannot boot from the drive, the host attempts to boot from the network. See “Boot the OS (Oracle ILOM)” on page 35.

These steps describe the high-level boot sequence:

1. A host reset is initiated.

2. OpenBoot runs and OpenBoot parameters are read.

These are the primary OpenBoot parameters and default values that determine how the server boots (see “View All OpenBoot Parameters” on page 47):

■

diag-switch? false

■

auto-boot? true

■

boot-device disk???net

3. A boot block is read from the boot device to locate a boot program.

4. The boot program loads the kernel into memory.

5. The kernel is executed and takes control.

You can configure booting parameters from the OS or at the ok prompt. You can also affect the boot behavior through Oracle ILOM.

These resources provide more information about the boot process and how to configure booting in Oracle Solaris:

■

Oracle Solaris 11 – Booting and Shutting Down Oracle Solaris on SPARC Platforms

■

Oracle Solaris 10 – System Administration Guide: Basic Administration

34 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 35

Boot the OS (Oracle ILOM)

Related Information

■

“Boot the OS (Oracle ILOM)” on page 35

■

“Boot the OS Manually (OpenBoot)” on page 35

Boot the OS (Oracle ILOM)

By default, the host automatically attempts to boot when the host is reset or powered on.

See “Log In to Oracle ILOM” on page 17.

Note - If you have a modular system, ensure that you are logged in to the desired server

module.

If the OpenBoot parameters are configured with default values, boot the host using one of these methods:

■

Oracle ILOM web interface – In Host Management > Power Control, select any of the reset, power on, or power cycle actions, and click Save.

■

Oracle ILOM CLI – Type:

-> reset /System

Note - If the OpenBoot parameters are not configured with default values, when you reset the

host, the host might stop at the OpenBoot prompt. To boot from the OpenBoot prompt, see

“Boot the OS Manually (OpenBoot)” on page 35.

Related Information

■

“Boot the OS Manually (OpenBoot)” on page 35

■

“Boot Sequence” on page 34

Boot the OS Manually (OpenBoot)

Use this procedure when you are at the OpenBoot prompt, and you want to boot the OS.

Booting and Shutting Down the OS 35

Page 36

Shut Down the OS (init Command)

Obtain the OpenBoot prompt.

See “Obtaining the OpenBoot Prompt” on page 38.

Boot the host using one of these methods:

■

Boot from the devices specified in the OpenBoot boot-device parameter:

ok boot

■ Specify a device to boot from:

ok boot boot_device

where boot_device is a valid device from which to boot. For a list of valid devices, see

“OpenBoot Configuration Parameters” on page 47.

Related Information

■

“Boot the OS (Oracle ILOM)” on page 35

■

“Boot Sequence” on page 34

Shut Down the OS (init Command)

The init command is an executable shell script that terminates all active processes on a system and then synchronizes the disks before changing run levels. Specifying run level 0 shuts down the OS and displays the OpenBoot prompt.

Shut down the OS.

Note - This document applies to several server and server module products. The following

example is based on the SPARC T5-1B server module. Your output might vary from the examples based on your product.

# init 0 # svc.startd: The system is coming down. Please wait. svc.startd: 126 system services are now being stopped. Sep 21 13:31:31 systemA.xxxxx.com syslogd: going down on signal 15 svc.startd: Killing user processes.

36 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 37

Shut Down the OS (shutdown Command)

Sep 21 13:31:37 The system is down. Shutdown took 23 seconds. syncing file systems... done Program terminated SUN BLADE 6000 MODULAR SYSTEM / SPARC T5-1B, No Keyboard Copyright (c) 1998, 2012, Oracle and/or its affiliates. All rights reserved. OpenBoot 4.35. 63 GB memory available, Serial #xxxxxxxx. Ethernet address 0:xx:xx:xx:xx:xx, Host ID: xxxxxxxx. {0} ok

Related Information

■

“Shut Down the OS (shutdown Command)” on page 37

Shut Down the OS (shutdown Command)

The shutdown command sends a warning message, then terminates active processes on a system to reach a specified run level. Specifying run level 0 shuts down the OS and displays the OpenBoot prompt.

Shut down the OS.

In this example, these command options shut down the OS to the OpenBoot prompt:

■

-g0 – Specifies a grace period of 0 seconds.

■

-i0 – Specifies the run level 0, which is equivalent to the init 0 command.

■

-y – Pre-answers the confirmation question so that the command runs without user intervention.

Note - This document applies to several server and server module products. The following

example is based on the SPARC T5-2 server. Your output might vary from the examples based on your product.

# shutdown -g0 -i0 -y # svc.startd: The system is coming down. Please wait. svc.startd: 106 system services are now being stopped. Sep 12 17:52:11 systemA syslogd: going down on signal 15 svc.startd: The system is down. syncing file systems...done Program terminated

Booting and Shutting Down the OS 37

Page 38

Obtaining the OpenBoot Prompt

 SPARC T5-2, No Keyboard Copyright (c) 1998, 2011, Oracle and/or its affiliates. All rights reserved. OpenBoot 4.33.1, 32256 MB memory available, Serial #xxxxxxxx. Ethernet address 0:xx:xx:xx:xx:xx, Host ID: xxxxxxxx. {0} ok

Related Information

■

“Shut Down the OS (init Command)” on page 36

Obtaining the OpenBoot Prompt

There are several ways to reach the OpenBoot prompt (ok).

■

“OpenBoot Prompt” on page 38

■

“Obtain the OpenBoot Prompt (Oracle Solaris)” on page 39

■

“Obtain the OpenBoot Prompt (Oracle ILOM CLI)” on page 40

■

“Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)” on page 41

Related Information

■

“Log In to Oracle ILOM” on page 17

■

“Booting and Shutting Down Oracle Solaris” on page 33

OpenBoot Prompt

When the host is powered on but the OS is not booted, you communicate with the OpenBoot firmware. OpenBoot firmware displays ok as its prompt.

This table lists the common tasks that are performed at the ok prompt:

Task For More Information

Boot the host. “Boot the OS Manually (OpenBoot)” on page 35

Configure OpenBoot parameters. “View All OpenBoot Parameters” on page 47

38 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 39

Obtain the OpenBoot Prompt (Oracle Solaris)

Task For More Information

“Change the Default Boot Device (OpenBoot)” on page 44

Run diagnostics. Refer to detecting and managing faults in the service manual for the

Reset and power off the host.

Eject media.

server.

At the OpenBoot prompt, type help reset to display details about the reset command.

At the OpenBoot prompt, type help eject to display details about the eject command.

For more details about OpenBoot, refer to the OpenBoot 4.x Command Reference Manual at:

http://docs.oracle.com/cd/E23824_01

Locate the document under Important Information From Previous Releases.

Related Information

■

“Obtain the OpenBoot Prompt (Oracle Solaris)” on page 39

■

“Obtain the OpenBoot Prompt (Oracle ILOM CLI)” on page 40

■

“Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)” on page 41

Obtain the OpenBoot Prompt (Oracle Solaris)

Use this procedure when you want to shut down the OS and reach the ok prompt.

Shut down the OS.

# shutdown -g0 -i0 -y  Shutdown started. Wed Sep 19 15:17:45 PDT 2012  Changing to init state 0 - please wait Broadcast Message from root (console) on systemA.com Wed Sep 19 15:17:45... THE SYSTEM systemA.com IS BEING SHUT DOWN NOW ! ! ! Log off now or risk your files being damaged  root@systemA:~# svc.startd: The system is coming down. Please wait.

Booting and Shutting Down the OS 39

Page 40

Obtain the OpenBoot Prompt (Oracle ILOM CLI)

svc.startd: 126 system services are now being stopped. Sep 19 15:18:01 systemA.com syslogd: going down on signal 15 svc.startd: Killing user processes. Sep 19 15:18:07 The system is down. Shutdown took 22 seconds. syncing file systems... done Program terminated < . . . > {0} ok

The OS is shut down and the OpenBoot prompt (ok) is displayed.

Related Information

■

“OpenBoot Overview” on page 13

■

“Configuring Boot and Restart Behavior” on page 43

■

“Obtain the OpenBoot Prompt (Oracle ILOM CLI)” on page 40

■

“Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)” on page 41

Obtain the OpenBoot Prompt (Oracle ILOM CLI)

Use this procedure when the host is powered down and you are logged into Oracle ILOM.

See “Log In to Oracle ILOM” on page 17.

Note - If you have a modular system, ensure that you are logged in to the desired server

module.

Change the auto-boot? parameter to false.

-> set /HOST/bootmode script=”setenv auto-boot? false”

This command temporarily prevents the OS from booting before you obtain the OpenBoot prompt. This change applies only to a single reset and expires in 10 minutes if the power on the host is not reset.

Reset the host.

-> reset /System

40 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 41

Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)

Switch communication to the host.

-> start /HOST/console Are you sure you want to start /HOST/console (y/n)? y Serial console started. To stop, type #.

The server might take several minutes to complete POST and then displays the OpenBoot prompt.

Related Information

■

“OpenBoot Overview” on page 13

■

“Configuring Boot and Restart Behavior” on page 43

■

“Obtain the OpenBoot Prompt (Oracle Solaris)” on page 39

■

“Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)” on page 41

Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)

Use this procedure when the host is powered down, and you want to get to the ok prompt when the host is powered on.

See “Log In to Oracle ILOM” on page 17.

Note - If you have a modular system, ensure that you are managing the desired server module.

In the Oracle ILOM web interface, in the left navigation pane, select Host Management > Host Boot Mode.

The Host Boot Mode page is displayed.

Apply these changes to the Host Boot Mode Settings:

For State, select: Reset NVRAM

This setting applies a one-time NVRAM (OpenBoot) change based on the script setting, then resets the NVRAM to default settings on the next host reset.

For Script, type: setenv auto-boot? false

Booting and Shutting Down the OS 41

Page 42

Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)

This setting configures the host to stop at the OpenBoot prompt instead of automatically booting the preinstalled OS.

Click Save.

Note - You have 10 minutes to perform the next step. After 10 minutes, the state automatically

returns to normal.

In the left navigation panel, click Host Management > Power Control.

Select Reset from the pull-down menu, and click Save.

In the left navigation panel, click Remote Control > Redirection.

Select Use Serial Redirection, and click Launch Remote Console.

As the host resets, messages are displayed in the serial console. The OpenBoot prompt is displayed when the reset activity completes.

Related Information

■

“OpenBoot Overview” on page 13

■

“Configuring Boot and Restart Behavior” on page 43

■

“Obtain the OpenBoot Prompt (Oracle Solaris)” on page 39

■

“Obtain the OpenBoot Prompt (Oracle ILOM CLI)” on page 40

42 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 43

Configuring Boot and Restart Behavior

Use OpenBoot and Oracle Solaris commands to reconfigure the server's boot and restart behavior permanently or temporarily. Oracle ILOM boot mode properties can help specify how the host boots, enabling you to correct a problem with the current settings in OpenBoot or Oracle VM Server for SPARC.

■

“Configuring Boot Parameters” on page 43

■

“Boot Mode Overview (Oracle ILOM)” on page 49

■

“Configure the Host Boot Mode (Oracle VM Server for SPARC)” on page 50

■

“Change the Host Boot Mode Behavior at Reset (Oracle ILOM)” on page 51

■

“Manage the Host Boot Mode Script (Oracle ILOM)” on page 51

■

“Display the Host Boot Mode Expiration Date (Oracle ILOM)” on page 52

■

“Override OpenBoot Settings to Reset the Server” on page 52

■

“Server Restart Behavior Configuration (Oracle ILOM)” on page 53

Related Information

■

“Booting and Shutting Down the OS” on page 33

Configuring Boot Parameters

These topics describe how to change the default boot configuration.

For more comprehensive information about customizing how the server boots, refer to the Oracle Solaris documentation for your release.

■

“Change the Default Boot Device (OpenBoot)” on page 44

■

“Enable or Disable Automatic Booting (OpenBoot)” on page 45

■

“Enable or Disable Automatic Booting (Oracle Solaris)” on page 46

Configuring Boot and Restart Behavior 43

Page 44

Change the Default Boot Device (OpenBoot)

■

“View All OpenBoot Parameters” on page 47

■

“OpenBoot Configuration Parameters” on page 47

■

“printenv Output” on page 48

Related Information

■

“Booting and Shutting Down the OS” on page 33

Change the Default Boot Device (OpenBoot)

Use this procedure to configure OpenBoot to boot from a specific device. This change is permanent but only takes effect after a reset.

Obtain the ok prompt.

See one of these tasks:

■

“Obtain the OpenBoot Prompt (Oracle Solaris)” on page 39

■

“Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)” on page 41

■

“Obtain the OpenBoot Prompt (Oracle ILOM CLI)” on page 40

Determine the name of the desired boot device.

To see names of devices, type:

ok devalias

Configure the boot-device parameter with your desired boot device.

ok setenv boot-device boot_device

where boot_device is a valid device from which to boot.

Verify the change.

ok printenv boot-device

Reset the host.

44 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 45

Enable or Disable Automatic Booting (OpenBoot)

ok reset-all

Related Information

■

“printenv Output” on page 48

Enable or Disable Automatic Booting (OpenBoot)

Use this procedure to configure OpenBoot so that a host reset or power on either attempts to boot automatically, or not. This change is permanent but only takes effect after a host reset.

Obtain the ok prompt.

See one of these tasks:

■

“Obtain the OpenBoot Prompt (Oracle Solaris)” on page 39

■

“Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)” on page 41

■

“Obtain the OpenBoot Prompt (Oracle ILOM CLI)” on page 40

Set the OpenBoot auto-boot? parameter.

■

true – (Default) The host automatically attempts to boot from the devices specified in boot-device.

■

false – The host does not automatically boot. You can boot manually.

For example:

ok setenv auto-boot? false

Verify the change.

ok printenv auto-boot? auto-boot? = false

Reset the host.

ok reset-all

The host resets. After initialization, the host attempts to boot or not based on your configuration.

Configuring Boot and Restart Behavior 45

Page 46

Enable or Disable Automatic Booting (Oracle Solaris)

Related Information

■

“printenv Output” on page 48

■

“Enable or Disable Automatic Booting (Oracle Solaris)” on page 46

Enable or Disable Automatic Booting (Oracle Solaris)

While running Oracle Solaris, use this procedure to configure OpenBoot so that a host reset or power on either attempts to boot automatically, or not. This change is permanent but only takes effect after a host reset.

Set the OpenBoot auto-boot? parameter.

■

true – (Default) The host automatically attempts to boot from the devices specified in bootdevice.

■

false – The host does not automatically boot. You can boot manually.

For example:

# eeprom auto-boot?=false

Verify the change.

# eeprom auto-boot? auto-boot?=false

Reset the host.

# init 6

The host resets. After initialization, the host attempts to boot or not based on your configuration.

Related Information

■

“Enable or Disable Automatic Booting (OpenBoot)” on page 45

46 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 47

View All OpenBoot Parameters

View all of the OpenBoot parameters using one of these methods:

■

From the OpenBoot prompt, type: printenv

■

From Oracle Solaris, type: eeprom

View the value for an individual OpenBoot parameter using one of these methods:

■

From the OpenBoot prompt, type: printenv parameter

where parameter is a valid OpenBoot parameter.

■

From Oracle Solaris, type: eeprom parameter

where parameter is a valid OpenBoot parameter.

Related Information

■

“OpenBoot Configuration Parameters” on page 47

■

“printenv Output” on page 48

OpenBoot Configuration Parameters

Parameter Default Value Description

auto-boot-on-error? false

auto-boot? true

boot-command boot Specifies the command to be executed when auto-boot? is true. Valid boot

Controls whether or not the host attempts to boot after POST detects a nonrecoverable error.

■

false – Host does not attempt to boot and stops at the ok prompt.

■

true – Host automatically attempts to boot.

Controls whether or not the host automatically boots after a system reset or when the power is turned on.

■

true – Host automatically attempts to boot from the devices specified in boot-device.

■

false – Host does not attempt to boot and stops at the ok prompt.

commands:

■

boot – Boots kernel from devices specified in boot-device.

■

boot net – Boots kernel from the network.

■

boot cdrom – Boots kernel from the CDROM.

Configuring Boot and Restart Behavior 47

Page 48

View All OpenBoot Parameters

Parameter Default Value Description

■

boot disk1:h – Boots from disk 1 partition h.

■

boot tape – Boots default file from tape.

■

boot device-path – Boots from the device specified as device-path. See

“Locate Device Paths (OpenBoot)” on page 72.

boot-device disk net

boot-file

diag-switch? false If the value is true, runs in the Diagnostic mode.

network-boot-arguments

Contains the name of the default boot device that is used when OpenBoot is not in diagnostic mode.

An optional parameter that provides boot arguments that are used when OpenBoot is not in diagnostic mode.

An optional parameter that enables you to set configuration parameters to be used by OpenBoot when you perform a WAN boot. Setting this parameter takes precedence over any default boot parameter values. Refer to the eeprom(1M) man page for details.

Related Information

■

“printenv Output” on page 48

printenv Output

This output is a sample from the OpenBoot command printenv. The output for each server might be different.

{0} ok printenv Variable Name Value Default Value  ttya-rts-dtr-off false false ttya-ignore-cd true true keyboard-layout reboot-command security-mode none No default security-password No default security-#badlogins 0 No default verbosity min min diag-switch? false false local-mac-address? true true fcode-debug? false false scsi-initiator-id 7 7 oem-logo No default oem-logo? false false

48 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 49

Boot Mode Overview (Oracle ILOM)

oem-banner No default oem-banner? false false ansi-terminal? true true screen-#columns 80 80 screen-#rows 34 34 ttya-mode 9600,8,n,1,- 9600,8,n,1,output-device virtual-console virtual-console input-device virtual-console virtual-console auto-boot-on-error? false false load-base 16384 16384 auto-boot? false true network-boot-arguments boot-command boot boot boot-file boot-device disk net disk net multipath-boot? false false boot-device-index 0 0 use-nvramrc? false false nvramrc error-reset-recovery boot boot

Related Information

■

“OpenBoot Configuration Parameters” on page 47

Boot Mode Overview (Oracle ILOM)

Boot mode (bootmode) properties enable you to override the default method the server uses when it boots. This ability is useful to override particular OpenBoot or Oracle VM Server for SPARC settings that might be incorrect, to set up OpenBoot variables using a script, or to perform similar tasks.

For example, if the OpenBoot settings have become corrupt, you can set the bootmode state property to reset_nvram, then reset the server to its factory default OpenBoot settings.

Service personnel might instruct you to use the bootmode script property for problem resolution. The full extent of script capabilities are not documented and exist primarily for debugging.

Because bootmode is intended only to correct a problem with the OpenBoot or Oracle VM Server for SPARC settings, the new properties specified in this command take effect for a single boot only. Additionally, to prevent an administrator from setting a bootmode state property and

Configuring Boot and Restart Behavior 49

Page 50

Configure the Host Boot Mode (Oracle VM Server for SPARC)

forgetting about it, a bootmode state property expires if the host is not reset within 10 minutes of the bootmode state property being set.

Related Information

■

“Reset the Server (Oracle Solaris)” on page 30

■

“Reset the Server (Oracle ILOM)” on page 30

■

“OpenBoot Overview” on page 13

■

“Oracle VM Server for SPARC Overview” on page 13

Configure the Host Boot Mode (Oracle VM Server for SPARC)

Note - You must use a valid Oracle VM Server configuration name for this task.

See “Log In to Oracle ILOM” on page 17.

Determine the valid Oracle VM Server configurations on your SP.

-> show /HOST/domain/configs

Set the boot mode configuration at the Oracle ILOM prompt.

-> set /HOST/bootmode config=configname

where configname is a valid named logical domain configuration. For example, if you created a Oracle VM Server configuration called ldm-set1:

-> set /HOST/bootmode config=ldm-set1

To return the boot mode config to the factory default configuration, specify factory-default:

-> set /HOST/bootmode config=factory-default

Related Information

■

“Reset the Server (Oracle ILOM)” on page 30

■

“Boot Mode Overview (Oracle ILOM)” on page 49

■

“Oracle VM Server for SPARC Overview” on page 13

50 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 51

Change the Host Boot Mode Behavior at Reset (Oracle ILOM)

The /HOST/bootmode state property controls how OpenBoot NVRAM variables are used. Normally the current settings of these variables are retained. Setting /HOST/bootmode state=reset_nvram changes the OpenBoot NVRAM variables to their default settings at the next reset.

At the Oracle ILOM prompt, type:

-> set /HOST/bootmode state=value

where value is one of the following:

■

normal – At next reset, retains current NVRAM variable settings.

■

reset_nvram – At next reset, returns OpenBoot variables to default settings.

Note - The state=reset_nvram property returns to normal after the next server reset or 10

minutes. (See “Display the Host Boot Mode Expiration Date (Oracle ILOM)” on page 52.) The config and script properties do not expire. Those two properties are cleared when the server resets or when you clear them manually by setting value to "" ("" indicates an empty script).

Related Information

■

“Reset the Server (Oracle ILOM)” on page 30

■

“Boot Mode Overview (Oracle ILOM)” on page 49

■

“Oracle VM Server for SPARC Overview” on page 13

Manage the Host Boot Mode Script (Oracle ILOM)

At the Oracle ILOM prompt, type:

-> set /HOST/bootmode script=value

where script controls the host server's firmware OpenBoot method of booting.

script does not affect the current /HOST/bootmode setting.

value can be up to 64 bytes in length.

Configuring Boot and Restart Behavior 51

Page 52

Display the Host Boot Mode Expiration Date (Oracle ILOM)

You can specify a /HOST/bootmode setting and set the script within the same command. For example:

-> set /HOST/bootmode state=reset_nvram script="setenv diag-switch? true"

After the server resets and OpenBoot reads the values stored in the script, OpenBoot sets the diag-switch? variable to the user-requested value of true.

Note - If you set /HOST/bootmode script="", Oracle ILOM sets the script to empty.

Related Information

■

“Reset the Server (Oracle ILOM)” on page 30

■

“Boot Mode Overview (Oracle ILOM)” on page 49

■

“Oracle VM Server for SPARC Overview” on page 13

Display the Host Boot Mode Expiration Date (Oracle ILOM)

At the Oracle ILOM prompt, type:

-> show /HOST/bootmode expires

Properties: expires = Thu Oct 14 18:24:16 2010

where expires is the date and time when the current boot mode will expire.

Related Information

■

“Reset the Server (Oracle ILOM)” on page 30

■

“Boot Mode Overview (Oracle ILOM)” on page 49

■

“Oracle VM Server for SPARC Overview” on page 13

Override OpenBoot Settings to Reset the Server

Use this procedure to override the OpenBoot settings and initiate reboot of the control domain, which results in the host booting to the OpenBoot prompt.

52 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 53

Server Restart Behavior Configuration (Oracle ILOM)

At the Oracle ILOM prompt, type:

-> set /HOST/domain/control auto-boot=disabled

->reset /HOST/domain/control [-force] [-script]

The host reboots and stops at the OpenBoot prompt.

Related Information

■

“Change the Host Boot Mode Behavior at Reset (Oracle ILOM)” on page 51

■

“Configuring Boot and Restart Behavior” on page 43

■

“Boot Mode Overview (Oracle ILOM)” on page 49

■

“Oracle VM Server for SPARC Overview” on page 13

Server Restart Behavior Configuration (Oracle ILOM)

In addition to making temporary changes in boot behavior, you can also use Oracle ILOM to set how the host will behave when an error is encountered. For details on these options, refer to the section on setting boot behavior on a SPARC host server in the Configuration and Maintenance Guide for your Oracle ILOM release.

Related Information

■

“Resetting the Server and SP” on page 29

Configuring Boot and Restart Behavior 53

Page 54

54 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 55

Changing Server Identification Information

These topics describe how to store information (for purposes such as inventory control or site resource management) on the SP and FRU PROMs using the Oracle ILOM CLI interface.

■

“Change Customer Data on FRU PROMs” on page 55

■

“Change Server Identifier Information” on page 56

Related Information

■

“Turn On the Locator LED” on page 93

Change Customer Data on FRU PROMs

Use the /SP customer_frudata property to store information in all FRU PROMs. This property can be used to identify a particular system to a third-party application, or for any other identifcation needs in your environment.

At the Oracle ILOM prompt, type:

-> set /SP customer_frudata=”data”

Note - You must enclose the data string (data) in quote marks.

Related Information

■

“Log In to Oracle ILOM” on page 17

■

“Change Server Identifier Information” on page 56

Changing Server Identification Information 55

Page 56

Change Server Identifier Information

Use the /SP system_identifier property to store customer identification information. This string is encoded in all trap messages generated by SNMP. Assigning a unique system identifier can be useful in distinguishing which system generates which SNMP message.

At the Oracle ILOM prompt, type:

-> set /SP system_identifier=”data”

Note - You must enclose the data string (data) in quote marks.

Related Information

■

“Log In to Oracle ILOM” on page 17

■

“Change Customer Data on FRU PROMs” on page 55

56 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 57

Configuring Policy Settings

These topics describe managing configuration policies using Oracle ILOM.

■

“Specify Cooldown Mode” on page 57

■

“Restore the Host Power State at Restart” on page 58

■

“Specify the Host Power State at Restart” on page 59

■

“Disable or Reenable the Host Power-On Delay” on page 59

■

“Specify Parallel Boot of the SP and Host” on page 60

■

“Specify Host Virtual Keyswitch Behavior” on page 61

■

“Reset the Values in the SP to Default Values” on page 61

Related Information

■

“Configuring Boot and Restart Behavior” on page 43

Specify Cooldown Mode

Some servers support the host cooldown mode, but not all. Setting the HOST_COOLDOWN property to enabled causes the server to enter cooldown mode while the host is powering off. The cooldown mode directs Oracle ILOM to monitor certain components to ensure that they are below a minimum temperature, so as not to cause harm to the user if internal components are accessed.

Once the components are below the threshold temperature, power is removed from the server, which enables the cover interlock switch to release. If the monitored temperatures take longer than four minutes to reach the threshold, the host tuns off.

At the Oracle ILOM prompt, type:

-> set /SP/policy HOST_COOLDOWN=value

where value can be:

Configuring Policy Settings 57

Page 58

Restore the Host Power State at Restart

■

enabled – Server cools certain components before powering off.

■

disabled – Component temperatures are not monitored during power off.

Related Information

■

“Power Off the Server (Oracle ILOM Web Interface)” on page 26

■

“Power Off the Server (Oracle ILOM CLI)” on page 24

Restore the Host Power State at Restart

Use the /SP/policy HOST_LAST_POWER_STATE property to control the behavior of the server after an unexpected power outage. When external power is restored, the Oracle ILOM SP starts to run automatically. Normally, the host power is not turned on until you use Oracle ILOM to turn it on.

Oracle ILOM records the current power state of the server in nonvolatile storage. If the HOST_LAST_POWER_STATE policy is enabled, Oracle ILOM can restore the host to the previous power state. This policy is useful in the event of a power failure, or if you physically move the server to a different location.

For example, if the host server is running when power is lost and the /SP/policy HOST_LAST_POWER_STATE property is set to disabled, the host server remains off when power is restored. If the /SP/policy HOST_LAST_POWER_STATE property is set to enabled, the host server restarts when the power is restored.

At the Oracle ILOM prompt, type:

-> set /SP/policy HOST_LAST_POWER_STATE=enabled

where value can be:

■

enabled – When power is restored, returns the server to the state it was in before the power was removed.

■

disabled – (Default) Keeps the server off when power is applied.

If you enable HOST_LAST_POWER_STATE, you should also configure /SP/policy HOST_POWER_ON_DELAY. See “Disable or Reenable the Host Power-On Delay” on page 59.

Related Information

■

“Disable or Reenable the Host Power-On Delay” on page 59

58 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 59

■

“Specify the Host Power State at Restart” on page 59

Specify the Host Power State at Restart

Use the /SP/policy HOST_AUTO_POWER_ON property to power on the host when external power is applied to the server. If this policy is set to enabled, the SP sets HOST_LAST_POWER_STATE to disabled.

Note - For a server module, when HOST_AUTO_POWER_ON is enabled, you should also set

HOST_POWER_ON_DELAY to enabled.

At the Oracle ILOM prompt, type:

-> set /SP/policy HOST_AUTO_POWER_ON=value

where value can be:

■

enabled – When power is applied, automatically powers on the host when the SP has been booted.

■

disabled – (Default) Keeps the host power off when power is applied.

Specify the Host Power State at Restart

Related Information

■

“Restore the Host Power State at Restart” on page 58

■

“Disable or Reenable the Host Power-On Delay” on page 59

Disable or Reenable the Host Power-On Delay

Use the /SP/policy HOST_POWER_ON_DELAY property to cause the server to wait for a short time before powering on automatically. The delay is a random interval of one to five seconds. Delaying the server power-on helps minimize current surges on the main power source. This power-on delay is important when multiple servers in racks or multiple server modules in a modular system power on after a power outage.

For a server module, when HOST_AUTO_POWER_ON is enabled, you should also set HOST_POWER_ON_DELAY to enabled.

At the Oracle ILOM prompt, type:

Configuring Policy Settings 59

Page 60

Specify Parallel Boot of the SP and Host

-> set /SP/policy HOST_POWER_ON_DELAY=value

where value can be:

■

enabled – Causes the server to wait for a short time before powering on automatically.

■

disabled – (Default) Server powers on automatically without a delay.

Related Information

■

“Specify the Host Power State at Restart” on page 59

Specify Parallel Boot of the SP and Host

The /SP/policy PARALLEL_BOOT property enables the host to boot and power on in parallel with the SP. When enabled, parallel booting occurs if an auto-power policy (HOST_AUTO_POWER_ON or HOST_LAST_POWER_STATE) was on or if a user presses the power button while the SP is in the process of booting. Oracle ILOM must be running in order to enable the host to power on in these situations. When this property is set to disabled, the SP boots first, then the host boots.

Note - Parallel boot is not supported on server modules.

At the Oracle ILOM prompt, type:

-> set /SP/policy PARALLEL_BOOT=value

where value can be:

■

enabled – SP and host boot concurrently.

■

disabled – SP and host boot serially.

Related Information

■

“Power On the Server (Oracle ILOM Web Interface)” on page 25

■

“Power On the Server (Oracle ILOM CLI)” on page 24

■

“Power Off the Server (Oracle ILOM Web Interface)” on page 26

■

“Power Off the Server (Oracle ILOM CLI)” on page 24

60 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 61

Specify Host Virtual Keyswitch Behavior

Use the /HOST keyswitch_state property to control the position of the virtual keyswitch.

At the Oracle ILOM prompt, type:

-> set /HOST keyswitch_state=value

where value can be:

■

normal – (Default) The server can power itself on and start the boot process.

■

standby – Powers off the host, and disables power on.

■

diag – Host power on is allowed. This value overrides the settings of /HOST/diag target, resulting in Max POST being executed.

■

locked – Host power on is allowed, however, you are prohibited from updating flash devices or setting /HOST send_break_action=break.

Related Information

■

“Power On the Server (Oracle ILOM Web Interface)” on page 25

■

“Power On the Server (Oracle ILOM CLI)” on page 24

■

“Power Off the Server (Oracle ILOM Web Interface)” on page 26

■

“Power Off the Server (Oracle ILOM CLI)” on page 24

Reset the Values in the SP to Default Values

If your SP becomes corrupt, or you want to reset the SP to the factory default values, you must change the /SP reset_to_defaults setting, then power off the host to implement the changes. This behavior is new. Previously you did not have to power off the host to reset default values to the SP.

You need administrator permissions to perform this task.

See “Log In to Oracle ILOM” on page 17.

Note - If you have a modular system, ensure that you are logged in to the desired server

module.

Configuring Policy Settings 61

Page 62

Reset the Values in the SP to Default Values

Reset the SP to the default values.

-> set /SP reset_to_defaults=value

where value can be:

■

all – Removes all of the SP configuration data.

■

factory – Removes all of the SP configuration data and also all log files.

Power off and restart the host to complete the setting change.

-> stop /System

-> reset /SP

Related Information

■

“Power Off the Server (Oracle ILOM CLI)” on page 24

62 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 63

Configuring SP and Host Network Addresses

These topics describe managing network addresses with Oracle ILOM.

■

“SP Network Address Options” on page 63

■

“Disable or Reenable Network Access to the SP” on page 64

■

“Display the SP Network Parameters” on page 64

■

“Display the Host MAC Address” on page 65

■

“Connecting to the SP (In-band)” on page 65

Related Information

■

“Matching Devices to Device Names” on page 69

SP Network Address Options

You can access the SP on your system in multiple ways. Consider the following options and choose the access method that is best for your environment.

You can physically connect to the SP using a serial connection or a network connection. The network connection can be configured to use a static IP address or DHCP (the default). Optionally, the servers can use an in-band network connection to the SP, rather than the default out-of-band NET MGT port.

For more information on each option, refer to the following documentation:

■

To use a serial connection to the SP, refer to the information about connecting a terminal or emulator to the SER MGT port in the installation guide for a server, or the information about communicating with the server module during startup in the installation guide for a server module.

■

To assign a static IP address to the SP, refer to the information about assigning a static IP address to the SP in the installation guide for the server.

Configuring SP and Host Network Addresses 63

Page 64

Disable or Reenable Network Access to the SP

■

To use an in-band connection to the SP, see “Oracle ILOM In-band (Sideband)

Management” on page 66.

Related Information

■

Oracle ILOM Documentation

■

“Oracle ILOM Overview” on page 11

■

“Log In to Oracle ILOM” on page 17

Disable or Reenable Network Access to the SP

At the Oracle ILOM prompt, type:

-> set /SP/network state=value

where value can be:

■

enabled (Default)

■

disabled

Related Information

■

“Log In to Oracle ILOM” on page 17

■

“SP Network Address Options” on page 63

Display the SP Network Parameters

This procedure displays information such as the network address for the SP.

At the Oracle ILOM prompt, type:

-> show /SP/network

Find the relevant property in the output.

■

If you want the IP address of the SP, view the ipaddress property in the output. For example:

64 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 65

ipaddress = 10.x.xx.xxx

■

If you want the IP address of the DHCP server that provided the dynamic IP address requested by the SP, view the dhcp_server_ip property in the output. For example:

dhcp_server_ip = 10.x.x.x

Related Information

■

“Log In to Oracle ILOM” on page 17

■

“Display the Host MAC Address” on page 65

Display the Host MAC Address

The /HOST macaddress property is automatically configured by the server software, so you cannot set or change the property. The value is read and determined from the server's removable system configuration card (SCC PROM) or from the server module's ID PROM, and then stored as a property in Oracle ILOM.

Display the Host MAC Address

The value displayed for /HOST macaddress is for the server's NET 0 port. For each additional port, the MAC addresses increments from that NET 0 value. For example, the MAC address for NET 1 is the NET 0 MAC address plus one (1).

At the Oracle ILOM prompt, type:

-> show /HOST macaddress

Related Information

■

“Log In to Oracle ILOM” on page 17

■

“Display the SP Network Parameters” on page 64

Connecting to the SP (In-band)

These topics describe how to use an in-band, or sideband connection, to the SP.

Configuring SP and Host Network Addresses 65

Page 66

Display the Host MAC Address

■

“Oracle ILOM In-band (Sideband) Management” on page 66

■

“Configure SP In-band (Sideband) Access” on page 67

Related Information

■

“Accessing the Server” on page 17

Oracle ILOM In-band (Sideband) Management

Note - In-band connection is not recommended for server modules.

By default, you connect to the server's SP using the out-of-band NET MGT port. The Oracle ILOM sideband management feature enables you to select either the NET MGT port or one of the server's Gigabit Ethernet ports (named NET n), which are in-band ports, to send and receive Oracle ILOM commands to and from the server SP. In-band ports are also called sideband ports.

The advantage of using a sideband management port to manage the server's SP is that one fewer cable connection and one fewer network switch port are needed. In configurations where numerous servers are being managed, such as data centers, sideband management can represent a significant savings in hardware and network utilization.

When sideband management is enabled in Oracle ILOM, the following conditions might occur:

■

Connectivity to the server SP might be lost when the SP management port configuration is changed while you are connected to the SP using a network connection, such as SSH, web, or Oracle ILOM Remote Console.

■

In-chip connectivity between the SP and the host operating system might not be supported by the on-board host Gigabit Ethernet controller. If this condition occurs, use a different port or route to transmit traffic between the source and destination targets instead of using L2 bridging or switching.

■

Server host power cycles might cause a brief interruption of network connectivity for server Gigabit Ethernet ports that are configured for sideband management. If this condition occurs, configure the adjacent switch or bridge ports as host ports.

Related Information

■

“Configure SP In-band (Sideband) Access” on page 67

■

“SP Network Address Options” on page 63

66 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 67

Configure SP In-band (Sideband) Access

This procedure describes how to access the SP from an in-band (or sideband) management port using a host network port.

If you perform this procedure using a network connection, you might lose connectivity to the server. Using a serial connection for this procedure eliminates the possibility of losing connectivity during sideband management configuration changes.

See “Log In to Oracle ILOM” on page 17.

If you logged in using the serial port, assign a static IP address.

For instructions, refer to the information about assigning a static IP address in the installation guide for the server.

View the current network settings.

-> show /SP/network

For example, in the output, you might find these properties:

managementport = /SYS/MB/SP/MGMT ... pendingmanagementport = /SYS/MP/SP/MGMT

Set the SP management port to a sideband port.

For server modules, port is MGMT, NET0, or NET1. For servers, port is MGMT, NET0, NET1, NET2, or NET3.

-> set /SP/network pendingmanagementport=/SYS/MB/port

-> set /SP/network commitpending=true

Verify the change.

-> show /SP/network

For example, in the output, you might find these new properties:

managementport = /SYS/MB/NET0

Configuring SP and Host Network Addresses 67

Page 68

Configure SP In-band (Sideband) Access

... pendingmanagementport = /SYS/MP/NET0

Related Information

■

“Oracle ILOM In-band (Sideband) Management” on page 66

■

“SP Network Address Options” on page 63

68 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 69

Matching Devices to Device Names

These topics explain how to identify drives and other devices on the server with names that are recognized by or displayed by software and firmware. The same physical device is known by different types of names in different contexts.

■

“Importance of Matching a Physical Device to a Name” on page 69

■

“WWN Syntax” on page 70

■

“Display Server Components (Oracle ILOM)” on page 71

■

“Locate Device Paths (OpenBoot)” on page 72

■

“Correlate WWN Device Names With Physical Locations (diskinfo Command)” on page 72

■

“probe-scsi-all Device Naming (OpenBoot)” on page 74

■

“Correlate WWN Device Names With Physical Locations (probe-scsi-all Command)” on page 75

■

“Identify a Disk Slot (Oracle Solaris)” on page 76

■

“WWN Syntax in an Oracle Solaris 10 Installation on an Individual Drive” on page 78

■

“WWN Syntax in an Oracle Solaris 10 Installation on a RAID Volume” on page 79

Related Information

■

“Configuring SP and Host Network Addresses” on page 63

■

“Configuring Hardware RAID” on page 81

Importance of Matching a Physical Device to a Name

These are some situations when you must correlate a logical device name with the device's physical location.

■

When downloading the OS over a network, you must specify the logical device name of the drive in slot 0 (the default boot device).

Matching Devices to Device Names 69

Page 70

WWN Syntax

■

When you use Oracle Solaris 10 Jumpstart, you must refer to drives with a specific syntax. The letters in the WWN portion of the drive name must be capitalized, while the c, t, and d initial characters are lower case (for example, c0t5000C50033438DBBd0).

■

When you run the Oracle Solaris format command, you must select one of the logical device names presented in the output. To ensure that you select the correct drive for an operation, you must correlate these logical device names with the physical drives.

■

When you see a system message that lists a drive's logical device name, you might need to identify the physical slot in which the drive is installed.

Related Information

■

“WWN Syntax” on page 70

■

“WWN Syntax in an Oracle Solaris 10 Installation on an Individual Drive” on page 78

■

“WWN Syntax in an Oracle Solaris 10 Installation on a RAID Volume” on page 79

WWN Syntax

Oracle Solaris uses the WWN (World Wide Name) syntax in place of the locally unique tn (target ID) field in logical device names. This change affects how device names can be mapped to specific SCSI devices. The following points are key to understanding the impact of this change:

■

Before the change to WWN nomenclature, Oracle Solaris identified the default boot device as c0t0d0.

■

With the change, the device identifier for the default boot device is now referred to as c0tWWNd0, where WWN is a hexadecimal value that is unique to this device throughout the world.

■

This WWN value is assigned by the manufacturer of the device and, therefore, has a random relationship to the server's device tree structure.

Because WWN values do not conform to the traditional logical device name structure, you cannot directly identify a target device from its cntWWNdn value. Instead, you can use one of the following alternative methods to map WWN-based device names to physical devices.

■

When the OS is not running, you can analyze the output of the OpenBoot command probe- scsi-all.

For example, you would analyze probe-scsi-all output when you want to identify a boot device.

70 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 71

Display Server Components (Oracle ILOM)

■

When the OS is running, you can analyze the output of the command prtconf -v. See

“Identify a Disk Slot (Oracle Solaris)” on page 76 for more information.

Related Information

■

“Identify a Disk Slot (Oracle Solaris)” on page 76

■

“WWN Syntax in an Oracle Solaris 10 Installation on an Individual Drive” on page 78

■

“WWN Syntax in an Oracle Solaris 10 Installation on a RAID Volume” on page 79

Display Server Components (Oracle ILOM)

The Oracle ILOM show components command displays real-time information about the components installed in the server. This information includes the target name for each component.

At the Oracle ILOM prompt, type:

Note - This is a sample of show components output. Specific components will vary based on

each server.

-> show components Target | Property | Value

Note - The target names displayed by Oracle ILOM commands might begin with /System or

/SYS, depending on your situation.

Related Information

■

“Locate Device Paths (OpenBoot)” on page 72

Matching Devices to Device Names 71

Page 72

Locate Device Paths (OpenBoot)

Display the OpenBoot prompt.

See “Obtain the OpenBoot Prompt Under Various Conditions” on page 19.

From the OpenBoot prompt, type:

Note - This example represents devalias output for a sample T5 series server. The specific

devices displayed will differ for different products.

ok devalias screen /pci@340/pci@1/pci@0/pci@4/display@0 disk1 /pci@300/pci@1/pci@0/pci@4/scsi@0/disk@p1 disk /pci@300/pci@1/pci0/pci@4/scsi@0/disk@p0 disk0 /pci@300/pci@1/pci@0/pci@4/scsi@0/disk@p0 scsi /pci@300/pci@1/pci@0/pci@4/scsi@0 scsi0 /pci@300/pci@1/pci@0/pci@4/scsi@0 net1 /pci@300/pci@1/pci@0/pci@2/network@0,1 net /pci@300/pci@1/pci@0/pci@2/network@0 net0 /pci@300/pci@1/pci@0/pci@2/network@0 virtual-console /virtual-devices/console@1 name aliases

Related Information

■

“Obtain the OpenBoot Prompt Under Various Conditions” on page 19

■

“Prepare to Create a RAID Hardware Volume (FCode-based RAID Utility)” on page 85

Correlate WWN Device Names With Physical Locations (diskinfo Command)

The diskinfo command is available in Oracle Solaris. If you are using Oracle Solaris 11, this command is effective for all T5 series servers. If you are using Oracle Solaris 10, this procedure is only effective for the server modules, so other servers require the procedure in “Correlate

WWN Device Names With Physical Locations (probe-scsi-all Command)” on page 75.

You also need to use that procedure if you do not have access to Oracle Solaris at the time you need to determine a name for a specific drive.

72 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 73

Correlate WWN Device Names With Physical Locations (diskinfo Command)

Display information about the drives on the server.

Note - This document applies to several server and server module products. The following

example is based on the SPARC T5-1B server module. Your output might vary from the examples based on your product.

For example, on a SPARC T5-1B server module running Oracle Solaris 10 1/13:

# diskinfo -a  Enclosure path: 0000000-0000000000-physical-hba-0 Chassis Serial Number: 0000000-0000000000-physical-hba-0 Chassis Model: sun4v-platform  Label Disk Name Vendor Product Vers

----------- ---------------------- -------- ---------------- ----/SYS/HDD0 c0t5000CCA01622AC64d0 HITACHI H109030SESUN300G A31A /SYS/HDD1 c0t5000CCA01622B1F4d0 HITACHI H109030SESUN300G A31A

In Oracle Solaris 11.1, you see output with similar information when you type:

# diskinfo -P SYS -o Rc

For further information, refer to the Oracle Solaris documentation or man page on the diskinfo command.

Look at the output under the Label and Disk Name columns to correlate a drive's physical location with its corresponding logical device name.

In this example for a SPARC T5-1B server module:

■

/SYS/HDD0 represents a drive in slot 0.

■

/SYS/HDD1 represents a drive in slot 1.

Related Information

■

diskinfo(1m) man page in Oracle Solaris

■

“Correlate WWN Device Names With Physical Locations (probe-scsi-all Command)” on page 75

Matching Devices to Device Names 73

Page 74

probe-scsi-all Device Naming (OpenBoot)

The output displayed by probe-scsi-all lists all SCSI devices in the server and provides a basic set of information about each device. When analyzing the probe-scsi-all output, look for the following data fields that are different names for the same device. You must use a specific type of name in different commands.

Entity Name Definition

Target

SASDeviceName

SASAddress

PhyNum

VolumeDeviceName (when a RAID volume is

configured)

Each SAS or SATA drive is assigned a unique target ID.

The WWN value assigned to a SAS drive by the manufacturer. Oracle Solaris recognizes this name.

The WWN value assigned to a SCSI device that is recognized by the OpenBoot firmware.

A hexidecimal ID of the controller port that is attached to the target drive.

The WWN value assigned to a RAID volume that is recognized by Oracle Solaris. The VolumeDeviceName replaces the SASDeviceName of every SCSI device contained in the RAID volume.

Use the VolumeDeviceName entity to determine the correct target in a RAID volume, or when the server is configured with an optional internal RAID HBA controller.

VolumeWWID (when a RAID volume is configured)

The WWN-based value assigned to a RAID volume that is recognized by the OpenBoot firmware. VolumeWWID replaces the SASAddress of every SCSI device contained in the RAID volume.

At a high level, the WWN mapping process consists of the following stages:

1. Identify the physical location of the hard drive that is to be the target of the operation.

2. Identify the controller port that is attached to that physical location.

3. Find the WWN-based device name of the drive attached to that controller port.

Note - Refer to the service manual for the server for a description of the physical drive slot

organization.

Related Information

■

“WWN Syntax” on page 70

74 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 75

Correlate WWN Device Names With Physical Locations (probe-scsi-all Command)

■

“Identify a Disk Slot (Oracle Solaris)” on page 76

■

“WWN Syntax in an Oracle Solaris 10 Installation on an Individual Drive” on page 78

■

“WWN Syntax in an Oracle Solaris 10 Installation on a RAID Volume” on page 79

Correlate WWN Device Names With Physical Locations (probe-scsi-all Command)

Note - If you have access to Oracle Solaris, you might be able to use the diskinfo command

instead as a way to determine the device names you need. See “Correlate WWN Device Names

With Physical Locations (diskinfo Command)” on page 72.

At the OpenBoot prompt, type:

ok probe-scsi-all /pci@400/pci@1/pci@0/pci@cLSI,sas@0  FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00  Target 9 Unit 0 Disk SEAGATE ST9300003SSUN3006 0B70 585937500 Blocks, 300 GB SASDeviceName 5000c50033438dbb SASAddress 5000c50033438db9 PhyNum 0 Target b Unit 0 Dusj SEAGATE ST930003SSUN300G 0468 585937500 Blocks, 300 GB SASDeviceName 5000c50005c15803 SASAddress 5000c50005c15801 PhyNum 1 Target c Unit 0 Elcl Serv device SUN NEM Hydra II SOL 0308 SASAddress 5080020000bb193d PhyNum 24  /pci@400/pci@1/pci@0/pci@0/pci@0/usb@0,2/hub@3/storage@2 Unit 0 Removable Read Only device AMI Virtual CDROM 1.00

In this output, look for these disk identifiers:

■

LSI,sas@0 – Disk controller (a REM in this example). If the server has more than one disk controller, the target drives associated with each controller are listed following that controller's information.

■

SASDeviceName – WWN that Oracle Solaris recognizes.

■

SASAddress – WWN that OpenBoot references.

■

PhyNum – Physical slot that the drive occupies (the value 0 indicates a drive in HDD slot 0).

Matching Devices to Device Names 75

Page 76

Identify a Disk Slot (Oracle Solaris)

Look at the values in this output to construct a logical device name in the cntWWNdn format that is recognized by Oracle Solaris.

For this example, you construct a name like this to indicate the drive in slot 0.

■

cn = c0

n is the SAS controller number.

■

tWWN = t5000c50033438dbb

WWN is the SASDeviceName value.

■

dn = d0

n is 0 for all embedded SCSI devices.

The completed logical device name is c0t5000c50033438dbbd0.

Related Information

■

“probe-scsi-all Device Naming (OpenBoot)” on page 74

■

“Correlate WWN Device Names With Physical Locations (diskinfo Command)” on page 72

Identify a Disk Slot (Oracle Solaris)

The examples in this procedure apply to a SPARC T5-4 server that has an eight-disk backplane configuration.

Note - This document applies to several server and server module products. The following

example is based on the SPARC T5-4 server. Your output might vary from the examples based on your product.

Type the format command.

# format Searching for disks...done  AVAILABLE DISK SELECTIONS:

0. c0t5000CCA00ABBAEB8d0 <SUN300G cyl 46873 alt 2 hd 20 sec 625>

/scsi_vhci/disk@g5000cca00abbaeb8

1. c0t5000C5001D40D7F7d0 <SUN300G cyl 46873 alt 2 hd 20 sec 625>

/scsi_vhci/disk@g5000c5001d40d7f7 [...]

76 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 77

Identify a Disk Slot (Oracle Solaris)

The remaining steps in this example identify the physical slot that corresponds to the device name c0t5000CCA00ABBAEB8d0.

Type prtconf -v and search for the device link containing the device name c0t5000CCA00ABBAEB8d0.

For this example, the following portion of the output includes that device name:

Device Minor Nodes: dev=(32,0) dev_path=/scsi_vhci/disk@g5000cca00abbaeb8:a spectype=blk type=minor dev_link=/dev/dsk/c0t5000CCA00ABBAEB8d0s0 <<=== Device link dev_link=/dev/sd3a dev_path=/scsi_vhci/disk@g5000cca00abbaeb8:a,raw spectype=chr type=minor dev_link=/dev/rdsk/c0t5000CCA00ABBAEB8d0s0 <<=== Device link dev_link=/dev/rsd3a

Search the prtconf output for the name='wwn' entry that shows the WWN value 5000cca00abbaeb8.

Note the obp-path value listed under WWN 5000cca00abbaeb8.

Refer to the following items to find the controller.

■

Controller 0 – /pci@400/pci@1/pci@0/pci@0/LSI,sas@0/disk@w5000cca00abbaeb9,0

■

Controller 1 – /pci@700/pci@1/pci@0/pci@0/LSI,sas@0/disk@w5000cca00abbaeb9,0

For SPARC T5-4 servers, the controller is identified in the first field. For servers with a fourprocessor configuration, pci@400 is controller 0 and pci@700 is controller 1.

The following output example shows the obp-path for a SPARC T5-4 server.

Paths from multipath bus adapters: mpt_sas#5 (online) name='wwn' type=string items=1 value='5000cca00abbaeb8' <<=== Hard drive WWN ID name='lun' type=int items=1 value=00000000 name='target-port' type=string items=1 value='5000cca00abbaeb9' <<=== Hard drive SAS address name='obp-path' type=string items=1 value='/pci@400/pci@1/pci@0/LSI,sas@0/disk@w5000cca00abbaeb9,0' name='phy-num' type=int items=1 value=00000000

Matching Devices to Device Names 77

Page 78

WWN Syntax in an Oracle Solaris 10 Installation on an Individual Drive

name='path-class' type=string items=1 value='primary'

In this example, the obp-path is:

/pci@400/pci@1/pci@0/pci@0/LSI,sas@0/disk@w5000cca00abbaeb9,0

Based on the earlier name identification, this disk is on controller 0.

Consult this port mapping table to determine which physical disk slot the phy-num value corresponds to.

This phy-num value corresponds to physical disk slot 0.

SAS Controller

0 0 0

†

Default boot drive

PhyNum Disk Slot

†

1 1 1 5

2 2 2 6

3 3 3 7

SAS Controller

1 0 4

PhyNum Disk Slot

Related Information

■

“WWN Syntax” on page 70

■

“probe-scsi-all Device Naming (OpenBoot)” on page 74

■

“WWN Syntax in an Oracle Solaris 10 Installation on an Individual Drive” on page 78

■

“WWN Syntax in an Oracle Solaris 10 Installation on a RAID Volume” on page 79

WWN Syntax in an Oracle Solaris 10 Installation on an Individual Drive

The following Oracle Solaris 10 Jumpstart profile example shows details of the WWN syntax for installing the operating system on a specific disk drive. In this example, the device name contains the WWN value 5000CCA00A75DCAC.

Note - All alpha characters in the WWN value must be capitalized when included in a Jumpstart

profile.

78 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 79

WWN Syntax in an Oracle Solaris 10 Installation on a RAID Volume

# install_type flash_install boot_device c0t5000CCA00A75DCACd0s0 preserve  archive_location nfs ***.***.***.***:/export/install/media/solaris/builds/s10u9/flar/latest.flar  # Disk layouts # partitioning explicit filesys rootdisk.s0 free / filesys rootdisk.s1 8192 swap

Related Information

■

“Importance of Matching a Physical Device to a Name” on page 69

■

“WWN Syntax” on page 70

■

“probe-scsi-all Device Naming (OpenBoot)” on page 74

■

“Identify a Disk Slot (Oracle Solaris)” on page 76

■

“WWN Syntax in an Oracle Solaris 10 Installation on a RAID Volume” on page 79

WWN Syntax in an Oracle Solaris 10 Installation on a RAID Volume

The following Oracle Solaris 10 Jumpstart profile example shows details of the WWN syntax for installing the OS on a RAID volume. When installing software on a RAID volume, use the virtual device's VolumeDeviceName instead of an individual device name. In this example, the RAID volume name is 3ce534e42c02a3c0.

# install_type flash_install boot_device 3ce534e42c02a3c0 preserve  archive_location nfs ***.***.***.***:/export/install/media/solaris/builds/s10u9/flar/latest.flar  # Disk layouts # partitioning explicit filesys rootdisk.s0 free / filesys rootdisk.s1 8192 swap

Matching Devices to Device Names 79

Page 80

WWN Syntax in an Oracle Solaris 10 Installation on a RAID Volume

Related Information

■

“Importance of Matching a Physical Device to a Name” on page 69

■

“WWN Syntax” on page 70

■

“probe-scsi-all Device Naming (OpenBoot)” on page 74

■

“Identify a Disk Slot (Oracle Solaris)” on page 76

■

“WWN Syntax in an Oracle Solaris 10 Installation on an Individual Drive” on page 78

80 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 81

Configuring Hardware RAID

These topics describe how to configure and manage RAID disk volumes using the server's onboard SAS-2 disk controller.

■

“Hardware RAID Support” on page 81

■

“Hardware RAID Guidelines” on page 84

■

“FCode-Based RAID Utility Commands” on page 84

■

“Prepare to Create a RAID Hardware Volume (FCode-based RAID Utility)” on page 85

■

“Create a Hardware RAID Volume” on page 86

■

“Hot-Spare Drives in RAID Volumes (LSI)” on page 88

■

“Determining if a Drive Has Failed” on page 88

■

“RAID Drive Replacement Strategies” on page 91

Related Information

■

“Matching Devices to Device Names” on page 69

Hardware RAID Support

The servers provide hardware RAID support through on-board SAS2 RAID controllers. Each controller enables you to create up to two logical disk volumes consisting of two or more redundant disk drives. The following table identifies the hardware RAID controllers built into each server.

Server Controller Description Supported RAID Levels

SPARC T5-1B One on-board SAS2 controller 0, 1

Netra SPARC T5-1B One on-board SAS2 controller 0, 1

SPARC T5-2 Two on-board SAS2 controllers 0, 1, 1e, 10

Configuring Hardware RAID 81

Page 82

Hardware RAID Support

Server Controller Description Supported RAID Levels

SPARC T5-4 Two on-board SAS2 controllers 0, 1, 1e, 10

SPARC T5-8 Two on-board SAS2 controllers 0, 1, 1e, 10

Note - RAID 1e and RAID 10 are functionally equivalent. RAID 1e requires an odd number of

drives (minimum three). RAID 10 requires an even number of drives (minimum four).

Some servers also support REM controllers that provide hardware RAID capabilities. Documentation for Oracle's REM controllers is available at: http://docs.oracle.com/cd/

E19946-01/index.html.

There are four sets of RAID management utilities you can use with the on-board SAS2 controllers provided in these servers.

FCode-Based RAID Utility

You can use FCode-based commands provided with the on-board controller to display targets and manage logical volumes on the server. You enter these commands at the OpenBoot prompt.

The examples of RAID shown in this document rely on the controller's FCode-based commands, unless otherwise specified.

sas2ircu Utility

You can use the LSI SAS2 2008 RAID Management Utility sas2ircu at the Oracle Solaris command prompt to manage RAID functionality for the on-board SAS2 controllers. The sas2ircu utility can configure RAID 0, RAID 1, RAID 1e, and RAID 10.

Note - With sas2ircu, when you specify RAID 1e, there must be an odd number of target

drives (minimum three). When you specify RAID 10, there must be an even number of target drives (minimum four).

The sas2ircu utility for Oracle servers, together with user documentation, are available on the LSI website at:

http://www.lsi.com/sep/Pages/oracle/index.aspx

82 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 83

Hardware RAID Support

Caution - When you get firmware updates for the on-board SAS controllers, you must acquire

them from Oracle's support site, https://support.oracle.com. Firmware applied to the onboard SAS controllers that was obtained from any other location or any vendor other than Oracle is not supported.

raidconfig Commands

You can use the raidconfig commands contained in the Oracle Hardware Management Pack. Use the Oracle Server CLI Tools component to create and manage RAID volumes on the server. To use these commands, download and install Oracle Hardware Management Pack software that supports the server. To install the software, refer to the Oracle Hardware Management Pack Installation Guide for your version at:

http://www.oracle.com/goto/ohmp/docs

RAID Capabilities in Oracle Enterprise Manager Ops Center

You can create RAIDs and manage existing RAIDs with Oracle Enterprise Manager Ops Center. If you reconfigure an existing RAID with Oracle Enterprise Manager Ops Center, the contents of the disks in the original RAID will be lost.

For more about Oracle Enterprise Manager Ops Center, see “Oracle Enterprise Manager Ops

Center Overview” on page 16.

Related Information

■

“Create a Hardware RAID Volume” on page 86

■

“Prepare to Create a RAID Hardware Volume (FCode-based RAID Utility)” on page 85

■

“Oracle Hardware Management Pack Overview” on page 15

■

“Oracle Enterprise Manager Ops Center Overview” on page 16

Configuring Hardware RAID 83

Page 84

Hardware RAID Guidelines

Caution - When you create a RAID volume using the on-board disk controllers, all data

currently on the disks you include in the volume will be lost.

The following points are important to understand when configuring RAID volumes on a server:

■

Before configuring and using RAID disk volumes on a server, ensure that you have installed the latest SRU or patches available for your operating system. Review the most recent product notes provided for your system for further guidance in keeping your OS up to date.

■

Volume migration (that is, relocating all RAID volume disk members from one server to another) is not supported. If you must perform this operation, contact your authorized Oracle service provider.

Related Information

■

“Updating the Firmware” on page 97

FCode-Based RAID Utility Commands

These commands are provided through an FCode-based RAID utility provided with the onboard controllers. You can enter these commands at the OpenBoot prompt. For details on preparing to enter these commands to affect a specific controller, see “Prepare to Create a RAID

Hardware Volume (FCode-based RAID Utility)” on page 85.

FCode Command Description

show-children

show-volumes

create-raid0-volume

create-raid1-volume

create-raid1e-volume

create-raid10-volume

Lists all connected physical drives and logical volumes.

Lists all connected logical volumes in detail.

Creates a RAID 0 volume (minimum two targets).

Creates a RAID 1 volume (exactly two targets).

Creates a RAID 1e volume for an odd number of target drives (minimum three).

Note - If you specify an even number of target drives (minimum four) with

this command, those drives will be configured and identified as RAID 10. For an even number of drives, RAID 1e is the functional equivalent of RAID 10.

Creates a RAID 10 volume for an even number of target drives (minimum four).

84 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 85

Prepare to Create a RAID Hardware Volume (FCode-based RAID Utility)

FCode Command Description

For any other number of target drives, this command fails.

delete-volume

activate-volume

Deletes a RAID volume.

Reactivates a RAID volume after the motherboard has been replaced.

Related Information

■

“Create a Hardware RAID Volume” on page 86

■

“Prepare to Create a RAID Hardware Volume (FCode-based RAID Utility)” on page 85

■

“Obtaining the OpenBoot Prompt” on page 38

Prepare to Create a RAID Hardware Volume (FCodebased RAID Utility)

Perform this procedure to be ready to create a RAID volume using the FCode-based RAID utility. This procedure also enables you to use other FCode-based RAID utility commands on a specific controller.

Perform the following procedure from an Xterm or an equivalent terminal window that supports scrolling.

Note - OpenBoot commands and FCode-based commands produce large amounts of detailed

output. An Xterm or Gnome terminal window provides scroll bar functionality, which helps you view such output.

Either apply power to the system or reset the system if power is already present, and disable auto-boot in the OpenBoot environment.

See “Obtain the OpenBoot Prompt Under Various Conditions” on page 19.

Enter the OpenBoot environment.

List the device paths on the server.

For example, the output from the command might include these lines:

ok show-devs ... /pci@300/pci@1/pci@0/pci@4/scsi@0 /pci@300/pci@1/pci@0/pci@4/scsi@0

Configuring Hardware RAID 85

Page 86

Create a Hardware RAID Volume

...

Use the OpenBoot select command to specify the controller where you want to create a hardware RAID volume.

ok select /pci@300/pci@1/pci@0/pci@4/scsi@0

Instead of using the entire device path for the controller, you can use a preconfigured alias for a controller. For example:

ok select scsi_alias

where scsi_alias corresponds to a preconfigured alias you had previously created for your path.

Note - To view the preconfigured aliases on the server, use the OpenBoot devalias command.

See “Locate Device Paths (OpenBoot)” on page 72.

If you decide to select a different controller after performing Step 5, you must unselect the current controller.

ok unselect-dev

Now you can select a different controller, as described in Step 5. You can then run other FCodebased RAID commands that apply to the selected controller.

Continue to create a hardware RAID volume on the selected controller.

See “Create a Hardware RAID Volume” on page 86.

Related Information

■

“Obtain the OpenBoot Prompt Under Various Conditions” on page 19

■

“FCode-Based RAID Utility Commands” on page 84

■

“Locate Device Paths (OpenBoot)” on page 72

Create a Hardware RAID Volume

Select the controller that will handle a new RAID volume.

See “Prepare to Create a RAID Hardware Volume (FCode-based RAID

Utility)” on page 85. At this point you have obtained the OpenBoot prompt and have

selected an on-board disk controller.

86 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 87

Create a Hardware RAID Volume

List the physical drives on the selected controller.

Note the target name of each disk you will use in the RAID. In this example, the targets are named 9, a, b, and c.

ok show-children ... Target 9 Unit 0 Disk HITACHI H109030SESUN300G A31A 585937500 Blocks, 300 GB SASDeviceName 5000cca01622ac64 SASAddress 5000cca01622ac65 PhyNum 0 Target a Unit 0 Disk HITACHI H109030SESUN300G A31A 585937500 Blocks, 300 GB SASDeviceName 5000cca01622b1f4 SASAddress 5000cca01622b1f5 PhyNum 1 ok 

Select one of these commands to create a logical drive from several physical disks:

■

create-raid0-volume

■

create-raid1-volume

■

create-raid1e-volume

■

create-raid10-volume

For example, to create a RAID 0 volume with targets 9 and a, type the targets first then type the command name:

ok 9 a create-raid0-volume

To create a RAID 1e volume with three targets (a, b, and c), type:

ok a b c create-raid1e-volume

To create a RAID 10 volume with four targets (9, a, b, and c), type:

ok 9 a b c create-raid10-volume

Verify creation of the RAID volume.

ok show-volumes

(Optional) Create a second RAID volume to be handled by the present controller.

To do so, enter another command as described in Step 3.

Configuring Hardware RAID 87

Page 88

Hot-Spare Drives in RAID Volumes (LSI)

Unselect the controller.

ok unselect-dev

Related Information

■

“FCode-Based RAID Utility Commands” on page 84

■

“Obtain the OpenBoot Prompt Under Various Conditions” on page 19

Hot-Spare Drives in RAID Volumes (LSI)

You can configure two global hot-spare drives to protect data on mirrored RAID volumes. If one of the drives in a RAID 1, RAID 1e, or RAID 10 mirrored volume fails, the on-board RAID controller will replace the failed drive automatically with a hot-spare drive and then resynchronize the mirrored data.

Use the sas2ircu LSI utility to add global hot-spare drives. You can also use the raidconfig utility included in the Oracle Hardware Management Pack. Refer to the SAS2 Integrated RAID Solution User Guide for more information about adding hot-spare drives.

Related Information

■

“Hardware RAID Support” on page 81

■

“Oracle Hardware Management Pack Overview” on page 15

Determining if a Drive Has Failed

These topics explain various ways to determine if a drive contained in a RAID volume has failed:

■

“Service Required Drive LEDs” on page 89

■

“Locate Error Messages Related to Drives in a RAID Volume” on page 89

■

“Display Status (FCode-Based RAID Utility)” on page 90

■

“Display Status (sas2ircu Utility, LSI)” on page 91

88 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 89

Locate Error Messages Related to Drives in a RAID Volume

Related Information

■

“Monitoring the Server” on page 93

Service Required Drive LEDs

When a fault occurs on a drive in a server, the amber Service Required LED lights on the front of the drive. This amber LED enables you to locate the faulted drive in the system. Additionally, the front and rear panel Service Action Required LEDs also light when the server detects a hard drive fault. Refer to the service manual for the server for the locations and descriptions of these LEDs.

Related Information

■

“Turn On the Locator LED” on page 93

Locate Error Messages Related to Drives in a RAID Volume

When a fault occurs on a drive, error messages are displayed on the system console about the drive and the RAID volume that includes that drive. For example, these messages on a system console display indicate that volume 905 has been degraded with the loss of PhysDiskNum 1:

Mar 16 16:28:26 hostname scsi: /pci@400/pci@2/pci@0/pci@e/scsi@0 (mpt_sas0): Mar 16 16:28:26 hostnamePhysDiskNum 1 with DevHandle 0xc in slot 0 for enclosure with handle 0x0 is now offline Mar 16 16:28:26 hostname scsi: /pci@400/pci@2/pci@0/pci@e/scsi@0 (mpt_sas0): Mar 16 16:28:26 hostnamePhysDiskNum 1 with DevHandle 0xc in slot 0 for enclosure with handle 0x0 is now , active, out of sync Mar 16 16:28:26 hostname scsi: WARNING: /pci@400/pci@2/pci@0/pci@e/scsi@0 (mpt_sas0): Mar 16 16:28:26 hostnameVolume 905 is degraded Mar 16 16:28:26 hostname scsi: /pci@400/pci@2/pci@0/pci@e/scsi@0 (mpt_sas0): Mar 16 16:28:26 hostnameVolume 0 is now degraded Mar 16 16:28:26 hostname scsi: WARNING: /pci@400/pci@2/pci@0/pci@e/scsi@0 (mpt_sas0): Mar 16 16:28:26 hostnameVolume 905 is degraded

Configuring Hardware RAID 89

Page 90

Display Status (FCode-Based RAID Utility)

Display recent system console messages in the /var/adm/messages files.

# more /var/adm/messages*

Refer to the information about these messages and others in the service manual for the server.

Related Information

■

“Monitoring the Server” on page 93

■

“Determining if a Drive Has Failed” on page 88

Display Status (FCode-Based RAID Utility)

You can halt the system and then use the show-volumes command at the OpenBoot prompt to determine if a drive has failed.

Halt the system and display the OpenBoot prompt.

See “Obtain the OpenBoot Prompt Under Various Conditions” on page 19.

Select the SAS controller device for the RAID volume you think has failed.

For example:

ok select /pci@300/pci@1/pci@0/pci@e/scsi@0

See “Prepare to Create a RAID Hardware Volume (FCode-based RAID Utility)” on page 85 for more information.

Display details about the RAID volumes and their associated disks that are handled by this controller.

In the following example, the secondary disk in a RAID 1 volume is offline.

ok show-volumes Volume 0 Target 389 Type RAID1 (Mirroring) Name raid1test WWID 04eec3557b137f31 Degraded Enabled 2 Members 2048 Blocks, 1048 KB Disk 1 Primary Optimal Target c HITACHI H101414SCSUN146G SA25

90 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 91

Display Status (sas2ircu Utility, LSI)

Disk 0 Secondary Offline Out Of Sync Target 0 HITACHI

After you finish typing commands that apply to this controller, unselect it.

ok unselect-dev

Related Info

■

“Locate Device Paths (OpenBoot)” on page 72

■

“Determining if a Drive Has Failed” on page 88

Display Status (sas2ircu Utility, LSI)

Use the LSI sas2ircu utility to display the status of the RAID volume and its associated drives.

Refer to the SAS2 Integrated RAID Solution User Guide for more information about displaying and interpreting device status using the sas2ircu utility.

Related Information

■

“Locate Device Paths (OpenBoot)” on page 72

■

“Determining if a Drive Has Failed” on page 88

RAID Drive Replacement Strategies

When you replace a drive that has been included in a RAID volume, follow the drive replacement instructions in the service manual for the server. Keep in mind these differences if a RAID volume is involved.

■

The cfgadm instructions in the service manual are for individual drives that are not part of RAID volumes. When a drive is part of a RAID volume, you do not need to unconfigure it before hot-swapping it with a new drive.

■

If the failed drive was in a RAID 0 volume, you lose all data on that volume. Replace the failed drive with a new drive of the same capacity. Then recreate the RAID 0 volume (see

“Create a Hardware RAID Volume” on page 86) and restore data from a backup.

Configuring Hardware RAID 91

Page 92

Display Status (sas2ircu Utility, LSI)

■

If the failed drive was in a RAID 1, RAID 1e, or RAID 10 volume, the new drive is automatically configured and synced with the RAID volume. Remove the failed drive and replace it with a new drive of the same capacity. Then allow the RAID volume to automatically incorporate the new drive.

Related Information

■

“Determining if a Drive Has Failed” on page 88

92 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 93

Monitoring the Server

The servers provide many ways to monitor system activity and faulty behavior, including LEDs, Oracle ILOM, and POST. Log files, including system console activity, are maintained by Oracle Solaris and Oracle ILOM. For specific information about LEDs, fault reports, and log files, refer to the topics on detecting and managing faults in the service manual for the server.

Note - You can use Oracle Enterprise Manager Ops Center to monitor this sever along with

other servers and assets. For more information, see “Oracle Enterprise Manager Ops Center

Overview” on page 16.

When a problem is detected on a server, you can use the locator button and LED to identify the server that needs service attention at its physical location.

■

“Turn On the Locator LED” on page 93

■

“Turn Off the Locator LED” on page 94

■

“Display the Locator LED State of the Server” on page 94

Related Information

■

Detecting and managing faults, in the service manual for the server

■

“Matching Devices to Device Names” on page 69

Turn On the Locator LED

When a server must be serviced, lighting the system locator LED assists in easily identifying the correct server. You do not need administrator permissions to use the set /System/ locator_indicator and show /System/locator_indicator commands.

See “Log In to Oracle ILOM” on page 17.

Monitoring the Server 93

Page 94

Turn Off the Locator LED

Illuminate the Locator LED.

-> set /System/locator_indicator=on

Related Information

■

“Turn Off the Locator LED” on page 94

■

“Display the Locator LED State of the Server” on page 94

Turn Off the Locator LED

After service of a server is completed, the Locator LED can be turned off. You do not need administrator permissions to use the set /System/locator_indicator command.

See “Log In to Oracle ILOM” on page 17.

Turn off the Locator LED.

-> set /System/locator_indicator=off

Related Information

■

“Turn On the Locator LED” on page 93

■

“Display the Locator LED State of the Server” on page 94

Display the Locator LED State of the Server

You do not need administrator permissions to use the show /System/locator_indicator command.

See “Log In to Oracle ILOM” on page 17.

Display the state of the Locator LED:

-> show /System/locator_indicator

94 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 95

Related Information

■

“Turn On the Locator LED” on page 93

■

“Turn Off the Locator LED” on page 94

Display the Locator LED State of the Server

Monitoring the Server 95

Page 96

96 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 97

Updating the Firmware

These topics describe how to update the system firmware and view current versions of firmware for Oracle's SPARC and Netra SPARC T5 series servers.

■

“Display the Firmware Versions” on page 97

■

“Update the Firmware” on page 98

Related Information

■

“Understanding System Administration Resources” on page 11

Display the Firmware Versions

The /HOST property displays information about the firmware versions on the host. The output includes the overall system firmware version and the versions of firmware components, such as Oracle ILOM, OpenBoot, and POST.

Display the current host property values.

-> show /HOST

Refer to the Oracle ILOM Administrator's Guide for Configuration and Maintenance for more information about the show /HOST command.

Examine the output to find the version listed for the system firmware or firmware component you wanted.

Related Information

■

“Update the Firmware” on page 98

Updating the Firmware 97

Page 98

Update the Firmware

You must install all the firmware for your server at the same time. You cannot install an individual system firmware component, such as Oracle ILOM.

Download a copy of the system firmware for your server or server module.

Refer to the information about downloading product software and firmware in the product notes for your server or in the Oracle ILOM Administrator's Guide for Configuration and Maintenance.

Update the firmware through the Oracle ILOM CLI or web interface.

Refer to the information about performing firmware updates in the Oracle ILOM Administrator's Guide for Configuration and Maintenance. Ensure that you perform the

preparatory steps described in that document before updating the firmware.

Related Information

■

“Display the Firmware Versions” on page 97

98 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016

Page 99

Glossary

ANSI SIS American National Standards Institute Status Indicator Standard.

ASF Alert standard format (Netra products only).

AWG American wire gauge.

blade Generic term for server modules and storage modules. See server module and storage module.

blade server Server module. See server module.

BMC Baseboard management controller.

BOB Memory buffer on board.

chassis For servers, refers to the server enclosure. For server modules, refers to the modular system

enclosure.

CMA Cable management assembly.

CMM Chassis monitoring module (server modules only). The CMM is the service processor in the

modular system that contains server modules. Oracle ILOM runs on the CMM, providing lights out management of the components in the modular system chassis. See modular system and

Oracle ILOM.

CMP Chip multiprocessor.

Glossary 99

Page 100

DHCP

DHCP Dynamic Host Configuration Protocol.

disk module or disk blade

DTE Data terminal equipment.

Interchangeable terms for storage module. See storage module.

EIA Electronics Industries Alliance.

ESD Electrostatic discharge.

FEM Fabric expansion module (server modules only). FEMs enable server modules to use the

10GbE connections provided by certain NEMs. See NEM.

FRU Field-replaceable unit.

HBA Host bus adapter.

host The part of the server or server module with the CPU and other hardware that runs the Oracle

Solaris OS and other applications. The term host is used to distinguish the primary computer from the SP. See SP.

hot-pluggable Describes a component that can be replaced with power applied, but the component must be

prepared for removal.

hotswappable

Describes a component that can be replaced with power applied, and no preparation is required.

ID PROM Chip that contains system information for the server or server module.

100 SPARC and Netra SPARC T5 Series Servers Administration Guide • August 2016