Oracle Netra SPARC S7-2, SPARC Administration Manual

Download

Page 1

SPARC and Netra SPARC S7-2 Series Servers Administration Guide

Part No: E73202-03

March 2017

Page 2

Page 3

SPARC and Netra SPARC S7-2 Series Servers Administration Guide

Part No: E73202-03

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.

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: E73202-03

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, accorder de licence, 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 livré sous licence au Gouvernement des Etats-Unis, ou à quiconque qui aurait souscrit la licence de ce logiciel 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 un risque de dommages corporels. Si vous utilisez ce logiciel ou ce 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 des applications dangereuses.

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 de 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.

Accès aux services de support Oracle

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 ......................... .................................. 14

Multipathing Software Overview ................................ .................... .................. 15

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

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

Oracle Auto Service Request Software Overview .......... ...................................... 17

Trusted Platform Module Overview .......................... .................... .................... 18

Accessing the Server .. ..................................................................... ................. 19

▼ Log In to Oracle ILOM ................ ............................................................. 19

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

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

▼ Display the Oracle ILOM Prompt ................ ............................................... 22

Oracle ILOM Remote System VNC Console ...................................................... 23

Controlling the Server .......................................... .................... ......................... 25

Powering the Server On and Off .............................................. ........................ 25

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

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

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

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

Page 6

Contents

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

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

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

SPARC) ........................ ..................................................................... .. 29

Resetting the Server and SP ... .................... ..................................................... 30

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

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

▼ Reset the SP ............................. ....................................................... 32

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 ............... ........................................... 46

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 .... ........................................ 53

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

6 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 7

Contents

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

▼ Change Server Identifier Information .................................... ....................... 55

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 ............................................ ......... 60

▼ 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 .............................................. 66

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

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

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

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

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

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

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

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

Managing Server Drives .... .................... ............................................................ 77

Hardware RAID Support ................. ............................................................... 77

Managing NVMe Devices ........ ..................................................................... .. 77

Monitoring the Server ...................... ................................................................. 79

▼ Turn On the Locator LED ................................................ ......................... 79

Page 8

Contents

▼ Turn Off the Locator LED ....................... .................................................. 80

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

Updating the Firmware ............. ..................................................................... .... 83

▼ Display the Firmware Versions ................... ................................................ 83

▼ Update the Firmware .................................................................... ............ 84

Index ................................... ..................................................................... .......... 87

8 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 9

Using This Documentation

■

Overview – Describes how to configure and administer the SPARC and Netra SPARC S7-2 series servers from Oracle.

■

Audience – System administrators of SPARC and Netra SPARC S7-2 series servers.

■

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

Note - This document applies to several server products. Specific examples used in this

document are based on one of these servers. Your output might vary from the examples based on your product.

Product Documentation Library

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

■

http://www.oracle.com/goto/s7-2/docs

■

http://www.oracle.com/goto/s7-2l/docs

■

http://www.oracle.com/goto/netra-s7-2/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 S7-2 Series Servers Administration Guide • March 2017

Page 11

Understanding System Administration Resources

These topics provide a summary of common tools and features involved in administering the server.

Note - For an overview of your specific server, refer to the "Understanding The Server" section

of the installation guide for that 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 14

■

“Multipathing Software Overview” on page 15

■

“Oracle Hardware Management Pack Overview” on page 15

■

“Oracle Enterprise Manager Ops Center Overview” on page 16

■

“Oracle Auto Service Request Software Overview” on page 17

■

“Trusted Platform Module Overview” on page 18

Related Information

■

“Updating the Firmware” on page 83

Oracle ILOM Overview

Oracle ILOM is system management firmware that is preinstalled on all the servers. This firmware 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.

Understanding System Administration Resources 11

Page 12

Oracle Solaris OS Overview

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. 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 server's SP through Oracle ILOM commands. Regardless of the host's power state, you can log into the ILOM CLI through the SER MGT port or NET MGT port.

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. Most features are common to all platforms, but some Oracle ILOM features belong to only a subset of platforms.

Note - For certain procedures included in the Oracle ILOM 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 19

■

“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 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

12 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 13

OpenBoot Overview

Note - Oracle Solaris 10 can only be used in guest domains on these servers.

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.

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

Oracle Solaris 11.3 also includes Oracle VM Server for SPARC and the Oracle Hardware Management Pack.

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).

Note - The OpenBoot firmware is based on the IEEE Standard 1275-1994 for Boot

(Initialization Configuration) Firmware: Core Requirements and Practices specification.

New OpenBoot properties are available on this server to accomodate booting an iSCSI device over IB. Also, a new OpenBoot variable has been added.

■

boot-pool-list - Lists device paths to OpenBoot accessible storage devices that comprise a boot pool. These are the devices that Oracle Solaris uses when booting. You can view this property with the .properties command under the /chosen node at the OpenBoot prompt.

■

tboot-list - Lists storage devices that include fall back images. You can view this property with the .properties command under the /chosen node at the OpenBoot prompt.

■

os-root-device - Defines devices and root file systems for root pools. This is a nonvolatile variable that you can view using the printenv command at the OpenBoot prompt or using the eeprom command at the Oracle Solaris prompt.

Understanding System Administration Resources 13

Page 14

Oracle VM Server for SPARC Overview

For more information about OpenBoot commands, refer to the OpenBoot documentation at:

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

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 OS, 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 SP, and specify a configuration to be used. You can also specify an Oracle VM Server for SPARC 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 since 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 28

■

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

14 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 15

■

“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 (HBAs) connected to the same dual-ported storage array.

For the servers, 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 Oracle Solaris Administration: Network Services and Network Virtualization.

■

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.

Multipathing Software Overview

Related Information

■

“Oracle Solaris OS Overview” on page 12

■

“Oracle VM Server for SPARC Overview” on page 14

Oracle Hardware Management Pack Overview

The Oracle Hardware Management Pack provides tools to manage and configure Oracle servers from the host OS. Oracle Solaris includes Oracle Hardware Management Pack starting with Oracle Solaris 11.2. The tools include a utility for managing NVMe devices (nvmeadm) and for updating firmware in various hardware devices in the server (fwupdate).

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

Understanding System Administration Resources 15

Page 16

Oracle Enterprise Manager Ops Center Overview

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

Related Information

■

“Managing Server Drives” on page 77

■

“Update the Firmware” on page 84

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 OSs, virtualization technologies, Oracle servers, storage, and networks.

Oracle Enterprise Manager Ops Center can discover a server, its SP, the OS, 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 How To guide that applies to your server. 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 3:

http://docs.oracle.com/cd/E59957_01/nav/deploy.htm

Related Information

■

“Hardware RAID Support” on page 77

16 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 17

Oracle Auto Service Request Software Overview

When you have completed initial installation and Oracle Solaris configuration, you can activate Oracle Auto Service Request (Oracle ASR) software for the server.

Oracle ASR software provides the ability to resolve problems faster by automatically opening service requests for Oracle's qualified server, storage, and Engineered Systems products when specific faults occur.

Parts are dispatched upon receipt of a service request sent by Oracle ASR. In many cases, Oracle engineers are already working to resolve an issue before you're even aware that a problem exists.

Oracle products with Oracle ASR securely transport electronic fault telemetry data to Oracle automatically to help expedite the diagnostic process. The one-way event notification requires no incoming internet connections or remote access mechanism. Only the information needed to solve a problem is communicated to Oracle.

Oracle ASR is a feature of the Oracle hardware warranty, Oracle Premium Support for Systems, and Oracle Platinum Services.

■

https://www.oracle.com/support/premier/systems/index.html

■

https://www.oracle.com/support/premier/engineered-systems/index.html

Oracle ASR is integrated with My Oracle Support (https://support.oracle.com). You must use My Oracle Support to activate your ASR assets, such as a new server.

To activate automated support for a server, download software and find additional information at:

http://oracle.com/us/support/auto-service-request/index.html

Some resources available for Oracle ASR through that site are:

■

Oracle ASR Documentation

http://docs.oracle.com/cd/E37710_01/index.htm

■

How to Approve Pending ASR Assets in My Oracle Support (DOC ID 1329200.1)

https://support.oracle.com/rs?type=doc&id=1329200.1

Related Information

■

Oracle Auto Service Request Documentation

Understanding System Administration Resources 17

Page 18

Trusted Platform Module Overview

http://docs.oracle.com/cd/E37710_01/index.htm

■

“Oracle Enterprise Manager Ops Center Overview” on page 16

Trusted Platform Module Overview

The server includes a Trusted Platform Module (TPM) as part of the SP. TPM refers to the device, as well as the implementation, by which encrypted configuration information specific to the system is stored. The information serves as metrics against which processes are measured during system boot.

Oracle Solaris uses TPM to securely store encryption keys. TPM, together with the other measures that are described in the Oracle Solaris documentation, secures the system from unauthorized access by users of applications.

The platform owner must initialize TPM by setting an owner password that is used to authorize privileged operations. The platform owner, also called the TPM owner, differs from the traditional superuser.

Related Information

■

Securing Systems and Attached Devices in Oracle Solaris 11.3 in the Oracle Solaris 11.3 documentation

18 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 19

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 19

■

“Log In to the System Console” on page 20

■

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

■

“Display the Oracle ILOM Prompt” on page 22

■

“Oracle ILOM Remote System VNC Console” on page 23

Related Information

■

“Accessing the Server” on page 19

■

“Booting and Shutting Down the OS” on page 33

Log In to Oracle ILOM

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

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) ... Oracle(R) Integrated Lights Out Manager Version 3.2.x.x Copyright (c) 2016, Oracle and/or its affiliates. All rights reserved. ...

Accessing the Server 19

Page 20

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 20

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 see the OpenBoot prompt (ok) unless Oracle Solaris is running.

Related Information

■

“Display the Oracle ILOM Prompt” on page 22

■

“Oracle ILOM Remote System VNC Console” on page 23

■

“Log In to Oracle ILOM” on page 19

20 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 21

Obtain the OpenBoot Prompt Under Various Conditions

This procedure presents several ways to reach the OpenBoot prompt, in order of preference, starting with a method that performs the most graceful shutdown of the OS. Some other methods to perform a graceful shutdown to reach the OpenBoot prompt are described in

“Obtaining the OpenBoot Prompt” on page 38.

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.

Shut down the OS at the host prompt.

From a shell or command tool window, type an appropriate OS command (for example, shutdown or init 0).

For details on shutting down the OS, see:

■

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

■

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

At the Oracle ILOM prompt, type:

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

This setting ensures that you reach the OpenBoot prompt rather than having the OS boot automatically. This change applies only to a single reset and expires in 10 minutes if the power on the host is not reset.

Type:

-> stop /System

The OpenBoot prompt (ok) appears.

If the OS was unresponsive and you were not able to reach the OpenBoot prompt, continue to the next steps in this procedure.

At the Oracle ILOM prompt, type:

-> set /HOST send_break_action=break

-> start /HOST/console

Accessing the Server 21

Page 22

Display the Oracle ILOM Prompt

You should now see the OpenBoot prompt. If the server is still not responding, perform the next steps.

If more than 10 minutes have passed since you typed the following command, do so again.

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

Type:

-> reset /System

-> start /HOST/console

Related Information

■

“Obtaining the OpenBoot Prompt” on page 38

■

“Monitoring the Server” on page 79

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 19.

Related Information

■

“Oracle ILOM Overview” on page 11

■

“Log In to Oracle ILOM” on page 19

■

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

22 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 23

Oracle ILOM Remote System VNC Console

Oracle ILOM Remote System VNC Console is an implementation of the Virtual Network Computing (VNC) system. It enables you to remotely redirect the host server keyboard, video, and mouse (KVM) events to a graphical shared desktop display.

Note - Oracle ILOM also provides Oracle ILOM Remote System Console Plus, but the servers

only support this for serial line redirection. The servers do not support the older Oracle ILOM Remote System Console and Oracle ILOM Storage Redirection CLI features.

To connect to the Oracle ILOM Remote System VNC Console, refer to the Configuration and Maintenance Guide for the Oracle ILOM release.

Related Information

■

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

Accessing the Server 23

Page 24

24 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 25

Controlling the Server

These topics describe how to control basic server operations.

■

“Powering the Server On and Off” on page 25

■

“Resetting the Server and SP” on page 30

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 26

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

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 27

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

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

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

Related Information

■

“Resetting the Server and SP” on page 30

Controlling the Server 25

Page 26

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 19.

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 26

■

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

■

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

Power Off the Server (Oracle ILOM CLI)

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

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

26 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 27

Power On the Server (Oracle ILOM Web Interface)

{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 the Server (Oracle ILOM Web Interface)” on page 27

■

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

■

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

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 19.

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 26

■

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

■

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

Controlling the Server 27

Page 28

Power Off the Server (Oracle ILOM Web Interface)

Shut down Oracle Solaris.

See:

■

“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 26

■

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

■

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

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 19.

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

28 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 29

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

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 29

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.

Controlling the Server 29

Page 30

Resetting the Server and SP

# 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.

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 28

Resetting the Server and SP

Use these topics to reset the server or SP.

30 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 31

Reset the Server (Oracle Solaris)

■

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

■

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

■

“Reset the SP” on page 32

Related Information

■

“Powering the Server On and Off” on page 25

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.

Reset the server from the Oracle Solaris prompt, by typing one of these commands:

■

# shutdown -g0 -i6 -y

■

# reboot

Related Information

■

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

■

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

■

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

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.

Controlling the Server 31

Page 32

Reset the SP

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 19.

Type one of these commands to reset the server.

■ 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 26

■

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

■

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

■

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

Reset the SP

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

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

Reset the SP.

-> reset /SP

Related Information

■

“Log In to Oracle ILOM” on page 19

32 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

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 included, 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 25

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 25

■

“Obtaining the OpenBoot Prompt” on page 38

Booting and Shutting Down the OS 33

Page 34

Booting and Shutting Down Oracle Solaris

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 46):

■

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.

Note - Each logical domain provides a virtualized form of OpenBoot commands.

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 S7-2 Series Servers Administration Guide • March 2017

Page 35

Boot the OS (Oracle ILOM)

Note - Oracle Solaris 10 can only be used in guest domains on these servers.

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 19.

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 products. The following example is based on the

SPARC S7-2 server. 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. Sep 21 13:31:37 The system is down. Shutdown took 23 seconds. syncing file systems... done Program terminated

36 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 37

Shut Down the OS (shutdown Command)

SPARC S7-2, No Keyboard ... {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 products. The following example is based on the

SPARC S7-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  SPARC S7-2, No Keyboard ... {0} ok

Related Information

■

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

Booting and Shutting Down the OS 37

Page 38

Obtaining the OpenBoot Prompt

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

Note - If you have any problems reaching the OpenBoot Prompt by your chosen method, refer

to some alternatives in “Obtain the OpenBoot Prompt Under Various Conditions” on page 21.

■

“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 19

■

“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.

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

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

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 46

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

Run diagnostics. Refer to the service manual for your server, detecting and managing

faults.

38 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 39

Obtain the OpenBoot Prompt (Oracle Solaris)

Task For More Information

Reset and power off the host.

Eject media.

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.

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 Under Various Conditions” on page 21

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. 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.

Booting and Shutting Down the OS 39

Page 40

Obtain the OpenBoot Prompt (Oracle ILOM CLI)

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 Under Various Conditions” on page 21

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 19.

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

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

40 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 41

Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)

■

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

■

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

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 19.

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

The Host Boot Mode page is displayed.

For Script, type: setenv auto-boot? false

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

Click Save to save this new setting.

In the left navigation panel, choose Host Management → Power Control.

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

In the left navigation panel, choose 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

Booting and Shutting Down the OS 41

Page 42

Obtain the OpenBoot Prompt (Oracle ILOM Web Interface)

■

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

42 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

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 53

■

“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

Configuring Boot and Restart Behavior 43

Page 44

Change the Default Boot Device (OpenBoot)

■

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

■

“View All OpenBoot Parameters” on page 46

■

“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.

Reset the host.

ok reset-all

Related Information

■

“printenv Output” on page 48

44 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 45

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.

Note - To enable automatic booting of the OS, the Oracle ILOM auto-boot property also must

be enabled. You can change the Oracle ILOM auto-boot property at /HOST/domain/control.

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

Reset the host.

ok reset-all

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

Related Information

■

“printenv Output” on page 48

■

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

Configuring Boot and Restart Behavior 45

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 poweron either attempts to boot automatically, or not. This change is permanent but only takes effect after a host reset.

Note - To enable automatic booting of the OS, the Oracle ILOM auto-boot property also must

be enabled. You can change the Oracle ILOM auto-boot property at /HOST/domain/control.

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

View All OpenBoot Parameters

View all of the OpenBoot parameters.

46 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 47

■ From the OpenBoot prompt, type: printenv

■ From Oracle Solaris, type: eeprom

View the value for an individual OpenBoot parameter.

■ 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

View All OpenBoot 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 CD-ROM.

■

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

■

boot tape – Boots default file from tape.

Configuring Boot and Restart Behavior 47

Page 48

View All OpenBoot Parameters

Parameter Default Value Description

■

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

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

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 on a SPARC S7-2 server. The output for each server might be different.

{0} ok printenvVariable 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 oem-banner No default oem-banner? false false ansi-terminal? true true screen-#columns 80 80 screen-#rows 34 34

48 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 49

Boot Mode Overview (Oracle ILOM)

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 os-root-device network-boot-arguments boot-command boot boot boot-file boot-device /pci@300/pci@2/pci@0/pci ... disk net multipath-boot? false false boot-device-index 0 0 use-nvramrc? false false nvramrc error-reset-recovery boot boot

If any value in the printenv output is truncated, you can see the full entry by typing printenv followed by the variable name. For example:

{0} ok printenv boot-device boot-device = /pci@302/pci@2/pci@0/pci@17/LSI,sas@0/disk@p2 disk net

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.

Configuring Boot and Restart Behavior 49

Page 50

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

The bootmode command is intended only to correct a problem with the OpenBoot or Oracle VM Server for SPARC settings, so 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 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 31

■

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

■

“OpenBoot Overview” on page 13

■

“Oracle VM Server for SPARC Overview” on page 14

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

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

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

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

Power cycle or reset the server when you are ready to boot with the selected configuration.

50 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 51

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

Related Information

■

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

■

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

■

“Oracle VM Server for SPARC Overview” on page 14

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 '', which indicates an empty script.

Related Information

■

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

■

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

■

“Oracle VM Server for SPARC Overview” on page 14

Manage the Host Boot Mode Script (Oracle ILOM)

At the Oracle ILOM prompt, type:

Configuring Boot and Restart Behavior 51

Page 52

Display the Host Boot Mode Expiration Date (Oracle ILOM)

-> 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.

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 value of the state property, the result is that all OpenBoot variables are set to the default value. Then Openboot reads the value of the state property, resulting in the diag-switch? variable being set 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 31

■

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

■

“Oracle VM Server for SPARC Overview” on page 14

Display the Host Boot Mode Expiration Date (Oracle ILOM)

At the Oracle ILOM prompt, type:

-> show /HOST/bootmode expires Properties: expires = Tue May 10 18:24:16 2016

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

Related Information

■

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

■

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

■

“Oracle VM Server for SPARC Overview” on page 14

52 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 53

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.

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 14

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 behaves 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 30

Configuring Boot and Restart Behavior 53

Page 54

54 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 55

Changing Server Identification Information

This topic describes how to store information (for purposes such as inventory control or site resource management) on the SP using the Oracle ILOM CLI interface.

■

“Change Server Identifier Information” on page 55

Related Information

■

“Turn On the Locator LED” on page 79

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 19

Changing Server Identification Information 55

Page 56

56 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

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 60

■

“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 turns 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 28

■

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

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, Oracle ILOM 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 S7-2 Series Servers Administration Guide • March 2017

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.

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 powered off when power is applied.

Related Information

■

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

■

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

Specify the Host Power State at Restart

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 poweron delay is important when multiple servers in racks power on after a power outage.

At the Oracle ILOM prompt, type:

-> 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

Configuring Policy Settings 59

Page 60

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.

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 27

■

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

■

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

■

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

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 poweron is allowed. This value overrides the settings of /HOST/diag target, resulting in Max POST being executed.

■

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

60 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 61

Reset the Values in the SP to Default Values

Related Information

■

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

■

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

■

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

■

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

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 different than in some past products, where 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 19.

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 – Changes SP and OpenBoot to factory default configuration and clears all SP 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 26

Configuring Policy Settings 61

Page 62

62 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

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 server 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 this 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 the server.

■

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.

■

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

Management” on page 66.

Configuring SP and Host Network Addresses 63

Page 64

Disable or Reenable Network Access to the SP

Related Information

■

Oracle ILOM Documentation

■

“Oracle ILOM Overview” on page 11

■

“Log In to Oracle ILOM” on page 19

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 19

■

“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:

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.

64 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 65

For example:

dhcp_server_ip = 10.x.x.x

Related Information

■

“Log In to Oracle ILOM” on page 19

■

“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) and then stored as a property in Oracle ILOM.

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).

Display the Host MAC Address

At the Oracle ILOM prompt, type:

-> show /HOST macaddress

Related Information

■

“Log In to Oracle ILOM” on page 19

■

“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.

■

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

■

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

Related Information

■

“Accessing the Server” on page 19

Configuring SP and Host Network Addresses 65

Page 66

Configure SP In-band (Sideband) Access

Oracle ILOM In-band (Sideband) Management

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 10 Gigabit Ethernet ports (named NET 0, NET 1, NET 2, and NET 3), 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, these 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 OS might not be supported by the onboard host 10 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 10 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 66

■

“SP Network Address Options” on page 63

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.

Connect to Oracle ILM through the SER MGT port.

Refer to the installation guide for your server to connectoo to the SER MGT port.

66 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 67

Configure SP In-band (Sideband) Access

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

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 = MGMT ... pendingmanagementport = MGMT ...

MGMT indicates the NET MGT port.

Configure a network port for the SP.

Type a port value of NET0, NET1, NET2, or NET3.

-> set /SP/network pendingmanagementport=port

Configure ipaddress and ipconfig as needed.

Refer to the section about assign an IP address in the installation guide the server.

Commit the network configuration changes.

->set /SP/network commitpending=true

Verify the change.

-> show /SP/network

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

managementport = NET0 ... pendingmanagementport = NET0

Related Information

■

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

■

“SP Network Address Options” on page 63

Configuring SP and Host Network Addresses 67

Page 68

68 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

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 70

■

“Locate Device Paths (OpenBoot)” on page 73

■

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

■

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

Related Information

■

“Configuring SP and Host Network Addresses” on page 63

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).

■

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.

Matching Devices to Device Names 69

Page 70

WWN Syntax

Related Information

■

“WWN Syntax” on page 70

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. These 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.

■

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

Related Information

■

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

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:

70 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 71

Display Server Components (Oracle ILOM)

Note - This document applies to several server products. The following example is based on the

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

-> show components Target | Property | Value

Matching Devices to Device Names 71

Page 72

Display Server Components (Oracle ILOM)

72 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 73

Related Information

■

“Locate Device Paths (OpenBoot)” on page 73

Locate Device Paths (OpenBoot)

Display the OpenBoot prompt.

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

From the OpenBoot prompt, type:

Note - This document applies to several server products. The following example is based on the

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

ok devalias fallback-miniroot /pci@300/pci@1/pci@0/pci@2/usb@0/hub@2/storage@1/disk@0 rcdrom /pci@300/pci@1/pci@0/pci@2/usb@0/hub@2/storage@1/disk@0 disk7 /pci@302/pci@2/pci@0/pci@14/LSI,sas@0/disk@p4 disk6 /pci@302/pci@2/pci@0/pci@14/LSI,sas@0/disk@p5 disk5 /pci@302/pci@2/pci@0/pci@14/LSI,sas@0/disk@p7 disk4 /pci@302/pci@2/pci@0/pci@14/LSI,sas@0/disk@p6 disk3 /pci@302/pci@2/pci@0/pci@14/LSI,sas@0/disk@p0 disk2 /pci@302/pci@2/pci@0/pci@14/LSI,sas@0/disk@p1 disk1 /pci@302/pci@2/pci@0/pci@14/LSI,sas@0/disk@p3 disk /pci@302/pci@2/pci@0/pci@14/LSI,sas@0/disk@p2 disk0 /pci@302/pci@2/pci@0/pci@14/LSI,sas@0/disk@p2 sas0 /pci@302/pci@2/pci@0/pci@14/LSI,sas@0 sas /pci@302/pci@2/pci@0/pci@14/LSI,sas@0 nvme3 /pci@302/pci@2/pci@0/pci@7/nvme@0/disk@1

Matching Devices to Device Names 73

Page 74

probe-scsi-all Device Naming (OpenBoot)

nvme2 /pci@302/pci@2/pci@0/pci@6/nvme@0/disk@1 nvme1 /pci@300/pci@2/pci@0/pci@5/nvme@0/disk@1 nvme0 /pci@300/pci@2/pci@0/pci@4/nvme@0/disk@1 net3 /pci@300/pci@1/pci@0/pci@1/network@0,3 net2 /pci@300/pci@1/pci@0/pci@1/network@0,2 net1 /pci@300/pci@1/pci@0/pci@1/network@0,1 net /pci@300/pci@1/pci@0/pci@1/network@0 net0 /pci@300/pci@1/pci@0/pci@1/network@0 virtual-console /virtual-devices/console@1 name aliases

Related Information

■

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

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

Each SAS drive is assigned a unique target ID.

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

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

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

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 server's service manual for a description of the physical drive slot

organization.

74 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 75

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

Related Information

■

“WWN Syntax” on page 70

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

At the OpenBoot prompt, type:

ok probe-scsi-all /pci@302/pci@2/pci@0/pci@14/LSI,sas@0

FCode Version 1.00.65, MPT Version 2.05, Firmware Version 9.00.00.00

Target 9 Unit 0 Disk HGST H101860SFSUN600G A3T0 1172123568 Blocks, 600 GB SASDeviceName 5000cca02f0256b8 SASAddress 5000cca02f0256b9 PhyNum 0 Target a Unit 0 Disk HGST H101860SFSUN600G A3T0 1172123568 Blocks, 600 GB SASDeviceName 5000cca02f02564c SASAddress 5000cca02f02564d PhyNum 1 Target b Unit 0 Disk HGST H101860SFSUN600G A770 1172123568 Blocks, 600 GB SASDeviceName 5000cca02f1390f4 SASAddress 5000cca02f1390f5 PhyNum 2 Target c Unit 0 Disk HGST H101860SFSUN600G A770 1172123568 Blocks, 600 GB SASDeviceName 5000cca02f1376d8 SASAddress 5000cca02f1376d9 PhyNum 3 Target d Unit 0 Disk HGST H101860SFSUN600G A3T0 1172123568 Blocks, 600 GB SASDeviceName 5000cca02f027838 SASAddress 5000cca02f027839 PhyNum 4 Target e Unit 0 Disk HGST H101860SFSUN600G A3T0 1172123568 Blocks, 600 GB SASDeviceName 5000cca02f02e798 SASAddress 5000cca02f02e799 PhyNum 5 Target f Unit 0 Disk HGST H101860SFSUN600G A3T0 1172123568 Blocks, 600 GB SASDeviceName 5000cca02f02b138 SASAddress 5000cca02f02b139 PhyNum 6 Target 10 Unit 0 Disk HGST H101860SFSUN600G A3T0 1172123568 Blocks, 600 GB SASDeviceName 5000cca02f028fd0 SASAddress 5000cca02f028fd1 PhyNum 7

/pci@300/pci@1/pci@0/pci@2/usb@0/storage@1 Unit 0 Disk smiMICRON eUSB DISK 1112

/pci@300/pci@1/pci@0/pci@2/usb@0/hub@2/storage@1 Unit 0 Removable Read Only device SUNRemote ISO CDROM1.01

Matching Devices to Device Names 75

Page 76

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

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).

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

where n is the SAS controller number.

■

tWWN = t5000cca02f0256b8

where WWN is the SASDeviceName value.

■

dn = d0

where n is 0 for all embedded SCSI devices.

The completed logical device name is c0t5000cca02f0256b8d0.

Related Information

■

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

76 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 77

Managing Server Drives

These topics describe how to configure and manage server drives.

■

“Hardware RAID Support” on page 77

■

“Managing NVMe Devices” on page 77

Related Information

■

“Matching Devices to Device Names” on page 69

Hardware RAID Support

These servers, unlike some past SPARC servers, do not provide built-in hardware RAID support. You cannot use the hardware RAID functions that were provided through Fcode-based RAID utilities and commands such as create-raid1-volume).

In place of hardware RAID, consider using the ZFS capabilities provided in Oracle Solaris. For information about creating Oracle Solaris ZFS storage pools and root pools, refer to Managing ZFS File Systems in Oracle Solaris 11.3 at http://docs.oracle.com/cd/E53394_01.

Related Information

■

“Managing NVMe Devices” on page 77

Managing NVMe Devices

NVMe drives and cards will work with most commands available for a SAS or SATA drive or SSD. In addition, on NVMe devices, you can use the nvmeadm command that is provided in the

Managing Server Drives 77

Page 78

Managing NVMe Devices

Oracle Hardware Management Pack, which is included in Oracle Solaris 11.3. For details on using nvmeadm, refer to the Oracle Server CLI Tools for Oracle Solaris 11.3 User's Guide.

Related Information

■

“Hardware RAID Support” on page 77

78 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 79

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 server 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 79

■

“Turn Off the Locator LED” on page 80

■

“Display the Locator LED State of the Server” on page 80

Related Information

■

Detecting and managing faults, in the service manual for your server

■

“Matching Devices to Device Names” on page 69

Turn On the Locator LED

When a server must be serviced, lighting the server 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 19.

Monitoring the Server 79

Page 80

Turn Off the Locator LED

Illuminate the Locator LED.

-> set /System locator_indicator=on

Related Information

■

“Turn Off the Locator LED” on page 80

■

“Display the Locator LED State of the Server” on page 80

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 19.

Turn off the Locator LED.

-> set /System locator_indicator=off

Related Information

■

“Turn On the Locator LED” on page 79

■

“Display the Locator LED State of the Server” on page 80

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 19.

Display the state of the Locator LED:

-> show /System locator_indicator

Related Information

■

“Turn On the Locator LED” on page 79

80 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 81

■

“Turn Off the Locator LED” on page 80

Display the Locator LED State of the Server

Monitoring the Server 81

Page 82

82 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 83

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 S7-2 series servers.

■

“Display the Firmware Versions” on page 83

■

“Update the Firmware” on page 84

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.

Note - You also can determine the versions of firmware in the server and of specific

components, such as a drive controller, with the fwupdate command. The fwupdate command is provided in the Oracle Hardware Management Pack, which is included in Oracle Solaris 11.3. For details on using fwpudate, refer to the Oracle Server CLI Tools for Oracle Solaris 11.3 User's Guide.

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.

Updating the Firmware 83

Page 84

Update the Firmware

Related Information

■

“Update the Firmware” on page 84

Update the Firmware

The Live Firmware update feature of the SPARC M7, T7, and S7 series servers supports updating Sun System firmware while the SPARC host is powered on. The Oracle ILOM firmware update goes into immediate effect. However, the host components update is delayed until the affected host is power cycled. Because Oracle ILOM can be updated while the host is powered on, this feature reduces the total system down time.

Note - For SPARC T7 servers the Live Firmware Update feature requires a minimum Sun

System Firmware version of 9.5.2.g.

Check the current system firmware version. From the Oracle ILOM command prompt, type:

-> show /HOST

Download the latest available system firmware version from My Oracle Support at:

https://support.oracle.com

Then place the SysFW image in a shared location the host can access, for example, a local or network share or on a TFTP, FTP, HTTP or HTTPS server.

Notify SP users of the scheduled firmware update and ask them to close all client sessions until after the firmware update is complete. Do not perform any other Oracle ILOM tasks during the firmware update.

Update the firmware through the Oracle ILOM CLI.

For information about performing firmware updates using the web interface, see Update

the Server SP or CMM Firmware Image in the Oracle ILOM Administrator's Guide for

Configuration and Maintenance Firmware Release 3.2.x.

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

Load the firmware image from the shared location. Type:

load -source protocol://username:password@server_ip/path_to_image/image.pkg

84 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 85

Update the Firmware

A series of prompts appear.

Type y to load the image file, then type y to enable the Preserve Configuration option, which saves and restores the existing Oracle ILOM firmware settings after the firmware update is complete.

Note - All firmware update options for your server are enabled (y) by default when using a

script (-script) to perform the firmware update.

Oracle ILOM displays a status message when the firmware process is complete. The system will reboot to apply the new firmware image.

Related Information

■

“Display the Firmware Versions” on page 83

Updating the Firmware 85

Page 86

86 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 87

Index

accessing the server, 19 auto-boot? parameter, 45, 46

boot mode

expiration date, 52 managing at reset, 51 managing configuration, 50 managing script, 51 managing server, 43 Oracle VM Server for SPARC, 50 overview, 49

booting

automatic booting, 45, 46 boot parameters, 43 boot sequence, 34 changing boot device, 44 configuring, 43 from OpenBoot prompt, 35 from Oracle ILOM, 35 how to boot and shut down, 33

components, displaying names, 70 cooldown mode, policy setting, 57

device names, 69 device paths, 73 DHCP server, displaying IP address, 64 domains, multiple active, 28, 29 drive management, 77

ejecting media, 38

fault detection, 79 firmware

displaying version, 83 updating, 83, 84

fwupdate command, 83

hardware RAID, 77 host network address, 63 host power state at restart

restoring, 58 specifying in policy setting, 59

host power-on delay, policy setting, 59

devalias command, 73

ID, changing, 55 in-band connection, 65, 66, 66

Page 88

Index

keyswitch, specifying host behavior, 60 KVM, 23

Live Firmware update, 84 Locator LED, 79, 80, 80 log files, for monitoring the server, 79

MAC address, host, 65 monitoring the server, 79 multipathing software, 15

network access to SP, 64 network address, 63, 63 NVMe devices, 77 nvmeadm command, 77

OpenBoot

auto-boot? parameter, 45, 46 devalias command, 73

displaying version, 83 overview, 13 parameters, 46, 47

printenv command, 48 probe-scsi-all command, 74, 75

prompt, 21, 38, 38, 39, 40, 41 reset override, 53

uses, 38 Oracle Auto Service Request, 17 Oracle Enterprise Manager Ops Center, 16 Oracle Hardware Management Pack, 15 Oracle ILOM

accessing, 22 accessing the system console, 20 configuring restart behavior, 53 default username and password, 19 displaying components, 70 logging in to, 19 overview, 11 parallel boot policy, 60 policy settings, 57

prompt, 11, 20, 22 Oracle ILOM Remote System VNC Console, 23 Oracle Solaris

booting, 33

init command, 36

overview, 12

shutdown command, 37

shutting down, 33, 36, 37 Oracle VM Server for SPARC

overview, 14

powering off, 29

powering on, 28

parallel boot, 60 physical device names, 69 policy settings, 57 POST, displaying version, 83 powering off, 25, 26, 28, 29 powering on, 25, 26, 27, 28

printenv command, 48 probe-scsi-all command, 74, 75

RAID, 77 resetting

changing behavior, 51

from OpenBoot prompt, 38

overview, 30

SP, 32

SP values, 61

88 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017

Page 89

Index

server

accessing, 19 changing identifier, 55 controlling, 25, 33 resetting

from Oracle ILOM, 31 from Oracle Solaris, 31

shutting down Oracle Solaris

init command, 36 shutdown command, 37

sideband connection, 65, 66, 66 SP

network access, 64 network address, 63, 63 reset values, 61

resetting, 30, 32 system administration overview, 11 system communication, 19 system console, logging in, 20

TPM, 18 Trusted Platform Module, 18

ZFS, 77

updating firmware, 83, 84

virtual keyswitch, 60 VNC, 23

WWN device names

probe-scsi-all command, 75

syntax, 70

Page 90

90 SPARC and Netra SPARC S7-2 Series Servers Administration Guide • March 2017