Sun Microsystems Ultra Enterprise 10000 User Guide
Ultra™Enterprise™10000
SSP 3.1 User’s Guide
Sun Microsystems Computer Company
A Sun Microsystems, Inc. Business
901 San Antonio Road
Palo Alto, CA 94303 USA
650 960-1300 fax 650 969-9131
Part No: 805-2955-10
Revision A, December 1997
Copyright 1997 Sun Microsystems, Inc., 901 San Antonio Road, PaloAlto, California 94303 U.S.A.All rights reserved.
This product or document is protectedby copyright and distributed under licenses restricting its use, copying, distribution, and decompilation.
No part of this productor document may be reproducedinany form by any means without prior written authorization of Sun and itslicensors,
if any.Third-partysoftware,includingfonttechnology, is copyrighted and licensed from Sun suppliers.
Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registeredtrademark in
the U.S. and other countries, exclusively licensed through X/Open Company, Ltd.
Sun,Sun Microsystems, the Sun logo, SunSoft, SunDocs,SunExpress,Solaris, Ultra Enterprise, and OpenBoot PROM aretrademarks, registered
trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries.All SPARCtrademarksareused under license and are
trademarks or registered trademarks of SPARCInternational, Inc. in theU.S. and other countries. Products bearingSPARCtrademarksare
based upon an architecture developed by Sun Microsystems, Inc.
The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges
the pioneering efforts of Xerox in researchingand developing the concept ofvisual or graphical user interfaces for the computer industry. Sun
holds a non-exclusive license fromXeroxto the Xerox Graphical User Interface, which license also covers Sun’s licensees who implementOPEN
LOOK GUIs and otherwise complywith Sun’s written licenseagreements.
RESTRICTEDRIGHTS: Use, duplication, or disclosure by the U.S.Government is subject to restrictions of FAR52.227-14(g)(2)(6/87) and
FAR52.227-19(6/87),orDFAR252.227-7015(b)(6/95)andDFAR227.7202-3(a).
DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,
INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSEORNON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Copyright 1997 Sun Microsystems, Inc., 901 San Antonio Road, PaloAlto, Californie 94303 Etats-Unis.Tousdroitsréservés.
Ce produit ou document est protégé par un copyrightet distribué avec des licencesqui en restreignent l’utilisation, la copie, ladistribution, et la
décompilation. Aucune partie de ceproduit ou document ne peutêtre reproduitesous aucune forme, par quelque moyen que ce soit, sans
l’autorisation préalable et écrite deSun et de sesbailleurs de licence, s’il y en a. Le logiciel détenu par des tiers,et qui comprend la technologie
relativeaux polices de caractères, est protégépar un copyright et licencié par des fournisseurs de Sun.
Des parties de ce produitpourrontêtredérivées des systèmes Berkeley BSDlicenciés par l’Université de Californie. UNIX est une marque
déposée aux Etats-Unis et dans d’autrespays et licenciée exclusivement par X/Open Company, Ltd.
Sun, Sun Microsystems, le logo Sun, SunSoft, SunDocs, SunExpress, Solari, Ultra Enterprise, et OpenBoot PROMsont des marques de fabrique
ou des marques déposées, ou marquesde service, de Sun Microsystems,Inc. aux Etats-Unis et dans d’autres pays. Touteslesmarques SPARC
sont utilisées sous licence etsont des marques de fabriqueou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans
d’autrespays. Les produits portant les marquesSPARCsontbaséssurune architecture développée par Sun Microsystems,Inc.
L’interfaced’utilisationgraphiqueOPEN LOOK et Sun™ a étédéveloppée par Sun Microsystems, Inc.pour ses utilisateurs et licenciés. Sun
reconnaîtles efforts de pionniers de Xeroxpour la recherche et le développementdu concept des interfacesd’utilisation visuelle ou graphique
pour l’industrie de l’informatique. Sundétient une licence nonexclusive de Xerox sur l’interfaced’utilisation graphique Xerox, cette licence
couvrant également les licenciés de Sun qui mettent en placel’interface d’utilisation graphique OPEN LOOK et qui en outrese conforment aux
licences écrites de Sun.
CETTE PUBLICATION EST FOURNIE "EN L’ETAT" ET AUCUNE GARANTIE, EXPRESSE OU IMPLICITE, N’EST ACCORDEE, Y COMPRIS
DES GARANTIES CONCERNANT LA VALEUR MARCHANDE, L’APTITUDE DE LA PUBLICATION A REPONDRE A UNE UTILISATION
PARTICULIERE, OU LE FAIT QU’ELLE NE SOIT PAS CONTREFAISANTE DE PRODUIT DE TIERS. CE DENI DE GARANTIE NE
S’APPLIQUERAIT PAS, DANS LA MESURE OU IL SERAIT TENU JURIDIQUEMENT NUL ET NON AVENU.
Contents
Preface vii
1. Introduction 1-1
SSP Features 1-1
Enterprise 10000 System Architecture 1-3
SSP User Environment 1-4
SSP Window 1-4
SSP Console Window 1-5
Network Console Window 1-5
Hostview 1-6
Using a Spare SSP 1-6
Documentation 1-7
man Pages 1-8
2. Overview of the SSP Tools 2-1
Instances of Client Programs and Daemons 2-1
Only One Instance 2-2
One Instance per Platform 2-2
One Instance per Domain 2-3
Hostview 2-3
Contents i
Hostview Main Window 2-5
▼ To Select Items in the Main Window 2-7
Main Window Menu Bar 2-7
Help Window 2-10
Main Window Buttons 2-11
Main Window Processor Symbols 2-12
Hostview Performance Considerations 2-13
The netcon(1M) Window 2-13
▼ To Display a netcon(1M) Window Using netcon(1M) 2-13
▼ To Display a netcon(1M) Window Using netcontool(1M) 2-13
Overview of netcontool(1M) 2-15
Overview of netcon(1M) 2-18
netcon(1M) Communications 2-18
3. System Administration Procedures 3-1
SSP Log Files 3-1
▼ To View a Messages File From Within Hostview 3-1
Administering Power 3-3
▼ To Power Components On or Off From Within Hostview 3-3
▼ To Power Components On or Off From the Command Line 3-4
▼ To Power Peripherals On or Off From the Command Line 3-5
▼ To Monitor Power Levels in Hostview 3-6
Administering Thermal Conditions and Fans 3-8
▼ To Monitor Thermal Conditions From Within Hostview 3-8
▼ To Monitor Fans From Within Hostview 3-10
▼ To Control Fans From Within Hostview 3-12
Domains 3-14
Domain Configuration Requirements 3-14
ii Ultra Enterprise 10000 SSP 3.1 User’s Guide • December 1997
▼ To Create Domains From Within Hostview 3-15
▼ To Create Domains From the Command Line 3-16
▼ To Remove Domains From Within Hostview 3-17
▼ To Remove Domains From the Command Line 3-18
▼ To Rename Domains From Within Hostview 3-18
▼ To Rename Domains From the Command Line 3-19
▼ To Bring up a Domain From Within Hostview 3-20
▼ To Bring up a Domain From the Command Line 3-20
▼ To Obtain Domain Status From Within Hostview 3-21
▼ To Specify the Domain for an SSP Window 3-23
▼ To Create a netcon(1M) Window for a Domain 3-23
SSP Messages Files 3-23
Blacklisting Components 3-23
▼ To Blacklist Boards and Buses From Within Hostview 3-25
▼ To Blacklist Processors From Within Hostview 3-26
▼ To Clear the Blacklist File From Within Hostview 3-27
Dual Control Board Handling 3-27
Control Board Executive (cbe) 3-28
Booting 3-28
Primary Control Board 3-28
Control Board Server (cbs) 3-28
Connection 3-28
Control Board Executive Image and Port Specification Files 3-29
▼ To Switch the Primary Control Board 3-30
4. SSP Internals 4-1
Startup Flow 4-1
Enterprise 10000 Client/Server Architecture 4-4
Contents iii
POST 4-6
Daemons 4-7
Event Detector Daemon (edd(1M)) 4-8
Control Board Server (cbs(1M)) 4-10
File Access Daemon (fad(1M)) 4-11
Network Time Protocol Daemon (xntpd(1M)/ ntpd(1M)) 4-11
obp_helper(1M) Daemon 4-13
Environment Variables 4-14
Executable Files Within a Domain 4-14
*.elf File 4-15
download_helper File 4-15
obp File 4-15
Glossary A-1
Index Index-1
iv Ultra Enterprise 10000 SSP 3.1 User’s Guide • December 1997
Figures
FIGURE 1-1 Enterprise 10000 System and Control Boards 1-3
FIGURE 1-2 SSP Window 1-4
FIGURE 1-3 SSP Console Window 1-5
FIGURE 1-4 netcon(1M) Window 1-5
FIGURE 1-5 Hostview GUI Program 1-6
FIGURE 2-1 SSP clients and daemons: only one instance. 2-2
FIGURE 2-2 SSP clients and daemons: one instance per platform 2-2
FIGURE 2-3 SSP clients and daemons: one instance per domain. 2-3
FIGURE 2-4 Hostview Main Window 2-5
FIGURE 2-5 netcontool(1M) Main Window 2-15
FIGURE 2-6 netcontool(1M) Console Configuration Window 2-16
FIGURE 3-1 SSP Logs Window 3-2
FIGURE 3-2 Hostview — Power Control and Status Window 3-3
FIGURE 3-3 Hostview — Power Status Display 3-6
FIGURE 3-4 Hostview — System Board Power Detail Window 3-7
FIGURE 3-5 Hostview — Thermal Status Display 3-9
FIGURE 3-6 Hostview — System Board Thermal Detail 3-10
FIGURE 3-7 Hostview — Fan Status Display 3-11
FIGURE 3-8 Hostview — Fan Tray Display 3-12
Figures v
FIGURE 3-9 Hostview — Fan Control and Status Window 3-13
FIGURE 3-10 Hostview — Remove Domain 3-17
FIGURE 3-11 Hostview — Rename Domain Window 3-19
FIGURE 3-12 Hostview — Domain Status Window 3-22
FIGURE 4-1 Startup Flow 4-3
FIGURE 4-2 Enterprise 10000 Client/Server Architecture 4-5
FIGURE 4-3 Uploading Event Detection Scripts 4-9
FIGURE 4-4 Event Recognition and Delivery 4-9
FIGURE 4-5 Response Action 4-10
FIGURE 4-6 SSP / Enterprise 10000 Communication Through cbs(1M) 4-11
vi Ultra Enterprise 10000 SSP 3.1 User’s Guide • September 1997
Preface
The Ultra Enterprise 10000 SSP 3.1 User’s Guide describes the SSP (System Service
Processor), which enables you to monitor and control the Ultra Enterprise 10000
system.
How This Book Is Organized
This document contains the following chapters:
Chapter 1, “Introduction,” introduces the System Service Processor (SSP).
Chapter 2, “Overview of the SSP Tools,” introduces Hostview and the
netcontool(1M) command.
Chapter 3, “System Administration Procedures,” describes how to perform
common system administration procedures.
Chapter 4, “SSP Internals,” provides more detailed information for system
administrators interested in how the SSP works. Included are descriptions of the SSP
booting process and the edd(1M) daemon, which monitors the Ultra Enterprise
10000 system.
Preface vii
Before You Read This Book
This manual is intended for the Ultra Enterprise 10000 system administrator, who
should have a working knowledge of UNIX
the Solaris
should first read the Solaris User and System Administrator AnswerBooks provided
with this system, and consider UNIX system administration training.
TM
operating environment. If you do not have such knowledge, you
®
systems, particularly those based on
Using UNIX Commands
This document does not contain information on basic UNIX®commands and
procedures such as shutting down the system, booting the system, and configuring
devices.
See one or more of the following for this information:
■ AnswerBook™ online documentation for the Solaris™ 2.x software environment,
particularly those dealing with Solaris system administration.
■ Other software documentation that you received with your system
viii Ultra Enterprise 10000 SSP 3.1 User’s Guide • December 1997
Typographic Conventions
TABLEP-1 Typographic Conventions
Typeface or
Symbol Meaning Examples
AaBbCc123 The names of commands, files,
and directories; on-screen
computer output.
AaBbCc123
AaBbCc123 Book titles, new words or terms,
What you type, when
contrasted with on-screen
computer output.
words to be emphasized.
Command-line variable; replace
with a real name or value.
Edit your .login file.
Use ls -a to list all files.
% You have mail.
% su
Password:
Read Chapter 6 in the User’s Guide.
These are called class options.
You must be root to do this.
To delete a file, type rm filename.
Shell Prompts
TABLEP-2 Shell Prompts
Shell Prompt
C shell machine_name%
C shell superuser machine_name#
Bourne shell and Korn shell $
Bourne shell and Korn shell superuser #
ix
Related Documentation
TABLEP-3 Related Documentation
Application Title
Installation Ultra Enterprise 10000 System Hardware and Software Installation
and De-Installation Guide
Reference (man pages) Ultra Enterprise 10000 SSP 3.1 Reference Manual
Release Notes SMCC Open Issues Supplement Release Notes (Solaris 2.6), or SSP
3.1 Release Notes (Solaris 2.5.1). The Open Issues Supplement
contains the information in the section, “Ultra Enterprise
10000 Servers”.
Other Dynamic Reconfiguration User’s Guide
Dynamic Reconfiguration Reference Manual
Alternate Pathing User ’s Guide
Alternate Pathing Reference Manual
Inter-Domain Network User ’s Guide
Ordering Sun Documents
SunDocsSMis a distribution program for Sun Microsystems technical documentation.
Contact SunExpress for easy ordering and quick delivery. You can find a listing of
available Sun documentation on the World Wide Web.
TABLEP-4 SunExpress Contact Information
Country Telephone Fax
Belgium 02-720-09-09 02-725-88-50
Canada 1-800-873-7869 1-800-944-0661
France 0800-90-61-57 0800-90-61-58
Germany 01-30-81-61-91 01-30-81-61-92
Holland 06-022-34-45 06-022-34-46
Japan 0120-33-9096 0120-33-9097
Luxembourg 32-2-720-09-09 32-2-725-88-50
x Ultra Enterprise 10000 SSP 3.1 User’s Guide • December 1997
TABLEP-4 SunExpress Contact Information
Sweden 020-79-57-26 020-79-57-27
Switzerland 0800-55-19-26 0800-55-19-27
United Kingdom 0800-89-88-88 0800-89-88-87
United States 1-800-873-7869 1-800-944-0661
World Wide Web: http://www.sun.com/sunexpress/
Sun Documentation on the Web
The docs.sun.com web site enables you to access Sun technical documentation on
the World Wide Web. You can browse the docs.sun.com archive or search for a
specific book title or subject at http://docs.sun.com.
Sun Welcomes Your Comments
We are interested in improving our documentation and welcome your comments
and suggestions. You can email your comments to us at smcc-docs@sun.com.
Please include the part number of your document in the subject line of your email.
xi
xii Ultra Enterprise 10000 SSP 3.1 User’s Guide • December 1997
CHAPTER
1
Introduction
The System Service Processor (SSP) is a SPARC®workstation that enables you to
control and monitor the Ultra Enterprise 10000 system. The SSP software packages
must be installed on the SSP workstation. In addition, the SSP workstation must be
able to communicate with the Ultra Enterprise 10000 system over an Ethernet
connection. In this book, the SSP workstation is simply called the SSP.
The Ultra Enterprise 10000 system is often referred to as the platform. System boards
within the platform may be logically grouped together into separately bootable
systems called Dynamic System Domains, or simply domains . Up to eight domains
may exist simultaneously on a single platform. (Domains are introduced in this
chapter, and are described in more detail in “Domains” on page 3-14.) The SSP
enables you to control and monitor domains, as well as the platform itself.
Domains can communicate with each other at high speeds using the Inter-Domain
Networks (IDN) feature, which is only available with Solaris version 2.6 (and later)
on the Ultra Enterprise 10000. IDN exposes a normal network interface to the
domains that make up the network, but no cabling or other network hardware is
required. Instead, domains communicate using hardware features that are built into
the Ultra Enterprise 10000. IDN networks are described in the Inter-Domain Network
User’s Guide.
SSP Features
SSP 3.1 software can be loaded only on Sun workstations running Solaris 2.5.1 in an
OpenWindows
Solaris 2.6. However, the SSP does work well with Ultra Enterprise 10000 domains
running Solaris 2.5.1 or Solaris 2.6. The GUI programs that are provided with the
SSP 3.1 software can be used remotely, possibly on a workstation running the
Common Desktop Environment (CDE) rather than Open Look.
TM
or Open Look environment. The SSP software cannot be run on
1-1
The SSP enables the system administrator to perform the following tasks:
■ Boot domains.
■ Perform emergency shutdown in an orderly fashion. For example, the SSP
software automatically shuts down a domain if the temperature of a processor
within that domain rises above a pre-set level.
■ Dynamically reconfigure a domain so that currently installed system boards can
be logically attached to or detached from the operating system while the domain
continues running in multiuser mode. This feature is known as Dynamic
Reconfiguration and is described in the Dynamic Reconfiguration User ’s Guide.(A
system board can easily be physically swapped in and out when it is not attached
to a domain, even while the system continues running in multiuser mode.)
■ Create domains by logically grouping system boards together. Domains are able
to run their own operating system and handle their own workload. See
“Domains” on page 3-14.
■ Assign paths to different controllers for I/O devices, which enables the system to
continue running in the event of certain types of failures. This feature is known as
Alternate Pathing and is described in the Alternate Pathing User’s Guide.
■ Monitor and display the temperatures, currents, and voltage levels of one or more
system boards or domains.
■ Control fan operations.
■ Monitor and control power to the components within a platform.
■ Execute diagnostic programs such as POST (power-on self test).
In addition, the SSP environment:
■ Warns you of impending problems, such as high temperatures or malfunctioning
power supplies.
■ Notifies you when a software error or failure has occurred.
■ Automatically reboots a domain after a system software failure (such as a panic).
■ Keeps logs of interactions between the SSP environment and the domains.
1-2 Ultra Enterprise 10000 SSP 3.1 User’s Guide • December 1997
Enterprise 10000 System Architecture
The Enterprise 10000 platform, SSP, and other workstations communicate over
Ethernet as shown in
SSP
FIGURE 1-1.
Ethernet
Enterprise 10000
platform
CBE
CBE
WS
FIGURE 1-1 Enterprise 10000 System and Control Boards
Control
board 0
Control
board 1
Redundant control boards are supported within the Enterprise 10000 platform. Each
control board runs a Control Board Executive (CBE) that communicates with the SSP
over the network. One control board is designated as the primary control board, and
the other is designated as the alternate control board. If the primary control board
fails, you can manually switch to the alternate control board as described in “Dual
Control Board Handling” on page 3-27.
SSP operations can also be performed by remotely logging in to the SSP from
another workstation on the network. Whether you log in to the SSP remotely or
locally, you must log in as user ssp and provide the appropriate password if you
want to perform SSP operations (such as monitoring and controlling the platform).
Chapter 1 Introduction 1-3
SSP User Environment
You can interact with the SSP and domains by using the Hostview GUI or other
window environments.
SSP Window
An SSP Window provides a command line interface to the Solaris and SSP
environments.
SSP or Other Workstation Display
SSP window
% rlogin ssp \
-1 ssp
FIGURE 1-2 SSP Window
To display an SSP Window, you must log in as user ssp and enter the ssp user
password. You are then prompted for the name of a domain. The SUNW_HOSTNAME
environment variable is set to that domain. (You can change the value of
SUNW_HOSTNAME at any time.) The effect of SUNW_HOSTNAME on client applications
and daemons is described in “Instances of Client Programs and Daemons” on
page 2-1.
You can also display an SSP Window on any workstation on the network by using
rlogin(1) to remotely log in to the SSP machine as user ssp. The DISPLAY
environment variable must be set to your display, and your xhost(1) settings must
enable the SSP software to display on your workstation.
Multiple SSP Windows can be used simultaneously.
SSP
1-4 Ultra Enterprise 10000 SSP 3.1 User’s Guide • December 1997
SSP Console Window
The SSP Console Window is the console for the SSP machine.
SSP Display
SSP Console Window
% cmdtool —C
FIGURE 1-3 SSP Console Window
SSP
This window is normally created when OpenWindows starts but, if necessary, you
can display it using cmdtool(1) with its -C option. This window displays
messages from programs running in the SSP and its Solaris environment and kernel.
Network Console Window
A netcon(1M) window receives system console messages from a domain.
Logical Connection
Enterprise 10000
Domain 1
Domain 2
Chapter 1 Introduction 1-5
netcon (1M) Windows
% setenv SUNW_HOSTNAME domain1
% netcon
% setenv SUNW_HOSTNAME domain2
% netcon
FIGURE 1-4 netcon(1M) Window
Logical Connection
SSP
Network
Platform
Multiple netcon(1M) windows can be open simultaneously, but only one at a time
can have write privileges to a specific domain. When a netcon(1M) window is in
read-only mode, you can view messages from the netcon(1M) window, but you
cannot enter any commands. For more information, see the netcon(1M) man page.
Hostview
The Hostview program provides a graphical user interface (GUI) with the same
functionality as many of the SSP commands:
Logical Connection
Logical Connection
Hostview
SSP Window
% hostview
FIGURE 1-5 Hostview GUI Program
Hostview is introduced in Chapter 2, “Overview of the SSP Tools” and is described
in more detail in Chapter 3, “System Administration Procedures”. It is also described
in hostview(1M) in the Ultra Enterprise 10000 SSP Reference.
SSP
Network
Enterprise 10000
Platform
Domain 1
Domain 2
Using a Spare SSP
The SSP unit is a Sun workstation with a defined hardware configuration. Any
identical Sun workstation can also serve as an SSP. You can optionally designate
such a Sun workstation as a spare SSP unit, to serve as a backup if your primary SSP
unit fails. You can also order your Ultra Enterprise 10000 server with a spare SSP
unit. The spare SSP can be a dedicated spare SSP or a non-dedicated spare SSP.
A dedicated spare SSP is a unit that you maintain in a ready state; if the primary SSP
fails, you can quickly switch to the spare SSP. The dedicated spare SSP is not used
for any other purpose. A non-dedicated spare SSP is one that you do not necessarily
1-6 Ultra Enterprise 10000 SSP 3.1 User’s Guide • December 1997
maintain in a ready state, one that may require a re-install of the operating system
and SSP software before you can begin using it as the SSP, should the primary SSP
fail. However, you can use a non-dedicated SSP for other purposes in the meantime.
To maintain a spare SSP, you must adhere to the following requirements:
■ The hardware for the spare SSP must be identical to the hardware for the main
SSP. (A spare SSP purchased from Sun satisfies this requirement.)
■ The operating system and SSP software on the spare SSP must be identical to the
operating system and SSP software on the main SSP before you switch to the
spare SSP. If you are maintaining a dedicated spare SSP, you must install the same
operating system upgrades and patches on it as you do on the primary SSP.
■ If you are maintaining a dedicated spare SSP, you must not install or use any non-
SSP software on it.
■ The main SSP must be backed up regularly. You should perform weekly full
backups and daily incremental backups. After any system configuration
operation, you should immediately perform an incremental backup in case the
main SSP crashes prior to the next scheduled daily incremental backup. System
configuration operations include:
■ Changing the primary control board
■ Inserting or removing a board (using the Hot Swap procedure)
■ Attaching or detaching a board
■ Creating, removing, or renaming a domain
■ Performing a bringup(1M) operation on a domain
■ Rebooting a domain
■ Automatic domain recovery operations due to events such as system panics or
hardware failures
To switch over to the spare SSP, see the following sections in the Ultra Enterprise
10000 System Hardware and Software Installation and De-Installation Guide , a copy of
which is in both the SSP 3.1 Media Kit and the SMCC Server Media Kit:
■ Replacing the SSP With a Dedicated Spare SSP
■ Replacing the Main SSP With a Non-dedicated Spare SSP
Documentation
For general system administration information, such as adding users and mounting
file systems, refer to the Solaris 2.5 System Administrator AnswerBook. If you encounter
any information in these documents that conflicts with the Ultra Enterprise 10000
documents, the Ultra Enterprise 10000 documents take precedence, followed by
documents that describe Sun hardware, and then the Solaris documents.
Chapter 1 Introduction 1-7
man Pages
The man pages for functions that run on the SSP are initially located on the SSP in
/opt/SUNWssp/man. When running Solaris 2.5.1 on the Ultra Enterprise 10000, the
man pages for Network Time Protocol (NTP) are initially loaded on the SSP (and on
domains) within /opt/SUNWxntp/man. When running Solaris 2.6 on the Ultra
Enterprise 10000, the man pages for NTP are bundled with operating system. Unless
noted otherwise, all man pages referenced in this document are SSP man pages.
They are included in the Ultra Enterprise 10000 SSP Reference, and you can view them
in an SSP Window by using the man(1) command.
1-8 Ultra Enterprise 10000 SSP 3.1 User’s Guide • December 1997
CHAPTER
2
Overview of the SSP Tools
This chapter introduces:
■ Hostview —This is a graphical user interface (GUI) front-end to SSP commands.
■ netcontool(1M)—This is a GUI interface to the netcon(1M) command.
netcontool(1M) simplifies the process of configuring and bringing up
netcon(1M) Windows. You can also use the netcon(1M) command directly to
display a netcon(1M) Window. However, when using netcon(1M), you must
know escape sequences to perform operations that can be performed by clicking
on buttons under netcontool(1M).
Instances of Client Programs and Daemons
An Enterprise 10000 platform may host multiple domains, where each domain runs
its own copy of the operating system, independent of any other domains. The client
programs and daemons running on the SSP fall into three categories with respect to
how many instances are created relative to a platform and its domains:
■ Only one instance
■ One instance per platform
■ One instance per domain
2-1
Only One Instance
For certain clients and daemons, exactly one instance is created on the SSP, without
regard to the platform or the number of domains that exist on the platform. For
these clients and daemons, the setting of the environment variable SUNW_HOSTNAME
is irrelevant. See
FIGURE 2-1.
SSP
Only one
instance
SUNW_HOSTNAME
is not relevant.
FIGURE 2-1 SSP clients and daemons: only one instance.
Platform
Domain
Domain
One Instance per Platform
For some clients and daemons, one instance is started for the platform. In the current
release, where the SSP can control only a single platform, there is little difference
between this type of client or daemon and the type previously described. However,
when a client or daemon is specific to a platform, the setting of the SUNW_HOSTNAME
environment variable is important; SUNW_HOSTNAME must identify the platform.
This can be accomplished by setting SUNW_HOSTNAME to the name of the platform or
to the name of a domain on the platform. See
SSP
Instance
SUNW_HOSTNAME
must identify the
platform.
FIGURE 2-2.
Platform
Domain
Domain
FIGURE 2-2 SSP clients and daemons: one instance per platform
2-2 Ultra Enterprise 10000 SSP 3.1 User’s Guide • December 1997
One Instance per Domain
For certain other clients and daemons, one instance is created on the SSP for each
domain on the platform. Before you run a client application of this genre, set
SUNW_HOSTNAME to the relevant domain name. (hpost(1M) and bringup(1M) are
examples of this genre.) See
FIGURE 2-3.
SSP
Instance 1
Platform
Domain
Instance 2
SUNW_HOSTNAME
Domain
must be set to the
domain name.
FIGURE 2-3 SSP clients and daemons: one instance per domain.
Hostview
Hostview is a GUI program that enables you to perform the following actions:
■ Power a platform on and off.
■ Dynamically reconfigure the boards within a platform, logically attaching or
detaching them from the operating system. This feature is described in the
Dynamic Reconfiguration User’s Guide.
■ Dynamically group system boards into domains. Each domain runs its own
instance of Solaris and has its own log messages file.
■ Bring up domains.
■ Start an SSP Window for each domain.
■ Access the SSP log messages file for each platform or domain.
■ Remotely log in to each domain.
■ Edit the blacklist(4) file to enable or disable hardware components on a
domain.
■ Display a netcon(1M) Window.
If you want to run Hostview, you only need to run one instance for a given platform,
although it is possible to run more than one instance simultaneously (perhaps on
different SSPs) to work with the same platform. You can run Hostview from any SSP
Window (such as, a session where you have logged in as user ssp).
Chapter 2 Overview of the SSP Tools 2-3
If you have logged into the SSP environment from a workstation, make sure your
DISPLAY environment variable is set to your current display and that your xhost
settings enable the SSP to display on your workstation (see xhost(1) in the Solaris
X Window System Reference Manual).
● To start up Hostview, run the hostview(1M) command in an SSP Window:
ssp% hostview &
2-4 Ultra Enterprise 10000 SSP 3.1 User’s Guide • December 1997
Power
Temp.
Fans
Failure
Support
Board
Control
Board
System
Board
Selected
Board
Buses
Domain 1
Hostview Main Window
When you start up Hostview, the main window is displayed:
Domain 2
FIGURE 2-4 Hostview Main Window
The menu bar on the main window provides the commands that you can use to
control the platform. See “Main Window Menu Bar” on page 2-7.
The buttons on the main window (power, temperature, and so forth) bring up status
details. The buttons are introduced in “Main Window Buttons” on page 2-11.
Chapter 2 Overview of the SSP Tools 2-5
The rest of the main window provides a graphical view of the platform boards and
buses. The system boards are named SB0 through SB15, and their processor numbers
are shown. The control boards are named CB0 and CB1. The support boards are
named CSB0 and CSB1. The buses are named ABUS0 through ABUS3, and DBUS0
through DBUS3.
The system boards along the top of the display are arranged in the order they appear
on the front side of the physical platform. The system boards along the bottom of the
display are arranged in the order they appear on the back side of the physical
platform.
If a system board is shown with no outline, the board is not part of a domain and is
not currently selected. Here is an example:
If a system board is part of a domain, a colored outline surrounds it. The boards
within a given domain all have an outline of the same color. Here is an example:
A black outline (around the domain color outline) indicates that a board is selected.
Here is an example:
The processors within the boards are numbered 0 through 63. The processor symbols
(diamond, circle, and so forth) indicate the state of the processors, and are described
in “Main Window Processor Symbols” on page 2-12.
2-6 Ultra Enterprise 10000 SSP 3.1 User’s Guide • December 1997
▼ To Select Items in the Main Window
You can select one or more boards in the Hostview main window. You can also select
one domain in the main window. You must select a set of boards prior to performing
certain operations, such as creating a domain.
■ To select a single board, click it with the left mouse button. The selected board is
indicated by a black outline, and all other boards are deselected.
■ To select additional boards, click them with the middle mouse button. You can
also deselect a currently selected board by clicking on it with the middle mouse
button. (The middle mouse button toggles the selection status of the board
without affecting the selection status of any other board.)
■ To select a domain, click a board within that domain with the left mouse button.
Note that it is possible to select boards from different domains (using the middle
mouse button), but the selected domain will correspond to the board that you
selected with the left mouse button.
Main Window Menu Bar
The items on the main Hostview menu are described in the following table.
TABLE2-1 Hostview Menu Items
Menu Selection Description
File SSP Logs Displays a window that shows the SSP
messages for a domain or for the platform.
For more information, see “SSP Log Files”
on page 3-1.
Quit Terminates Hostview.
Edit Blacklist File Lets you specify boards and CPUs to be
blacklisted.
Control Power Displays a window that enables you to turn
the power on and off for the selected board.
See “To Power Components On or Off From
Within Hostview” on page 3-3. You can also
set the JTAG claim and margin/trip
settings.
Bringup Displays a window that lets you run
bringup(1M) on a domain. See “To Bring
up a Domain From Within Hostview” on
page 3-20
.
Chapter 2 Overview of the SSP Tools 2-7
Loading...