Fujitsu Siemens Computers SX series User Manual

1Preface

With the business servers in the SX series (abbreviated to: SX servers), Fujitsu Siemens
Computers is pursuing its strategy of opening up the BS2000/OSD operating system by
making available a modern hardware solution which is based on SPARC64
and represents a future-safe investment for the customer.

The OSD Extended Configuration (OSD/XC) software package includes a ported variant of
the BS2000/OSD basic configuration which offers high performance when run on the
SX servers' SPARC64 architecture. Further software packages included in the OSD/XC
package extend the functionality available in the basic configuration. Existing BS2000/OSD
applications in the /390 world offer full object compatibility, i.e. they require no modifications,
when run on the SPARC64 architecture of the SX servers.

The SX server hardware is based on the PRIMEPOWER server hardware. The business
servers in the SX series can be divided into two classes: on the one hand the partitionable
models, with facilities for using several separate runtime environments for BS2000/OSD
and Solaris

™ applications, and on the other hand the entry-level models without partitioning

which offer a cost-effective way of entering the SX server series.
The hardware of the partitionable models is designed so that existing hardware compo-

nents (CPU, main memory, controllers, disks, etc.) can be distributed across multiple parti­tions. This means that different, independent operating systems together with their available
applications can be run on separate partitions. These operating systems and applications
do not affect each other when they are running.

™ technology

With their high availability and scalability, and the capacity for the parallel operation of
several independent application environments, the partitionable SX server models provide
an optimum basis for enterprise and business applications and for server and storage
consolidation. At the same time they also open up the SX series to the varied application
environment of the Solaris

™ operating system.

The SX100 series models are the entry-level models of the SX series. These non-partitio-
nable models are designed exclusively for use with BS2000/OSD. The SX series entry-level
models with their high availability and favourable total-cost-of-ownership (TCO) form an
optimum basis for the BS2000/OSD entry-level both for proven enterprise applications and
for new enterprise and E-business solutions.

U41272-J-Z385-3-76 1

Preface

All SX series models have the latest processor technology and optional fibre channel
interface technology for fibreCAT disk systems with possible SAN integration. These
features ensure that SX series models are a future-safe investment.

Figure 1: Example of an SX server: SX150 Business Server

On the business servers in the SX series suitable redundancy facilities result from the
operation of several partitions. These facilities are explained in more detail in the manual
“SX Series Business Servers – Concepts and Functions” [1].

Moreover, almost all functional elements can optionally be designed and configured redun­dantly on an SX server (console interfaces, disks, power supply, peripherals, etc.).

Business servers in the SX series have the following partitions according to the operating
system being run:

● BS2000 partitions

The BS2000/OSD operating system is installed with the X2000 carrier system. X2000
is based on Solaris and essentially provides the runtime environment for BS2000/OSD.
As an alternative to the native operation of BS2000/OSD, depending on the model up
to 15 independent BS2000/OSD guest systems can be operated under VM2000.

● Solaris partitions

The Solaris operating system is installed.

Each partition can be set up either on the basis of the physical partitioning PPAR or on the
basis of the extended partitioning XPAR. You will find more details on this in the appendix
(page 385ff).

2 U41272-J-Z385-3-76

Preface

X2000 is based on the Solaris operating system and provides the following functions:

● HAL (Hardware Abstraction Layer)

HAL maps the hardware-software interfaces of the /390 mode to equivalent interfaces
of the SPARC64 mode.

● /390 firmware

The /390 firmware component extends the SPARC64 mode and enables existing
customer applications to run object-compatibly on the SX servers under OSD/XC. This
applies both for applications generated with ASSEMBH and also for programs which
were generated with the BS2000 compilers for high-level programming languages. As
of OSD/XC V2.0 and X2000 V3.0A05 the SX servers also support ESA data spaces in
customer applications. Objects which are available in the special RISC object format for
SR2000 must be recompiled. The commands supported by ASSEMBH are described
in the manual “Assembler Instructions (BS2000/OSD)”[16].

● Execution of the inputs/outputs and data communication

● Administration and operation of the SX server

Entry-level models in the SX series

The entry-level models in the SX series are non-partitionable and designed for use exclu­sively with the BS2000/OSD operating system. BS2000/OSD running on entry-level models
uses the functionality of the X2000 carrier system.

With these models, too, state-of-the-art processor technology, the efficient LTO tape device,
and optional fibre channel connection technology for FibreCAT and Symmetrix disk systems
and for CentricStor and ITC/SBU with SAN integration capability make these servers a
future-safe investment.

You will find more detailed information on the hardware of the different model series in the
appendix (page 385ff).

U41272-J-Z385-3-76 3

Documentation for the SX Series Business Servers Preface

1.1 Documentation for the SX Series Business Servers

Extensive documentation is available to help you in your work with SX servers. It can be
ordered in printed form as a documentation package.
Its exact composition can be found in the Release Notice for OSD/XC.

The following manuals have been published specifically for the SX server series:

● SX Series Business Servers

Concepts and Functions
User Guide

This manual provides an overview of the features and special characteristics of the
SX server. It also provides information concerning the OSD/XC-based extensions to
BS2000/OSD.

● Operating Manuals for the SX Servers

These manuals describe the particular SX server and its hardware components.
They also provide information on hardware operation.

● SX Series Business Servers

Operation and Administration

User Guide
This manual contains all the information necessary to operate an SX server. It includes

information on configuring the system together with a description of important functions
for its operation and administration.

4 U41272-J-Z385-3-76

Preface Documentation for the SX Series Business Servers

● OSD/XC

Performance Guidelines

User Guide
This manual focuses on the principles and measurements involved in evaluating the

performance of BS2000/OSD applications which run on SX servers. The performance­related characteristics of the SX server architecture are described together with the
underlying operating sequences. Extensive information on tuning the configuration and
the software make it possible to optimize the economic efficiency of OSD/XC operation.

SX Series
Concepts and
Functions

SX100
Betriebsanleitung

SX130
Betriebsanleitung

SX140
Betriebsanleitung

SX150
User Guide

Figure 2: Structure of the documentation for the SX Series Business Servers

SX Series
Operating and

OSD/XC
Performance
GuidelinesAdministration

The core literature for the SX Series Business Servers in the BS2000 environment
consists of:

● the manuals for the BS2000/OSD-BC V6.0 basic configuration

● the manuals for the shipped versions of OSD/XC software products

● the manuals for the current versions of system-related software products which can be

purchased separately

U41272-J-Z385-3-76 5

Documentation for the SX Series Business Servers Preface

The following manuals in the core literature have been extended or replaced for OSD/XC:

Manual Comment

BS2000/OSD-BC
Performance Handbook

BS2000/OSD-BC
System Exits

Replaced by:
OSD/XC Performance Guidelines

Only valid in connection with Special Release

i The “OSD/XC Migration Guide” will be discontinued. As of the edition of June 2005

migration to SX servers is described in the “BS2000/OSD-BC Migration Guide”[3].

Readme files

For information on any functional changes or extensions, please refer to the Readme file for
the BS2000/OSD-BC V6.0 basic configuration or the product-specific Readme files for the
various software products:

SYSRME.<product>.<version>.E

Examples

SYSRME.BS2CP.060.D (BS2000/OSD-BC V6.0)
SYSRME.PERCON.028.D (PERCON V2.8)

Please refer to the appropriate system administrator for the user ID under which the
required Readme file can be found. You can also obtain the path name of the Readme file
directly by entering the following IMON command:

/SHOW-INSTALLATION-PATH INSTALLATION-UNIT=<product>, LOGICAL-ID=SYSRME.E

You can view the Readme file with/SHOW-FILE or by opening it in an editor or print it at a
standard printer using the following command:

/PRINT-DOCUMENT $<userid>.SYSRME.<product>.<version>.E,

LINE-SPACING=*BY-EBCDIC-CONTROL

Additional literature, in particular for the PRIMEPOWER servers and the products in the
Solaris environment, is available to complement the SX server documentation.

6 U41272-J-Z385-3-76

Preface Target groups

1.2 Target groups

This manual is intended for privileged users (operators, system administrators) of the
SX series business servers. It is assumed that readers possess a thorough understanding
of the operating system and the hardware and have a basic knowledge of the graphical user
interface PRIMEPOWER ServerView.

1.3 Summary of contents

You will find general information on the operation of an SX server in the chapter “Operating

concept of the SX servers”. This information includes:

– Operating concept for SX servers with the System Management Console (SMC)
– Operating concept for SX server entry-level models
– Remote operation of each LAN PC
– Notes on security for SX servers with SMC
– Remote Service (Teleservice)
– Procedures for switching the server (with SMC) on/off
– Procedures for switching the server (entry-level models) on/off

The chapter “Functions of the Solaris-CDE interface” describes the X-window interface
CDE (Common Desktop Environment) for controlling the SMC (System Management
Console).

The chapter “Functions of the System Management Console” explains the hardware
operation of the server and administration of the partitions.

The chapter “Functions of the SX server entry-level models” describes the switching on/off
functions, the integrated console, an optional LAN console and the time cluster with
external time servers for the entry-level models in the SX series.

The chapter “Remote operation via PC” discusses the recommended hardware and
software configuration and gives instructions on the configuration and operation of the
recommended software.

The chapter “Operating BS2000 instances” describes the operation of the BS2000 console
and dialog, as well as the event mode.

The chapter “The X2000 user interface” provides an overview of the functions of the X2000
interface provided in PRIMEPOWER ServerView. For details on individual menus and
dialog boxes refer to the online help.

The chapter “Global X2000 functions” describes the configuration of the SX server in
PRIMEPOWER ServerView.

U41272-J-Z385-3-76 7

Summary of contents Preface

The chapter “Dynamic Reconfiguration” describes how Dynamic Reconfiguration can be
performed for BS2000 partitions and the requirements for this. This function is available on
SX servers as of the SX150 model series.

The chapter “Solaris: system administration” gives an overview of the system administration
in Solaris with reference to one or two examples.

The chapters “What if ...” and “X2000 messages” contain information on the detection and
removal of faults.

The appendix provides information on the hardware properties of the business servers in
the SX series and on the optional SKP-SR for BS2000 operation.

This is followed by a list of abbreviations and figures, the related publications and an index.

8 U41272-J-Z385-3-76

Preface Notational conventions

1.4 Notational conventions

The following fonts and symbols are used in this manual to indicate different types of infor­mation:

Font/Symbol Indicates Example

AaBbCc123 System outputs are written in this

typewriter font.

AaBbCc123 Commands entered by the user are

written in typewriter font bold

Italic text Program interface functions and

menus are written like this.

“ ” Manual, chapter and section titles

are enclosed by double inverted
commas. The names of positions,
keys, buttons and menus are also
enclosed in double inverted
commas.

[ ... ] Square brackets indicate a reference

to related publications. The full title
and details of the reference
document are given in the “Related
Publications” section.

Ê

The enter symbol indicates an action
that the operator must perform (e.g.
enter something on the keyboard).

RC2000%

# ls -l <Return>

Select the menu

Edit local parameters

See chapter 3, “Configuration of the
System Console“, in the “System

Console Software User’s Guide
(SCS)“[7].

see “Migration Guide“[3].

Ê Click the button VConfig.

Indicates warnings.

!

Indicates important information

i

U41272-J-Z385-3-76 9

about product operation.

Notational conventions Preface

10 U41272-J-Z385-3-76

2 Operating concept of the SX servers

SX servers (with the exception of entry-level models) are operated via the system
management console (SMC) as the central console for the hardware and for the BS2000
and – optionally – Solaris operating systems. The business servers of the SX series, with
the exception of the entry-level models, are therefore also referred to in the following as
“SX servers with SMC”.

A concept has been developed for uniform operation of the different operating systems. This
operation is described in the section “Operating concept for SX servers with SMC” on

page 12.

The entry-level models in the SX series are also operated centrally with the integrated
console or an optional LAN console. For operating the entry-level models see the section

“Remote operation via LAN-PC” on page 16.

Remote administration can be performed from PCs separate from the computer center.
These can be used to administer the server and to configure and operate the instances of
BS2000 (e.g. remote BS2000 console) and, optionally Solaris, on the basis of a uniform
concept.

U41272-J-Z385-3-76 11

Operating concept for SX servers with SMC Operating concept of the SX servers

2.1 Operating concept for SX servers with SMC

The figure below shows the operating concept of an SX server with SMC and a BS2000 and
Solaris partition, taking the example of an SX130 configuration:

System cabinet

Server

BS2000 partition

BS2000/OSD

(OSD/XC)

X2000

CCU

Modem

SX1xx

Switch

System Control LAN

Solaris partition

Solaris

SCF

Switch

User LAN

Router

Admin LAN

PC

System Management Console

(SMC)

Teleservice-

Gate V.24

Figure 3: Example of an operating concept for an SX server

Browser

SINIX-TE

(optional)

9750 Emulation

(optional)

Exceed

Up to and including SX140 the SMC for an SX server is based on a PRIMESTATION system
with Solaris 8. The SMC for an SX150 server is based on a PRIMEPOWER250 system with
Solaris 9. The user interface for all functions is the X-Window Common Desktop
Environment (CDE) interface. This is where the System Console Software (SCS) runs. This
is used to administer the hardware functions of the SX system, and in particular the
functions for starting up/shutting down the server and partitioning the system.

The DVD/CD-ROM drive of the SMC can be used across partitions. In this way, operating
systems and applications can be installed in every partition of the SX server.

12 U41272-J-Z385-3-76

Operating concept of the SX servers Operating concept for SX servers with SMC

System administration of X2000 functions (and optionally, Solaris functions) can be
performed from any client via the PRIMEPOWER ServerView graphical user interface. To
do this, you will need a Web browser which has Java support. The SMC server names and
the names of all the partitions present on the SX server must be entered in the DNS. The
PRIMEPOWER ServerView application Domain makes it possible to perform administration
tasks outside of the local system. This means that administrators can administer clusters of
systems as a single system. So it is not necessary to perform each action for every system
individually and helps avoid errors.

The Domain application can support multiple BS2000/OSD instances and Solaris partitions
in a single PRIMEPOWER ServerView session.

The BS2000 console and dialog can be operated in the dtterm terminal emulation mode of
the X-Window CDE interface. The X2000 applications KVP software and 9750 emulation
provide the necessary functionality.

The individual SMC functions are described in detail in chapter “Functions of the System

Management Console” on page 43ff.

U41272-J-Z385-3-76 13

SX server entry-level models (without SMC) Operating concept of the SX servers

2.2 Operating concept for SX server entry-level models
(without SMC)

PCI

SX100

BS2000

OSD/XC

LAN

DVD

BS2000 ZASLAN

DAT

hme0

SOLARIS / X2000

PC

BrowserX-Server

opt. 9750-Emu.SINIX-TE

Figure 4: Operating concept of an SX server without SMC

Integrated console

Teleservicegate V24

Modem

Customer LAN

An SX server entry-level model is operated as standard via the integrated console. The
operator interface for all functions is the X-Window interface CDE of the Solaris/X2000
carrier system. Here the interface provides functions for all the instances to be operated,
such as BS2000 console, BS2000 dialog, X2000 configuration and hardware adminis­tration.

Hardware components consist of a DVD/CD ROM drive for installing the operating system
and applications, and a DAT drive for backup purposes.

14 U41272-J-Z385-3-76

Operating concept of the SX servers SX server entry-level models (without SMC)

2.2.1 Operation with integrated console

The entry-level models are operated from an integrated console with screen, keyboard and
touchpad installed in a rack.

The console is a Solaris console device on which the messages of the Solaris and the
X2000 carrier system can be monitored when starting up the server (e.g. after switching
on). This therefore gives you access to the OpenBoot PROM.

The console also provides the user interface for all the required functions after starting up
the server. The individual functions are described in detail in the chapter “Functions of the

SX server entry-level models” on page 125.

2.2.2 Operation with a LAN console and remote console adapter

The figure below shows an operating concept for an entry-level model with a LAN console
and a remote console adapter:

PCI

SX100

LAN

DVD

BS2000 ZASLAN

Customer LAN

BS2000

OSD/XC

DAT

V24
tty a

hme0

SOLARIS / X2000

Integrated Console

(except operation)

RCA

LAN Console

PC

BrowserX-Server

opt. 9750-Emu.SINIX-TE

other SX100-/
PRIMEPOWER-/
RM servers

Teleservicegate V24

Modem

Figure 5: Example of an operating concept for an entry-level model

As an alternative to the integrated console on entry-level SX series servers, you can use a
LAN console together with a V24/Ethernet converter, the remote console adapter (RCA).

U41272-J-Z385-3-76 15

Remote operation via LAN-PC Operating concept of the SX servers

The LAN console is available for administering UNIX/Solaris midrange servers and
SX server entry-level models from Fujitsu Siemens Computers Gmbh. The LAN console
has the following features:

● It supports the installation, configuration, administration and diagnostics management

of one or more connected SX server entry-level models, RM servers and
PRIMEPOWER servers.

● The LAN console can be used to perform all the functions of a character-orientated

screen, including the OBP monitor and a reboot of the system.

● The selection and display of one or more consoles of SX, RM and PRIMEPOWER

servers are performed by the tool xscon.

● Support of PRIMEPOWER ServerView (Web-based system administration).

● The SX server entry-level models and RM and PRIMEPOWER servers can also be

booted remotely (via LAN).

● The Teleservice connection for all systems is available centrally on the LAN console.

2.3 Remote operation via LAN-PC

If remote operation of the SX server is required, it is possible to use PCs with a network
connection to the server's SMC.

If an X server is employed, then it is possible to make use of the SMC user interface. This
means that it is possible to access the System Console Software (SCS) using the same
interface as is available directly at the SMC.

Administration of the SX business server partitions using PRIMEPOWER ServerView is
possible either by calling PRIMEPOWER ServerView in the CDE user interface, via the
Start button, via an icon on the desktop, or directly in the PC's browser. The BS2000
console and dialog can be operated in the SMC dtterm windows.

Alternatively, SINIX-TE can be used as a 97801 emulation in order to provide support for
Fujitsu-Siemens emulation keyboards for BS2000 (this is not possible when establishing a
communication using the Secure Shell).

If an SKP-SR is present, then this can also be used to provide support for 97801 emulations
for BS2000 console and dialog access (this is only released on SX130 servers but cannot
be used for communication when the Secure Shell is employed).

For further information on hardware and software requirements as well as on configuration,
refer to chapter “Remote operation via PC” on page 133ff.

16 U41272-J-Z385-3-76

Operating concept of the SX servers Notes on security

2.4 Notes on security

With an SX business server you can connect multiple systems to each other to form an
operating cluster. Entry-level models in addition to the operating system BS2000/OSD now
have the carrier system X2000 available as an additional system. This means that for
administration and operating purposes you will require access to a number of different
logins. The access to these logins (and in particular to the root login) has security-related
implications. The sections below provide some notes on access control.

2.4.1 Passwords

The business servers in the SX series are shipped with standard passwords for access to
the X2000 carrier system, Solaris (in the case of Solaris partitions) and the SMC.

These passwords must be changed by the customer, particularly for the root logins

i

on the corresponding systems!
When assigning passwords, we recommend that you follow these general rules:
– Passwords must be changed at regular intervals.

– Passwords can contain characters, figures and special characters.
– Passwords must not be stored on the system or on the remote workstations.

2.4.2 Login access to root in the partitions

In the SX business server as it is supplied, root access to the partitions is possible only via
the console, either on the SMC (see section “Consoles of the partitions with RC2000” on

page 86) or, for entry-level models, on the local console.

In the system as supplied, a remote login to the root login via a network is therefore not
possible.

This is achieved by setting CONSOLE=/dev/console/ in the file /etc/default/login.

This entry must not be changed into a comment!

i

Generally speaking, it is not necessary to possess login access to the root login in order to
administer partition systems (of, for example, entry-level models) because PRIMEPOWER
ServerView is provided for this purpose. This is particularly true in the case of BS2000
systems.

U41272-J-Z385-3-76 17

Notes on security Operating concept of the SX servers

However, should it become necessary to work under the root login then it is advisable to set
up user-specific logins under which login can be performed. Only then should the user
acquire root permissions by means of the su command.

User-specific IDs can be set up in the Users application of PRIMEPOWER ServerView in
the Users tab by clicking on the Users button and selecting the Create function (for details
please see the section “Administration of PRIMEPOWER ServerView” on page 53).

The advantage of this procedure is that root requests are logged in the sulog file. This
ensures that there is a record of when which users have acquired root permissions.

2.4.3 FTP access to root

This is similar to login access. File transfer with root permissions also calls for certain
security-related considerations. For this reason, FTP access to root is not possible by
default. This is achieved by setting root in the file /etc/ftpusers.

This entry must not be changed into a comment!

i

It is better to start by performing the transfer under a user-specific login. As described
above, the files can then be copied to the target location by using the su command with the
appropriate authorizations to request the root permissions.

2.4.4 User roles for SX servers with SMC

Depending on the extent to which it is necessary to separate Solaris and BS2000 adminis­tration and operation, there are a number of different ways of performing these tasks.
A number of related scenarios are presented below:

● Joint administration of the server, the configuration and operation by system adminis-

tration
In the simplest case all the server administration tasks are performed by a restricted

user group. In this case, all the members of this user group are able to access the SMC
from where they perform all the necessary tasks.

The SMC is not accessed via the root login but under one or more server administrator
logins belonging to the cladmin group (see section “User groups and logins” on

page 44).

18 U41272-J-Z385-3-76

Operating concept of the SX servers Notes on security

● Separate server administration and partition administration

Each partition on the SX server can have its own partition administrator. The partition
administrator possesses the rights necessary to switch the partition on and off and
access the partition's hardware console.

For information on setting up a login for a partition administrator, refer to section “User

groups and logins” on page 44. This login is a member of the clmon group and a partition

administrator group that you will need to create.

● Administration of operating systems in partitions without partition administration rights

If necessary for the purposes of operating system administration and operation, it is
possible to create logins which do not possess any extended rights for the adminis­tration of the server or the partitions. These logins should be members of the clmon
group in order to ensure that the SCS read access functions are available at the
partition's hardware console. For more information, see section “User groups and

logins” on page 44.

The following logins have already been created as supplied to manage the server

i

on the SMC:

– A server administrator login sxadmin

– A partition administrator login bs2admin for the BS2000 partition

– A partition administrator login soladmin for any Solaris partitions present

It is recommended that you use these logins to administer the server.

2.4.5 Security when accessing BS2000 operation functions

The following protective mechanisms can be set up when configuring BS2000 console
access:

BS2000 operation is performed via a login in X2000 for which a separate password is
required. This password must be subject to the usual password maintenance rules. The
logins from cons0 to cons7 are provided as default for this purpose. The administrator
defines any additional logins via PRIMEPOWER ServerView.

Running operator terminals (BS2000 consoles) can be secured via the main KVP function
menu (see the section “The Main KVP Function Menu” on page 164) by locking the inputs
on the BS2000 system. To reset this lock, it is necessary to enter the password. This does
not affect message output.

U41272-J-Z385-3-76 19

Notes on security Operating concept of the SX servers

To connect additional operator terminals via LAN, it is always necessary to enter a
password.

All the inputs and outputs can be recorded in a logging file and then archived. In the case
of high security requirements, the option for both logging and archiving should be set to
FORCED. These settings are made in the Bs2Devices application of PRIMEPOWER
ServerView by clicking on the BS2-KVP tab, selecting the first entry for a KVP name,
clicking with the right mouse button, and selecting the function “Show or modify logging
options”.

Activating these options also has the effect of recording all inputs and outputs in the

i

logging file. This results in an increase in the size of the logging file. You should

therefore check the size of the logging files and free space in the file system at

regular intervals.

2.4.6 Secure access with Secure Shell (open SSH)

Where tight security for the remote operation of SX series business servers is specified,
Secure Shell (SSH) is an ideal solution for secure remote logins, executing commands, and
file transfers for administration purposes.

The most commonly used and most widespread application of Secure Shell is the secure
remote administration of servers in business networks. The Secure Shell protocol is used
worldwide on innumerable systems and Secure Shell technology has been developed as a
de facto standard in the area of application connection.

Secure Shell is an application which protects TCP/IP connections between two computers.
The connection is coded on the application layer, which means that the security provided
by Secure Shell is independent of the type or speed of the network connection.

In the business servers in the SX series Secure Shell is used for the connection between
the administration PC and the system management console (or the server directly in the
case of the entry-level models) and also the partitions.

The product OpenSSH is used on the BS2000 partitions, the Solaris partitions with a
Solaris version up to and including V8, and the SMC of the partionable servers up to and
including SX140. The Secure Shell Software from Sun which is integrated into Solaris from
V9 on is used on Solaris partitions with a Solaris version as of V9, and the SMC as of the
SX150 model series. Both products support both Version 1 and Version 2 of the SSH
protocol.

20 U41272-J-Z385-3-76

Operating concept of the SX servers Notes on security

If the SSH is to be used on the BS2000 partition (i.e. the product OpenSSH is installed), the
rlogin, rsh, rcp, ftp and telnet services offered on the LAN are deactivated automatically and
they are replaced by the equivalent SSH interfaces ssh, scp and sftp. In this case the host­and ID-specific SSH configuration files (both in the partitions and on the SMC) are included
in the system data backup; X2000 itself then uses a secure transfer mechanism based on
DomainAdmin of the PRIMEPOWER ServerView Suite for communication between the
partitions and the SMC.

The following features of Secure Shell are used:

● Powerful authentication mechanisms

With the asymmetrical process for private/public keys at host and user level SSH incor­porates powerful authentication mechanisms. Here the private keys can be protected
by pass phrases. Integration into other authentication procedures such as Kerberos,
SecurID, PGP, TIS Gauntlet and PAM is also possible.

● Strong encryption

Open SSH uses, among other things, 3DES and Blowfish as the encryption algorithms.
Both are unpatented. Here SSH Version 2 offers considerably more and more powerful
encryption algorithms than Version 1. Encryption commences before authentication.
No passwords, private keys, commands or user data are transmitted in plain text.

● X11 Forwarding

X11 forwarding enables X-Windows network traffic to be coded in such a way that no
one is able to read the data traffic simultaneously or slip in malicious commands. The
data traffic for administration of the SX servers as part of the operating concept is
therefore protected.

● Port Forwarding

Port forwarding enables TCP/IP connections to be forwarded to a remote machine via
a coded protocol. Applications can therefore be made more secure.

U41272-J-Z385-3-76 21

Remote service (Teleservice) Operating concept of the SX servers

Components of the SSH

The SSH suite comprises the client program ssh which replaces rlogin, rsh and telnet,
Secure Copy scp which replaces rcp, and the Secure File Transfer Programm sftp which
replaces ftp. The client program ssh is used to set up a connection to a remote system
and to execute commands on a remote system.

The SSH suite also includes some administrative components such as the SSH daemon
sshd on the server side, the ssh-keygen function for generating, administering, and
converting authentication keys for SSH, and the ssh-agent and ssh-add functions for
controlling the SSH authentication agent.

Specifications for these functions are available on the Internet (e.g. at the URL

http://www.openbsd.org/cgi-bin/man.cgi). The use of keys and of the authenti-

cation agent is described in detail in the section “Key management for Secure Shell” on

page 153.

For details on installation and configuration and the application and use of Secure Shell see
the section “Access with Secure Shell” on page 144.

2.5 Remote service (Teleservice)

Teleservice gives you rapid access to the service staff and the service staff rapid, targeted
access to your system if this should be required.

Depending on the SX server specification, the Teleservice connection for all partitions is
centrally located on the SMC or, in the case of entry-level models, directly on the SX server
itself. This means that only one connecting line to the service center is required.

The Teleservice settings should only be made by a service engineer. The following

i

The following are provided for Teleservice purposes:

● An ISDN modem including the necessary cable connections

● A power connection (230V)

● The Teleservice software

● The file transfer software

sections are therefore for information only.

● Teleservice Call Management and Remote Service 2000 for the BS2000 Teleservice

connection which is supplied together with X2000

22 U41272-J-Z385-3-76

Operating concept of the SX servers Operating sequences on server switch-on / switch-off

● An ISDN telephone connection is also required in the vicinity of the system.

If no ISDN connection can be provided then an analog modem must be ordered

i

Teleservice Call Management is a central instance in X2000 which makes it possible to
automatically report error messages from the Solaris/X2000/BS2000 area of a partition to
the Teleservice center.

The error messages are assembled in logs by Logging V3.0 and are then categorized by
message type and passed to Teleservice Call Management in the form of Teleservice calls.
This processes the messages before routing them on to Remote Service 2000 (rs2k). The
Remote Service 2000 transfers the messages to the Teleservice center.

Logging V3.0 has a user interface that can be called via the PRIMEPOWER ServerView
(System - Diagnostics button). By default, all the settings are configured in such a way that
the corresponding error messages can be selected and forwarded as Teleservice calls.

separately.

Teleservice Call Management does not possess its own user interface since no configu­ration measures are required from the user here. Any Teleservice Call Management error
messages are stored in Logging V3.0 with the ID SMAWLtsca in the module name.

Remote Service 2000 has a user interface which is not dependent on PRIMEPOWER
ServerView and which can be used to configure the settings for the transfer of Teleservice
calls.

For further information on Teleservice in Solaris, refer to the manuals “Teleservice
(Unix)” [31], “LAN Console or System Management Console (SMC)” [9] and “Solaris

System Diagnostics” [28].

2.6 Overview of operating sequences on server switch-on /
switch-off

This section gives an overview of the actions and operating sequences involved in switching
the SX server on and off.

The commands and actions refer to the operation of a variety of functions. These are
explained in detail in the individual chapters and here are simply listed in summary form as
a comprehension aid.

U41272-J-Z385-3-76 23

Operating sequences on server switch-on / switch-off Operating concept of the SX servers

2.6.1 SX server with SMC

2.6.1.1 Switch-on of the SX server and automatic start-up of the operating systems

SMC
ready

System unit
ready

Solaris
ready

● Power on the server

(described in the SX1xx Operating Manual [2])

● Start up the System Management Console (SMC)

(described in the SX1xx Operating Manual [2])
This automatically starts Solaris at the SMC as well as the System

Console Software.

● Log in as server administrator sxadmin at the SMC (described in

section “User roles for SX servers with SMC” on page 18 and in
section “User groups and logins” on page 44).

Open the Machine Administration Menu and start up the server
(described in section “Machine Administration Menu” on page 58.

This powers up the system unit. After the POST (Power On Self
Test), the Solaris operating system and, in BS2000 partitions, X2000
are started automatically.

For automatic start-up to be possible, the mode selection switch at
the control panel must be set to LOCK (see SX1xx Operating
Manual [2])

X2000
ready

The start-up of the X2000 and Solaris systems can be monitored at
the RC2000 consoles (for more information, see section “Consoles

of the partitions with RC2000” on page 86).

BS2000
System ready

● When X2000 is started, BS2000 OSD/XC is also started

automatically provided that this operation has been enabled by
setting automatic IPL. This setting is recommended for automated
operation (for more information, see page 215 and the online help
system for BS2Devices in PRIMEPOWER ServerView).

BS2000 start-up can be monitored at the BS2000 console. For
information on calling a console window, see section “BS2000

console mode” on page 159.

Once the BS2000 system has reached Dialog-System-Ready,
dialog access is possible (for more information, see section

“EM9750 mode” on page 182).

Figure 6: Operating sequences when switching the SX server on/off

24 U41272-J-Z385-3-76

Operating concept of the SX servers Operating sequences on server switch-on / switch-off

2.6.1.2 Automatic termination of operating systems and server switch-off

An SX server with SMC is switched off in the same way it is switched on, i.e. via the SCS
Machine Administration Menu on the SMC. When the server is switched off, the Solaris
systems in the Solaris partitions are terminated automatically, BS2000 in the BS2000 parti­tions is terminated with a shutdown command and then, finally, X2000 is terminated (see
also “Definition of the BS2000 shutdown command” on page 216 and the corresponding
PRIMEPOWER ServerView online help).

In cases where application dependencies have to be taken into account, it is advisable to
terminate the individual operating systems one-by-one in order to be able to monitor the
progress of these actions.

Solaris systems are set to Run-Level 5, i.e. Power Off. This means that the corresponding
partition is already terminated.

In BS2000 partitions, the BS2000 shutdown occurs first. Following this, the partition must
then be switched off via the Machine Administration Menu at the system console (see
section “Switching partitions off” on page 65). This automatically terminates the X2000
system.

When the last partition on the server is switched off, the entire server itself is also
automatically terminated.

The system console (SMC) should always be left running to permit the continued (remote
if necessary) administration of the server. This is particularly important if a schedule for
automatic switch-on/switch-off via APCS has been activated (for more information, see

section “Switching the server on/off on a scheduled basis” on page 66).

U41272-J-Z385-3-76 25

Operating sequences on server switch-on / switch-off Operating concept of the SX servers

2.6.2 SX server entry-level models

2.6.2.1 Switch-on of entry-level model and automatic start-up of BS2000/OSD

Power on of
system unit

System unit
ready

X2000
ready

BS2000
System ready

● Power on the system unit

(see SX100 operating instructions [2])

● This starts up the system unit. After the POST (Power On Self Test),

X2000 is started automatically.
For automatic start-up to be possible, the mode selection switch on

the control panel must be set to the LOCK (see SX100 Operating
Manual [2]).

The start-up of the X2000 system can be monitored on the local
console (see SX100 Operating Manual [2]).

● When X2000 is started, BS2000/OSD is also started automatically

provided that this operation has been enabled by setting automatic
IPL. This setting is recommended for automated operation (for
details see page 215 and the online help of the application
BS2Devices in PRIMEPOWER ServerView).

● The start-up of the BS2000 can be monitored on the BS2000 con-

sole. Calling a console window is described in the section “BS2000

console mode” on page 159.

Once the BS2000 system has reached Dialog-System-Ready,
dialog access is possible (for this see section “EM9750 mode” on

page 182).

Figure 7: Operating sequences when switching SX server without SMC on/off

2.6.2.2 Automatic termination of BS2000/OSD and server switch-off

An SX server without SMC is switched off in the same way it is switched on, i.e. using the
switch on the system unit (see SX100 Operating Manual [2]). When the server is switched
off, BS2000/OSD is terminated automatically for each shutdown, then X2000 is terminated.
The server is then switched off.

However, when consideration has to be given to dependent applications, it is advisable to
terminate the operating system BS2000/OSD specifically to monitor the progress of these
actions.

26 U41272-J-Z385-3-76

3 Functions of the Solaris-CDE interface

The business servers in the SX series are operated from the console of the server with the
Solaris user interface. This user interface is called Common Desktop Environment – abbre­viated to CDE. Here, the interface provides not only functions for operating Solaris (or the
X2000 carrier system) but is also used for operating BS2000 instances. Details on
operation are given in the following section.

Here the console of the corresponding SX server can be either the system management
console (SMC) or, in the case of the SX series entry-level models, the local console of the
server or a LAN console. Since the commands for calling the functions are different for the
SMC/LAN console and local console, they are listed separately in the following sections.

In addition to the consoles, the CDE interface can also be operated remotely from
administration PCs (see chapter “Remote operation via PC” on page 133).

U41272-J-Z385-3-76 27

CDE interface Functions of the Solaris-CDE interface

3.1 CDE interface

Login screen

When the system console has been switched on, the following login screen appears (this
example is for the SMC):

Figure 8: CDE login screen (user name)

Ê Enter your user name in the text box (e.g. sxadmin; see the following section). Then click

the OK button.

A new window appears in which to enter your password:

Figure 9: CDE login screen (password)

Ê Enter your password in the text box. Then click the OK button.

28 U41272-J-Z385-3-76

Functions of the Solaris-CDE interface CDE interface

If this is the first time you have logged in, the following windows appear on the system
console (this example is for the SMC):

Application Manager

CDE control panel

SCS button

File manager with home directory

Figure 10: CDE window after the first login on a SMC

The next time you log in, the interface will appear in the form it was when you terminated
the CDE.

U41272-J-Z385-3-76 29

CDE interface Functions of the Solaris-CDE interface

The Application Manager of the System Console Software (SCS) from which the functions
can be activated looks like this:

Figure 11: Application Manager of the System Console Software (SCS)

A double-click calls up the functions.

30 U41272-J-Z385-3-76

Functions of the Solaris-CDE interface System administration of BS2000 and Solaris (optional)

3.2 System administration of BS2000 and Solaris (optional)

In the case of SX servers (not entry-level models) you must access the partitions in order
to be able to administer the operating systems in the individual partitions. This is provided
on the one hand by the consoles of the partitions supplied on the system management
console (SMC) of RC2000, and on the other by the network access of the SMC via the
administration LAN of the server.

In the case of the entry-level models, you access the partitions from the local console on
which you logged on directly to the system.

The administration of BS2000 systems requires access to the BS2000 console and a
BS2000 dialog access. Here access is provided via preconfigured X2000 user IDs in the
system.

For the sake of simplicity and increased operating security, the CDE user interface is
configured so that it is possible to call the individual instances at a mouse click.

This has already been done in the factory for the predefined user IDs sxadmin (server
administration of all the SX servers), bs2admin (BS2000 administration; not for the entry­level models) and soladmin (Solaris administration; only if a Solaris partition is available).

In the case of the SX servers, except for the entry-level model, icons are set up on the SMC,
under these user IDs, for access to the Solaris partitions (only in the case of the identifi­cation sxadmin), for the BS2000 console, for the BS2000 dialog and for PRIMEPOWER
ServerView of the BS2000 partition. The functions for hardware administration are provided
by the system console software on the SMC (see chapter “Functions of the System

Management Console” on page 43).

In the case of the entry-level models, icons are set, under the user ID sxadmin, for access
to the BS2000 console, to the BS2000 dialog, to PRIMEPOWER ServerView and to the
hardware administration with the machine administration menu.

In the next section a description is given of how these CDE actions (e.g. for further user­specific IDs) can be set up or modified.

U41272-J-Z385-3-76 31

Preconfiguring terminals Functions of the Solaris-CDE interface

3.3 Preconfiguring terminals

The preconfiguration for accessing the individual functions is based on the creation of an
“action” in the CDE interface of the Solaris system on the SMC or on the X2000 carrier
system. An icon is assigned to a command sequence. The configured commands can be
called up via this icon simply and without a risk of operator error.

The icons can be stored in various places, for example, directly on the CDE desktop or on
the control panel of the CDE interface.

The basic procedures for creating this “action” and storing the relevant icon are described
first in an example for accessing a BS2000 console. Then a description of the commands
used to access the individual instances (Solaris shell, BS2000 console, etc.) is provided.

The CDE desktop provides the function Create Action for creating actions. This tool can be
called up either via the Application Manager in the subfolder Desktop_Apps or directly via the
context menu of the desktop (right-click on the desktop background: Workspace Menu ->
Tool s -> Create Action).

This opens the processing window “Create Action”:

Figure 12: “Create Action” window

32 U41272-J-Z385-3-76

Functions of the Solaris-CDE interface Preconfiguring terminals

Three entries are important when creating an action:
– The name of the action (subtitle of the icon)

– The icon
– The command which is triggered when the icon is activated (with a double-click)

These three entries must be entered in that order in the fields of the window Create Action.
Enter the name of the icon in the first input line Action Name (Icon Label). Use a name which

will enable you to clearly identify the action, for example, “BS2000 Console”, “BS2000
Dialog” or “Solaris Shell – Server sx150part2”.

Select the appropriate icon from the section Action Icons. Click on Find Set… . This opens a
new window for selection:

Figure 13: Window for selecting an icon

All the icons available on the SMC are in the directory /usr/dt/appconfig/icons/C.
Select this line with a double-click. A selection list of all available icons then appears in the

right-hand side of the window.
For this example of accessing a BS2000 console, select the icon Dtterm, since terminal

emulation is to be started on the SMC with this action.

U41272-J-Z385-3-76 33

Preconfiguring terminals Functions of the Solaris-CDE interface

Confirm your selection with OK.
After returning to the main window, enter the actual command. Do this in the line Command

when Action is Opened (Double-clicked).
Example

Figure 14: Example for a command in the “Create Action” window

In the example for a BS2000 console, the command consists of calling up the terminal
emulation dtterm with parameters for the character set, the window title, the color settings
for the console and a command which is executed in the generated window. These
commands and parameters are explained in detail in the following sections.

When the command has been entered, the generated action must be saved. To do this, call
Save from the File> menu. The action is then saved in the home directory of the current login.
This is confirmed with an appropriate message.

Finally, the action which has just been created is integrated into the CDE interface.
The following options are available for this:

● Store the action directly on the desktop

After the file manager has been opened with the home directory, you can drag and drop
the action which is there to copy it directly onto the desktop.

34 U41272-J-Z385-3-76

Functions of the Solaris-CDE interface Preconfiguring terminals

● Integrate the action into the CDE control panel

First create a new button in the CDE control panel to do this. Right-click on the position
at which the button is to be added. Select Add Icon from the context menu which is
displayed. An empty button is then created.

The button is assigned the action dragged onto it from the opened file manager with the
home directory.

If the button which has just been created is to be extended to include a menu (like most
other buttons on the CDE control panel), right-click on it to call the context menu again
and select Add Subpanel. A submenu is then displayed at the top of the checkbox with
the available action and an empty menu item (labeled "Install Icon"). Fill this empty
menu item by dragging and dropping the relevant action.

3.3.1 Parameters for configuring an action for a dtterm terminal emulation

The following actions for Solaris shell (not on entry-level models), BS2000 console and
BS2000 dialog are based on a dtterm terminal emulation call. This makes a window
available for actual access via further commands. Configuring a dtterm window is a very
flexible process and we will therefore first explain some of the possible parameters
concerned.

The terminal emulation is always called up by the command dtterm. If the path variable
has not been set correctly, it may be necessary to specify the absolute path
/usr/dt/bin/dtterm.

Parameters can be specified additively:

● Assign a window title with -title "<title text>", e.g. -title "Solaris Shell

- Server SX150ABC" or -title "BS2000 Console".

● Select a character set with -fn <font name>, e.g. -fn 9x15.

All fonts which are installed can be determined with the command xlsfonts.

● Specify the terminal type with –tn <terminal type>, e.g. –tn bs2console.

Not only the previous color scheme, with output of the messages in a yellow color, but
also a color scheme adapted to the CDE, can be used when calling the console distri­bution program KVP for the BS2000 console. Here normal messages and inputs are
output in the foreground color (black), emergency messages and questions are output
as before in red, and KVP messages are underlined.
The terminal type bs2console must be set for using these color schemes.

U41272-J-Z385-3-76 35

Preconfiguring terminals Functions of the Solaris-CDE interface

● Select a background color with -bg <Name_of_background_color>,

e.g. -bg grey65.

● This is particularly important with the BS2000 console if the terminal type bs2console

is not set, since the called BS2000 KVP program outputs the messages in yellow.
All colors that can be selected are listed in the file /usr/openwin/lib/X11/rgb.txt.
When selecting a color, ensure that all outputs remain legible.
The following colors are recommended for the BS2000 console, in addition to various

grays (grey65...70, DarkGrey): tan2, burlywood3, DarkKhaki, CadetBlue, PeachPuff3,
NavajoWhite3, SteelBlue2.

The general standard recommendation is the terminal type bs2console without

i

any special background color being specified.

3.3.2 Solaris shell (not on entry-level models)

To create a Solaris shell access to a partition, the following command must be entered when
creating the action if the Secure Shell is not used:

dtterm -e telnet <server name of the Solaris partition>

If the Secure Shell is used, the following command must be entered when creating the
action:

dtterm -e ssh <server name of the Solaris partition>

The call of the terminal emulation dtterm can be extended as described above to include
parameters for assigning a title text and selecting a character set or a background color.

Example without using the Secure Shell

dtterm -fn 9x15 -bg white -title "Solaris Shell - Server SX-ABC"

-e telnet sx-abc.

Example using the Secure Shell

dtterm -fn 9x15 -bg white -title "Solaris Shell - Server SX-ABC"

-e ssh sx-abc.

36 U41272-J-Z385-3-76

Functions of the Solaris-CDE interface Preconfiguring terminals

3.3.3 BS2000 console

The ID cons0 mentioned in this section represents a predefined KVP ID. Here the

i

SX servers without entry-level models

To create BS2000 console access to a partition, the following command must be entered
when creating the action if the Secure Shell is not used:

dtterm -tn bs2console -e rlogin <server name of BS2000 partition> -l cons0

If the Secure Shell is used, the following command must be entered when creating the
action:

dtterm -tn bs2console -e ssh <server name of BS2000 partition> -l cons0

relevant KVP ID must be entered, according to the desired IPL console mnemonics
(for this see page 164).

The call to the terminal emulation dtterm can be extended as described above to include
parameters for assigning a title text and selecting a character set or a background color.

Example without using the Secure Shell

dtterm -fn 9x15 -tn bs2console -title "BS2000 console SX-BS2"

-e rlogin sx-bs2 -l cons0

Example using the Secure Shell

dtterm -fn 9x15 -tn bs2console -title "BS2000 console SX-BS2"

-e ssh sx-bs2 -l cons0

SX server entry-level models with the local console

To create a BS2000 dialog access to a partition, the following command must be entered
when creating the action:

dtterm –fn <font> –title "BS2000 console - <servername>" –tn bs2console -e sh
–c "exec login cons0"

Example

dtterm -fn 9x15 -title "BS2000 console – SX100" -tn bs2console -e sh –c
"exec login cons0"

U41272-J-Z385-3-76 37

Preconfiguring terminals Functions of the Solaris-CDE interface

3.3.4 BS2000 dialog

SX servers without entry-level models

To create BS2000 dialog access to a partition, the following command must be entered
when creating the action if the Secure Shell is not used:

dtterm -e rlogin <server name of the BS2000 partition> -l em9750

If the Secure Shell is used, the following command must be entered when creating the
action:

dtterm -e ssh <server name of the BS2000 partition> -l em9750

The call to the terminal emulation dtterm can be extended as described above to include
parameters for assigning a title text and selecting a character set.

Example without using the Secure Shell

dtterm -fn 9x15 -title "BS2000 dialog" -e rlogin sx-bs2 -l em9750

Example using the Secure Shell

dtterm -fn 9x15 -title "BS2000 dialog" -e ssh sx-bs2 -l em9750

Details of setting up console accesses to the guest systems of a VM2000 system are
provided in the section "Operating the guest systems using operator terminals" in the
"VM2000 (BS2000/OSD)"[14] manual.

SX server entry-level models with local console

To create BS2000 dialog access to a partition, the following command must be entered
when creating the action:

dtterm -e sh –c "exec login em9750"

Example

dtterm -fn 9x15 -title "BS2000 dialog – SX100" -e sh –c "exec login
em9750"

38 U41272-J-Z385-3-76

Functions of the Solaris-CDE interface Preconfiguring terminals

3.3.5 PRIMEPOWER ServerView (BS2000 system)

SX server (not entry-level models)

A CDE action can also be created to call PRIMEPOWER ServerView as an application. The
call should be made in the System Management Console.

When creating the action, select the icon “WSA” instead of the icon “Dtterm”.
The command to be entered should then be:

/opt/SMAW/bin/wsa `uname -n`

The command locally calls the PRIMEPOWER ServerView-application of the SMC.

SX server entry-level models with local console

To call PRIMEPOWER ServerView as an application in an entry server, you must call the
PRIMEPOWER ServerView program directly. Here the call is performed in the X2000
carrier system.

The following command must be entered in the CDE action:

/opt/SMAW/bin/wsa ’uname –n’

3.3.6 Machine Administration Menu (for entry-level models only)

In this case the functions for hardware administration, unlike those for SX servers with SMC,
are not integrated directly in the CDE interface. To call the machine administration menu
(see section “Displaying the configuration” on page 81) a further CDE action must therefore
be created for the entry-level models in the SX series. The machine administration menu
requires root rights, which is why the ID madmin is created with corresponding assignment
of rights. The ID madmin allows direct access to the relevant function.

The following command must be entered in the CDE action:

dtterm -e sh –c "exec login madmin"

In this case the calling of the terminal emulation can be supplemented as mentioned above
by parameters for assigning a title text and for selecting a character set.

Example

dtterm -fn 9x15 -title "MAdmin – SX100" -e sh –c "exec login madmin"

U41272-J-Z385-3-76 39

Calling terminal instances Functions of the Solaris-CDE interface

3.4 Calling terminal instances

The desktop generated in the previous section can have the following appearance:

Figure 15: Example of a desktop

The generated actions (e.g. BS2000 console) are called either by clicking on the button in the
CDE control panel or by activating the submenu of this button (click on the small arrow at
the top edge of the icon) and the clicking on the relevant entry.

When the BS2000 console, BS2000 dialog and Machine Administration Menu are called,
authorization is needed.

When using the password mechanism, the passwords which must be entered are those of
the relevant KVP ID (BS2000 console), the em9750 ID (BS2000 dialog) and the madmin ID
(for the Machine Administration Menu), respectively. When using the Secure Shell with a
key not protected by a pass phrase, no further specification is necessary at this place.

When using the Secure Shell with a key protected by a pass phrase the pass phrase must
be entered.

The windows which are opened are closed automatically by stopping the application
running in them. BS2000 consoles are stopped by entering ::c or [CTRL] [D] . A BS2000
dialog is stopped by logging the dialog off and then pressing the [F10] key and leaving the
em9750 emulation (with Exit). Terminate the Machine Administration Menu using the
q function (for Quit).

The windows can also be closed by clicking on the top-left corner of the window and
selecting the action Close from the context menu.

40 U41272-J-Z385-3-76

Functions of the Solaris-CDE interface Calling terminal instances

If windows are opened during the current CDE session and the session is terminated with
EXIT, these windows will automatically be restarted when you next log in to the CDE
interface.

U41272-J-Z385-3-76 41

Calling terminal instances Functions of the Solaris-CDE interface

42 U41272-J-Z385-3-76

4 Functions of the System Management Console

A PRIMEPOWER250 (up to and including SX140 a PRIMESTATION) is used on SX servers
(with the exception of entry-level models) as the System Management Console (SMC):

● The SMC checks the hardware configuration and the operating status of the SX server.

● The SMC partitions the resources and thus enables the processor and memory

capacities of the SX server to be shared.

● The SMC supports partition-specific console displays.

● The SMC supports a power supply scheduling system for switching the SX server or

individual partitions on it on and off at specific times.

● The DVD/CD-ROM drive of the SMC can be used across partitions.

● In this way, operating systems and applications can be installed in every partition of the

SX server.

● The DAT drive of the SMC can be used across partitions (but usually only by service

technicians).

● On every partition of the SX server, the time is synchronized with the time of the SMC

via the network time protocol (NTP).

● The SMC monitors the entire hardware of the SX server.

● If an error is detected, the relevant information is displayed on the SMC. The system

administrator can optionally be notified by e-mail.

● The CDE interface (CDE = Common Desktop Environment) of the SMC allows access

to PRIMEPOWER ServerView (see section “Starting PRIMEPOWER ServerView

Suite” on page 196) and to BS2000 operation facilities (console, dialog; see section
“Calling terminal instances” on page 40).

This manual only describes functions which are absolutely necessary for operating the
SX server. Additional information is described in the latest version of “System Console

Software User’s Guide (SCS)” [7].

U41272-J-Z385-3-76 43

User groups and logins Functions of the System Management Console

4.1 User groups and logins

The System Console Software supports a graded system of rights to manage the hardware
functions of the SX server.

The following sections describe how to set up logins for the various administrator roles
(server administrator, partition administrator, BS2000 or Solaris administrator, and also
administrator of PRIMEPOWER ServerView) with PRIMEPOWER ServerView and the
System Console Software (SCS). It is also possible to combine multiple administrator roles
in one user ID.
Both SCS and PRIMEPOWER ServerView require root authorization to perform these
setup processes.

As of PRIMEPOWER ServerView V2.2B access to applications in PRIMEPOWER
ServerView and access to nodes of the administration domain can be defined selectively
for a PRIMEPOWER ServerView administrator via a differentiated assignment of rights.
Details on this are provided in the section “Privilege concept with Role-Based Access

Control” on page 201ff.

System administrators work with the System Management Console to manage the server.
In addition, separate administrators can be defined for individual partitions that only have
access to the assigned partition. To manage BS2000 or Solaris in a partition, it is also
possible to define BS2000 or Solaris administrators who do not have rights for managing
the hardware of the server.

This section describes how to handle user logins for the following operating staff:

● Server administrators

● Partition administrators

● BS2000 or Solaris administrators

● PRIMEPOWER ServerView administrators

The SX server is shipped ready with the following user logins for managing the

i

server from the SMC:
– A server administrator login sxadmin

– A partition administrator login bs2admin for all the BS2000 partitions present
– A partition administrator login soladmin for all the Solaris partitions that may be

present

It is recommended that you use these logins to manage the server.

44 U41272-J-Z385-3-76

Functions of the System Management Console User groups and logins

The functionality of the user groups cladmin and clmon and the partition administration
groups p0grp, p1grp, etc. described in the sections below is determined by SCS and
described in the following table. The user groups mentioned are set in the factory.

User group

cladmin clmon cemainte

Operation Adm

(1)

Non-Adm

(1)

Reference to monitoring messages and config-

XX XX

uration dialog boxes
System power-on indication X - - X
Power-on instruction, shutdown instruction,

XX - X

and dump switch instruction to the partition
Settings for Multiple-Partition Configuration X - - ­R/W (read/write) monitoring of the OS console

screen

(3)

R/O (read-only) monitoring of the OS console
screen

(4)

XX - X

XX XX

Saving crash dump data X X - ­Scheduling automatic mainframe operation X - - ­Viewing the automatic operation schedule of a

XX XX

mainframe
Maintenance operation

Table 1: Functionality of the administrator user group in the SCS

(2)

X- -X

Comments

(1) The “Adm” column designates users who belong to the user group clmon and a

partition administration group. The “Non-Adm” column designates users who
belong to the user group clmon but to no partition administration group.

(2) Maintenance functions are offered via the System Console Machine Administration.

The functions of the Machine Administration are normally used by hardware mainte­nance engineers. But system administrators who belong to the user group cladmin

can use these functions to check the hardware status.
(3) RC2000 makes read/write monitoring of a partition available for a user.
(4) RC2000 makes read monitoring of a partition available for up to 14 users.

U41272-J-Z385-3-76 45

User groups and logins Functions of the System Management Console

4.1.1 Server administrator

The administrator of the server manages the entire server and the system console.
The administrator has root access to the system console. This root authorization allows the

administrator to use all available functions of the SCS. For basic security reasons, however,
only the following actions should be performed:

– Configuring the system console (generally this is not necessary since the console has

been configured ex works)
– Adding, modifying and deleting partition administrators (where required)
– Configuring the SMC as an installation server
– Configuring and modifying server names for partitions

A login with the name sxadmin is configured by default for the server administrator. This login
is a member of the following user groups:

– cladmin (a group defined by the System Console Software with administration authori-

zation for the server).

Users in this group have administrative rights for all partitions of the server.
– wsauser as secondary user group (a group for administering PRIMEPOWER

ServerView defined by PRIMEPOWER ServerView)
In the as-supplied status the sxadmin ID has read/write access for all applications of

PRIMEPOWER ServerView and for all nodes of the administration domain.

To configure further server administrator logins, the following actions are necessary:

1. Set up the login with PRIMEPOWER ServerView in the user group cladmin:

a) Start PRIMEPOWER ServerView (see the section “Starting PRIMEPOWER

ServerView Suite” on page 196)

b) Select Applications -> Users from the menu bar
c) Select Users -> Create from the menu bar

46 U41272-J-Z385-3-76

Functions of the System Management Console User groups and logins

d) Create a new user (e.g. user name sxadmin1) as a member of the user group

cladmin:

Figure 16: PRIMEPOWER ServerView window: “Create user” (cladmin)

Make the following entries here:

– Enter the user name sxadmin1 under “User login” (the user id is assigned

automatically)
– Select the SMC as the “Node”
–Select cladmin for “Primary group”

U41272-J-Z385-3-76 47

User groups and logins Functions of the System Management Console

– No entries are required in the “Supplementary groups” section for someone who

is exclusively an SX server administrator.

If PRIMEPOWER ServerView is also to be operated in write mode under this

user ID, wsauser must be selected as the secondary user group. The secondary

user group wsaruser must be selected for operation in read mode. Membership

in one of the two user groups wsauser or wsaruser also causes this user process

to run in PRIMEPOWER ServerView with root authorization.
– Select a login shell.
– A comment can be specified if necessary.

The home directory in Solaris (in this example /export/home/sxadmin1) is
created automatically.

e) As of PRIMEPOWER ServerView V2.2B the access rights of this user ID can be

defined more specifically with regard to access to applications in PRIMEPOWER
ServerView and access to nodes in the administration domain. Further details are
provided in the section “Privilege concept with Role-Based Access Control” on

page 201ff.

2. Set up the SCS user interface (Termi na l in the Application Manager) for the server
administrator using the following command (which must be performed with root
authorization):

/opt/FJSVscsl/bin/scslowneradd -a <username>

The option -a here stands for “administrator”.

48 U41272-J-Z385-3-76

Functions of the System Management Console User groups and logins

4.1.2 Partition administrators

Partition administrators also use the interface of the System Console Software to manage
the hardware of the partition. They have access to the hardware console of the partition
assigned to them and are authorized to switch the partition on/off. They do not have rights
to any other partitions.

Two partition administrator logins are configured by default for the two platform types:

● bs2admin for all BS2000 partitions present

● soladmin for all Solaris partitions that may be present

A login is configured for the partition administrator. This login is a member of the following
SMC user groups:

● clmon (this is a group with monitoring rights for all partitions of the server)

● In all partition administration groups which belong to the platform type concerned (each

group has administration rights for the partition assigned to it)

In addition the login is a member of the secondary user group wsauser which provides
authorization to administer PRIMEPOWER ServerView.

Partition administration groups correspond one-to-one to server partitions. A user regis­tered in this group has the rights needed for managing the partition and can carry out input
and output operations on the RC2000 console of the partition.

In the as-supplied status a partition administrator login has read/write access to all applica­tions of PRIMEPOWER ServerView of the nodes on the platform type concerned.

To configure further partition administrator logins, the following actions are necessary:

1. Configure the login with PRIMEPOWER ServerView in the user group clmon:
a) Start PRIMEPOWER ServerView (see the section “Starting PRIMEPOWER

ServerView Suite” on page 196)

b) Select Applications -> Users from the menu bar
c) Select Users -> Create from the menu bar

U41272-J-Z385-3-76 49

User groups and logins Functions of the System Management Console

d) Create a new user (e.g. user name soladmin2) as a member of the user group clmon:

Figure 17: PRIMEPOWER ServerView window: “Create user” (clmon)

No entries are required in the “Supplementary groups” section for someone who is

exclusively an SX server administrator.

If PRIMEPOWER ServerView is also to be operated in write mode under this user

ID, wsauser must be selected as the secondary user group. The secondary user

group wsaruser must be selected for operation in read mode. Membership in one of

the two user groups wsauser or wsaruser also causes this user process to run in

PRIMEPOWER ServerView with root authorization.

As of PRIMEPOWER ServerView V2.2B the access rights of this user ID can be

defined more specifically with regard to access to applications in PRIMEPOWER

ServerView and access to nodes of the administration domain. Details on this can

be found in the section “Privilege concept with Role-Based Access Control” on

page 201ff.

50 U41272-J-Z385-3-76

Functions of the System Management Console User groups and logins

2. If necessary, configure a further partition-specific user group with PRIMEPOWER
ServerView, e.g. part1grp.

User groups suitable for this have already been configured by default with the

i

name p0grp, p1grp, etc. and are used for the partition administrators bs2admin
and soladmin.

These groups can be used when configuring further partition administrators.
Alternatively, further user groups can also be created for this.

Click on the Groups tab and select Groups -> Create from the menu bar:

Figure 18: PRIMEPOWER ServerView window: “Create group”

3. Set up the SCS user interface (Termi na l in the Application Manager) for the partition
administrator using the following command (which must be executed with root
authorization):

/opt/FJSVscsl/bin/scslowneradd -h <server name of partition>:<partition
administration group> <username>

The -h option here stands for partition administrator.

U41272-J-Z385-3-76 51

User groups and logins Functions of the System Management Console

4.1.3 BS2000 or Solaris administrators

To manage the operating systems of individual partitions, it may be useful to configure user
IDs which do not have extended rights relating to the management of the hardware of the
server (like server administrators or partition administrators).

These user IDs must however be able to read the data of the RC2000 consoles of the parti­tions.

These IDs are also suitable for the administrator for preconfiguring terminals to access the
partitions (see also section “Preconfiguring terminals” on page 32).

The following actions are needed to configure a user ID of this type:

1. Set up the login with PRIMEPOWER ServerView in the user group clmon:
a) Start PRIMEPOWER ServerView (see the section “Starting PRIMEPOWER

ServerView Suite” on page 196)

b) Select the Users application
c) Select Users -> Create from the menu bar
d) Create a new user (e.g. user name bs2adm1) as a member of the user group clmon

No entries are required in the “Supplementary groups” section for someone who is

exclusively an SX server administrator.

If PRIMEPOWER ServerView is also to be operated in write mode under this user

ID, wsauser must be selected as the secondary user group. The secondary user

group wsaruser must be selected for operation in read mode. Membership in one of

the two user groups wsauser or wsaruser also causes this user process to run in

PRIMEPOWER ServerView with root authorization.

As of PRIMEPOWER ServerView V2.2B the access rights of this user ID can be

defined more specifically with regard to access to applications in PRIMEPOWER

ServerView and access to nodes of the administration domain. Details on this can

be found in the section “Privilege concept with Role-Based Access Control” on

page 201ff.

52 U41272-J-Z385-3-76

Functions of the System Management Console User groups and logins

2. Set up the SCS user interface (Termi na l in the Application Manager) for the user ID
using the following command (which must be executed with root authorization):

/opt/FJSVscsl/bin/scslowneradd -h <server name_of_partition>:clmon <user
name>

In the next step you must remove the assignment of administration rights to a partition
which was needed temporarily to set up the SCS user interface. Proceed as follows:

3. Remove partition administration rights
The entry generated by the command scslowneradd in the file /etc/FJSVclowners

must be removed using an editor (e.g. vi).
The line to be deleted comprises an entry with the following format:

clmon:<server name of partition>.

4.1.4 Administration of PRIMEPOWER ServerView

The actions described under item 1 are required to set up a user ID which has no extended
rights with regard to the hardware administration of the server and can be operated under
PRIMEPOWER ServerView.

As of PRIMEPOWER ServerView Suite V2.2B it is possible to define the access rights of
this user ID with regard to access to applications in PRIMEPOWER ServerView and the
access to nodes of the administration domain more precisely (see item 2 on page 55). The
information required for this is provided in the section “Privilege concept with Role-Based

Access Control” on page 201ff.

1. Setting up the user ID with PRIMEPOWER ServerView in the primary user group other
or in a user group defined by the user (a user group can be generated in the Groups tab
in the Users group by clicking on the Groups button):

a) Start PRIMEPOWER ServerView (see the section “Starting PRIMEPOWER

ServerView Suite” on page 196)

b) Select the Users application.
c) Select Users -> Create in the menu bar.

U41272-J-Z385-3-76 53

User groups and logins Functions of the System Management Console

d) Create the new user (e.g. user name pwsvadm)

Figure 19: PRIMEPOWER ServerView window:”Create user” (administrator of PRIMEPOWER

ServerView)

As the user is not to be allocated special SCS privileges, the user must be assigned

as a member of the primary user group other. The SMC must be selected as the

node.

To permit PRIMEPOWER ServerView to be operated in write mode under this ID at

a later time the user ID must be entered in the secondary user group wsauser which

is defined for this purpose. If you wish to operate PRIMEPOWER ServerView only

in read mode, the secondary user group wsaruser must be selected. Membership in

one of the two user groups wsauser or wsaruser ensures that this user group runs

within PRIMEPOWER ServerView with root authorization

To do this you must select the secondary user group from the window and add it

using the Add button.

54 U41272-J-Z385-3-76

Functions of the System Management Console User groups and logins

2. After this it may be necessary to adjust the access rights to the applications of
PRIMEPOWER ServerView and the nodes of the administration domain.

In the following cases such a user ID is automatically assigned the full access rights to
all available applications of PRIMEPOWER ServerView and to all nodes of the
administration domain:

● Use of PRIMEPOWER ServerView Suite Version < V2.2B

● When the user ID is created the feature Role Based Access Control (RBAC) is not

activated in PRIMEPOWER ServerView.

If the RBAC feature is activated in PRIMEPOWER ServerView when the user ID is
created, the user ID is not assigned access rights to the PRIMEPOWER ServerView
applications or the nodes of the application domain. These rights must then be set
accordingly.

The interface for checking, setting, and modifying the RBAC access rights is described
in the section “Privilege concept with Role-Based Access Control” on page 201ff.

U41272-J-Z385-3-76 55

System console software (SCS) Functions of the System Management Console

4.2 System console software (SCS)

The system console menu used to activate the functions looks like this:

Figure 20: System console menu

Click the system console icon in the toolbar to open the menu.

56 U41272-J-Z385-3-76

Functions of the System Management Console System console software (SCS)

The table below describes the functions of the tools provided on the system console:

Function Description

System Console Menu with the functions provided by the system console. Is automati-

cally started after logging in.

RC2000 Shows a host browser via which the console windows of the server can

be opened. Is automatically started after logging in.

Monitoring Messages Shows server errors, for instance, which are acknowledged by the

system console. Is automatically started after logging in.

Configuration Shows the partition structure of the server. Is automatically started after

logging in.

Machine Administration
Menu

Terminal Allows commands to be executed on the system console.
Web-Based Admin View This function is currently not used.
User's Guide Shows the user's guide to the System Console Software.

Opens the system administration window of the system console.

If the functions provided by the system console were closed before logging out, they are not
automatically displayed when you log into the system again. If this happens, click on the
relevant icon in the toolbar or in the Application Manager to start a function.

If the Application Manager window was minimized before the last logout, it does not appear
maximized when you log into the system again.

U41272-J-Z385-3-76 57

Functions of the System Console Software (SCS) Functions of the System Management Console

4.3 Functions of the System Console Software (SCS)

This section describes the SCS functions Machine Administration Menu, RC2000 and
Monitoring Messages.

4.3.1 Machine Administration Menu

The System Console Machine Administration Menu enables the management and servicing of
the system hardware.

This menu is available for administrators of the system console or service engineers.
This function is called up by selecting Machine Administration Menu from the system console

menu (see figure 20 on page 56) or by double-clicking on the Machine Administration Menu
icon in the Application Manager (see figure 11 on page 30):

Menu name

Figure 21: Machine Administration Menu

The menu name does not appear in the frame but as the first line in the text window.

58 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

4.3.1.1 Functions for switching the server on/off

This section describes how the power supply of the server is handled via the system
console.

The following procedure describes how to access the System/Partition Power Administration
Menu:

1. Select System Specific Administration:

1 <RETURN>

All available servers are offered for selection.

Example

System-Specific Administration
Segment ID#1

This is a list of the servers.
A menu for each server can be activated for units containing a
description of server names.

No Server name

--- ---------------­001 machine0

q:Quit b:Back to previous menu t:Go to top menu h:Help

------------------------------------------------------------­Select.(n,q,b,t,h):

U41272-J-Z385-3-76 59

Functions of the System Console Software (SCS) Functions of the System Management Console

2. Select the required server.

Example

1 <RETURN>

The System-Specific Administration menu is opened for the selected server (in this
example machine0 of the SX150 server):

Server

Figure 22: Machine Administration Menu: “System-Specific Administration”

60 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

3. Select System/Partition Power Administration:

8 <Return>

This opens the menu System/Partition Power Administration for the selected server
(machine0):

Figure 23: Machine Administration Menu: “System/Partition Power Administration”

The System/Partition Power Administration menu contains the following functions:

1. System Power-On Instruction Switches the server on

2. System Power-Off Instruction Switches the server off

3. Partition Power-On Instruction Switches a partition on

4. Partition Power-Off Instruction Switches a partition off

WARNING!

!

The following menu items should only be used by a service engineer, otherwise
the operation of the system can be disrupted:

5. Partition Dump Switch Instruction A system crash is initiated. A dump is

generated as a diagnostic document.

6. Partition Reset Instruction Resets a partition

7. Partition forced Power-Off Instruction Forced switching off of a partition

8. Warm-up Time Administration Sets the warming-up time

9. Fan Stop Delay Instruction Sets the stop delay of the fan

10. Wait Time Administration Sets the wait time for switching on

U41272-J-Z385-3-76 61

Functions of the System Console Software (SCS) Functions of the System Management Console

Switching the entire server on

The function System Power-On Instruction switches the server on if it is switched off.
Switching on the server via this menu item has the same effect as powering on the server

via the control panel on the front side of the SX server (see the SX1xx Operating
Manual [2]).

1. Select the function System Power-On Instruction from the menu System/Partition Power
Administration:

1 <RETURN>

The following screen output enables the status of the server power supply to be
checked first:

machine0 System-Specific Administration
System Power-On Instruction

System Power status OFF

Do you want to issue the power-on instruction
to this system? (y: yes)

q:Quit b:Back to previous menu t:Go to top menu h:Help

------------------------------------------------------------­Select.(y,q,b,t,h):

In this example, the server is switched off.

2. To switch the server on, enter:

y <RETURN>

If the server is already switched on (on status), the action is ignored.

62 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

Switching the entire server off

The function System Power-Off Instruction switches the server off if it is switched on.

1. Select the function System Power-Off Instruction from the menu System/Partition Power
Administration:

2 <RETURN>

The following screen output enables the status of the server power supply to be
checked first:

machine0 System-Specific Administration
System Power-Off Instruction

System Power status ON

Do you want to issue the power-off instruction
to this system? (y: yes)

q:Quit b:Back to previous menu t:Go to top menu h:Help

------------------------------------------------------------­Select.(y,q,b,t,h):

In this example, the server is switched on.

2. To switch the server off, enter:

y <RETURN>

If the server is already switched off (off status), the action is ignored.

U41272-J-Z385-3-76 63

Functions of the System Console Software (SCS) Functions of the System Management Console

Switching partitions on

The function Partition Power-On Instruction switches on one or more partitions.

Switching on a partition starts the operating system in the partition.

i

1. Select the function Partition Power-On Instruction from the menu System/Partition Power
Administration:

3 <RETURN>

The following screen output shows the status of the individual partitions on the selected
server.

Example

machine0 System-Specific Administration
Partition Power-On Instruction

PID Power status

-- --­00 ON
01 OFF
02 OFF

Select the partitions to be powered on. (a: All)
To specify multiple PIDs, separate with a comma (,).

q:Quit b:Back to previous menu t:Go to top menu h:Help

------------------------------------------------------------­Select.(n,a,q,b,t,h):

In this example, the partitions of the server machine0 with the PIDs 01 and 02
(PID = Partition ID) are switched off.

2. To switch the partitions on, enter the PID(s), separated by a comma.

Example

1,2 <RETURN>

Entering a <RETURN> has the same effect in this example.
If a partition has already been activated, the command for this partition is ignored.

64 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

Switching partitions off

The function Partition Power-Off Instruction powers off one or more partitions.

1. Select the function Partition Power-Off Instruction from the menu System/Partition Power
Administration:

4 <RETURN>

The following screen output shows the status of the individual partitions on the required
server.

Example

machine0 System-Specific Administration
Partition Power-Off Instruction

PID Power status

-- --­00 ON
01 ON
02 ON

Select the partition to shutdown. (a: All)
To specify multiple PIDs, separate with a comma (,).

q:Quit b:Back to previous menu t:Go to top menu h:Help

------------------------------------------------------------­Select.(n,a,q,b,t,h):

In this example, all partitions of the server machine0 are switched on.

2. To switch the partitions off, enter the PID(s), separated by a comma. In the following
example, the partitions with the PIDs 00 and 01 are switched off:

0,1 <RETURN>

The following entry switches off all partitions:

a <RETURN>

If a partition has already been switched off, the command for this partition is ignored.

U41272-J-Z385-3-76 65

Functions of the System Console Software (SCS) Functions of the System Management Console

4.3.1.2 Switching the server on/off on a scheduled basis

The automatic power control system (APCS: ) switches the server on or off automatically,
on the basis of a series of on/off schedule entries. These entries form the system schedule.

Switching on/off thus affects all partitions of the server.
Switching on automatically starts the operating system of the partition if the mode selector

of the system is in the LOCK position (normal mode) (see sections “Switching the entire

server on” on page 62 and “Mode selector” in the SX1xx Operating Manual [2]). Switching

the server off in this switch position shuts down the operating system. For BS2000/OSD
partitions, this involves starting/shutting down the carrier system X2000.

For an automatic IPL (Initial Program Load) of BS2000 on switching on the server (see
“Configuration of automatic IPL (G)” on page 215) or for an automatic shutdown of BS2000
(see “Evaluation of shutdown (X)” on page 216) on switching off the server, the relevant
entries must be made in the KVP menu.

Ê Select System-Specific Administration from the Machine Administration Menu (see figure 21

on page 58):

1 <RETURN>

Ê Select the required server.

66 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

Ê Select Auto Power Control System (APCS) Administration from System-Specific

Administration (see figure 22 on page 60):

11 <RETURN>

This opens the APCS Setup Menu:

Figure 24: Machine Administration Menu: “APCS Setup Menu”

The following actions can be performed using this menu:
– Starting the system schedule

– Stopping the system schedule
– Adding an entry to the schedule and deleting an entry
– Adding a holiday
– Deleting a holiday
– Deleting the entire schedule
– Listing all schedule entries
– Showing the schedule status

To create or delete schedule entries and enable APCS operation, proceed as follows:

1. Select the function Stop System Schedule to stop the system schedule:

2 <RETURN>

2. Select Add System Schedule Entry to add an entry:

3 <RETURN>

Follow the instructions for adding a schedule entry.

U41272-J-Z385-3-76 67

Functions of the System Console Software (SCS) Functions of the System Management Console

Examples

a) Setting the power on time:

Set Power On Time (Add)

Please set the automatic power on time.
Press the "RETURN" key if you do not wish to power on the system
automatically.

Example)
Power on at AM 8:00 : 0800
Power on at PM 2:00 : 1400

q:quit b:back t:top

---------------------------------------------------------------------­Select.(HHMM,q,b,t):

Enter the four-digit time and press the Return key. Or just press the Return key if no
power on time is to be set.

b) Setting the power off time:

Set Power Off Time (Add)

Please set the automatic power off time.
Press the "RETURN" key, if you do not wish to power off the system
automatically.

Example)
Power off at 0:00 AM : 0000
Power off at 11:00 PM : 2330

q:quit b:back t:top

---------------------------------------------------------------------­Select.(HHMM,q,b,t):

Enter the four-digit time and press the Return key. Or just press the Return key if no
power off time is to be set.

68 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

c) Setting the schedule:

Schedule Setup (Add)

Please set the day or days to put into operation.

.Specific Day
Example) Feb. 1st, 2000 : 20000201

.Specific days in this month
Example) From 1st through 10th : 01-10

.To repeat this for several months
Example) From 1st through 10th in Feb.
through May : 01-10 -r 02-05

.From a specific day through another specific day
Example) From Feb. 1st through Jun. 10th : 0201-0610

.Specific day of the week
Sunday : SUN
Monday : MON
Tuesday : TUE
Wednesday : WED
Thursday : THU
Friday : FRI
Saturday : SAT

Example) Every Monday or Tuesday from Feb. through May :
MON,TUE -r 02-05

q:quit b:back t:top

---------------------------------------------------------------------­Select.(schedule,q,b,t):

Enter the schedule as for the above examples. Then press the Return key.

U41272-J-Z385-3-76 69

Functions of the System Console Software (SCS) Functions of the System Management Console

3. You can enter holidays with the function Add Holiday:

4 <RETURN>

Example

Add Holiday

Please set the day when schedule entry or entries are to be ignored.

Example)
Feb. 1st, 2000 : 20000201

q:quit b:back t:top

---------------------------------------------------------------------­Please input.(YYMMDD,q,b,t):

Enter the six-digit holiday date (YYMMDD). Then press the Return key.

4. To check the schedule entries, select the function Show Status of System Schedule:

8 <RETURN>

Example

STATUS : APCS has been stopped by operator
PRESENT : 9/27(Fri) 2 14:51:43
POWER-OFF : -
POWER-ON : -
OVER : -
SCHEDULE OF 7 days NEXT:
DATE TIME FUNC PROCEDURE
{END OF DATA}

press return key:

Show Status of System Schedule only shows the data for a period of 7 days

i

(beginning at the current time). To display a longer period, use the following

apcsset command (-L Option):

#/opt/FJSVapcs/sbin/apcsset -s machine0 -L 30 -f

For details on the apcsset command, see “System Console Software User’s

Guide (SCS)” [7].

5. To delete schedule entries (including holidays), use the menu item Select and Delete
Entire System Schedule:

5 <RETURN>

70 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

6. Select the function Start System Schedule to start the system schedule:

1 <RETURN>

7. Transfer the schedule to every partition:
If the server is switched on while changes are being made to the schedule, these

changes need to be passed to the console of every partition via the schedule update
command:

# /opt/FJSVapcs/sbin/apcsflush

For further details on the apcsflush command, see “System Console Software User’s

Guide (SCS)” [7]. This command only transfers the schedule to the partition. The

system is only affected if one of the setpoints specified in the schedule is reached.

Individual partitions cannot be switched on or off under time control. However, this

i

functionality can be used via the processes described in the section below.

4.3.1.3 Switching partitions on/off on a time-driven basis

Time-driven commands

Time-driven execution of a command can be defined in the Ta sks application of the
PRIMEPOWER ServerView Suite. The Tasks -> Create task function opens a calendar
window which provides a straightforward way of declaring a time scheme. The Node window
enables you to select a node (in this application the SMC must be specified). In the
Command window you can specify a single command or a script which is then executed with
root authorization at the specified times.

The definitions are activated when they have been defined, i.e. the task has the enabled
status. Clicking on the definition with the right mouse button and selecting the De-/Activate
function deactivates or reactivates it.

The Task s application is a generally usable, convenient encapsulation of the cron job which
avoids errors. When a time scheme is defined corresponding entries are generated in the
crontab.

A separate calendar screen must be created for each command or script. Further condi­tions for starting or suppressing reactions must be implemented in the script. These include,
for example, the inclusion of public holidays.

U41272-J-Z385-3-76 71

Functions of the System Console Software (SCS) Functions of the System Management Console

In this application the tasks are preferably executed on the SMC since the System Console
Software (SCS) is only directly available there.

Example

Activating a partition every Monday at 8.00 a.m..

Figure 25: PRIMEPOWER ServerView- window: “Create task”

Switching a partition on

A partition is switched on with the following SCS command:

/opt/FJSVcsl/bin/node_control -up <machine_name> -pid=<partition ID>

Example

/opt/FJSVcsl/bin/node_control -up fernando0 -pid=1

72 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

After the power supply has been switched on the system unit is started up. After the POST
(Power On Self Test) the Solaris operating system and, in the BS2000 partitions, the X2000
carrier system is started automatically if the mode selector in the SX server’s control panel
is set to LOCK (see figure “Control panel of an SX140 or SX150 server”). Furthermore, no
time interval may be set via the Auto Power Control System (APCS) of SCS in which the
system is to be deactivated. Settings in the APCS are made via Machine Administration Menu
(System-Specific Administration -> select machine_name -> APCS Administration).

Cursor pushbutton CHECK-LED (yellow/orange)

Status display LCD

Figure 26: Control panel of an SX140 or SX150 server

POWER-LED (green)

POWER CHECK

Decision pushbutton

On/Off switch

UNLOCK

LOCKMAINTE-

NANCE

Mode selector

When X2000 is started, BS2000/OSD is also started automatically if this was specified by
setting the automatic IPL. This setting must be made in the BS2-KVP register of the
Bs2Devices application of PRIMEPOWER ServerView:

1. Select the first entry with the KVP name HV0 and click on it with the right mouse button.

2. Then set the function “Configuration of automatic IPL”.

The machine_name and partition ID parameters needed for this command can be ascer­tained in the CDE interface on the SMC. After you have pulled down the icon Configuration
on the System Console (SCS) the machine_name is displayed in the Server column and the

partition ID in the PID column.

Example

Figure 27: Configuration window

U41272-J-Z385-3-76 73

Functions of the System Console Software (SCS) Functions of the System Management Console

Switching a partition off

A partition is switched off using the following SCS command:

/opt/FJSVcsl/bin/node_control -down <machine_name> -pid=<partition ID>

Example

/opt/FJSVcsl/bin/node_control -down fernando0 -pid=1

In this case any Solaris system which is still running is closed down in an orderly manner
and the power supply to this partition is interrupted. This procedure can take about
1minute.

In BS2000 partitions any BS2000 system which is still running will be shut down and X2000
then closed down. A prerequisite here is that shutdown is really specified in the BS2-KVP
register of the Bs2Devices application of PRIMEPOWER ServerView under “Definition of the
BS2000 shutdown command”.

Comments

● The Auto Power Control System of SCS (APCS, see the section “Switching the server

on/off on a scheduled basis” on page 66) can only be used to switch the entire server

on/off on a time-driven basis .

● Machine Administration Menu (System-Specific Administration -> select machine_name ->

System/Partition Power Administration) enables a partition to be switched on or off, but not

on a time-driven basis.

Information functions

The power on/off status of one or more server partitions, together with system-board­specific information, can be ascertained using the following function:

/opt/FJSVcsl/bin/get_node_conf <machine_name> -s [-pid=<partition ID>]

Example

/opt/FJSVcsl/bin/get_node_conf fernando0 -s

root@fernandoADM # /opt/FJSVcsl/bin/get_node_conf fernando0 -s
SB#00-0:type=1,pid=00,serial=PB350A0403,status=ON
SB#00-1:type=1,pid=00,serial=PB350A0403,status=ON
SB#00-2:type=1,pid=01,serial=PB350A0403,status=OFF
SB#00-3:type=1,pid=01,serial=PB350A0403,status=OFF
SB#01-0:type=1,pid=02,serial=PB350A0603,status=ON
SB#01-1:type=1,pid=02,serial=PB350A0603,status=ON
SB#01-2:type=1,pid=00,serial=PB350A0603,status=ON
SB#01-3:type=1,pid=00,serial=PB350A0603,status=ON
root@fernandoADM #

74 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

4.3.1.4 Administering the system board’s operating mode

In SX140 systems or higher it is possible to define, ascertain or modify the operating mode
of any system board located in a cabinet slot. A system board can be operated in the
following modes:

X for the extended system board (XSB) mode
P for the physical system board (PSB) mode
On SX130 systems there are only physical system boards.

Ê In the Machine Administration Menu (see figure 21 on page 58) select the menu item

System-Specific Administration:

1 <RETURN>

Ê Select the required server.
Ê In the System-Specific Administration menu (see figure 22 on page 60) select the menu

item SB Mode Administration.

13 <RETURN>

Comment

On SX140 systems you must select the menu item System Board Maintenance
Administration and then SB Mode Administration in the System-Specific Administration
menu.

U41272-J-Z385-3-76 75

Functions of the System Console Software (SCS) Functions of the System Management Console

The SB Mode Administration menu is opened:

Figure 28: SB Mode Administration Menu

The current operating mode of each system board in a slot s in cabinet c (presented in the
format cs in the Slot column, in other words, for example, 01 for slot 1 and cabinet 0) is
displayed in the Mode column of this menu:

X The system board is operated in XSB mode.
P The system board is operated in PSB mode.
The status id the system board is also displayed in the Status column. The following values

are possible:
– – – The system board is not inserted in the slot.
ON The system board is turned on.
OFF The system board is not used or the power is off.
ALM The system board is inserted in the slot and is working, but not correctly.
ON* PCI/DISK BOX or memory are not installed or the installation cannot be recognized.
In XSB mode the numbers of the configured XSBs are displayed in the XSB column for each

slot in each cabinet.

76 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

This menu also enables a system board to be configured or modified. To modify a board
you must first select the function m. You can then use the function x in XSB mode and the
function p in PSB mode to modify it (see also the Select line in figure 28 on page 76).

Ê After a modification you must restart SCS:

#/etc/init.d/FJSVscsl restart

U41272-J-Z385-3-76 77

Functions of the System Console Software (SCS) Functions of the System Management Console

4.3.1.5 Configuring and modifying partitions

Partitions can be configured for the operating systems and applications which run on them
using the physical and/or (from SX140 systems on) the extended system board mode. In
this case a partition can, however, only incorporate on type of system board mode.

Ê In the Machine Administration Menu (see figure 21 on page 58) select the menu item

System-Specific Administration:

1 <RETURN>

Ê Select the required server.
Ê In the System-Specific Administration menu (see figure 22 on page 60) select the menu

item Partition/System Board Administration.

6 <RETURN>

Figure 29: Partition and System Board Administration Menu, taking an SX150 server as an example

78 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

Adding a system board to a partition
Ê To add a system board to a partition select the menu item System Board Addition to

Partition in the Partition and System Board Administration menu:

2 <RETURN>

The System Board Addition to Partition menu is opened. This provides information on the
division of the system boards to the partitions and their status.

Figure 30: System Board Addition to Partition Menu, taking an SX150 server as an example

The “SP” display in the Now PID column indicates that this system board is in the system
board pool. The > sign in front of the SB column indicates which system board is being
processed with this screen.

Ê You must then enter the number of the partition which you assign to this system board,

or enter “s” if you do not wish to initiate an action.

The modifications only take effect after Solaris has been rebooted.

U41272-J-Z385-3-76 79

Functions of the System Console Software (SCS) Functions of the System Management Console

Removing a system board from a partition
Ê To remove a system board from a partition select the menu item System Board Removal

from Partition in the menu Partition and System Board Administration:

3 <RETURN>

The System Board Removal from Partition menu is opened. This provides information on the
division of the system boards to the partitions and their status.

Figure 31: System Board Removal from Partition Menu, taking an SX150 server as an example

The “SP” display in the Now PID column indicates that this system board is in the system
board pool.

Ê Enter the number(s) of the system board(s) (separated by a comma) which you want to

remove from a partition.

The modifications only take effect after Solaris has been rebooted.

80 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

4.3.1.6 Configuring/changing the partitioning

At least one partition of the SX server is reserved for running BS2000/OSD. These parti­tions are designated below as BS2000/OSD partitions.

In addition to the BS2000/OSD partitions, an SX server can include Solaris partitions.
Configuring a Solaris partition and adding or removing system boards of a partition is
carried out in the same way as for the PRIMEPOWER servers.

The necessary actions for Solaris partitions are described in the manuals “System Console

Software User’s Guide (SCS)” [7], “Partition Operation Guide” [27] and “Dynamic

Reconfiguration – Introduction to the Procedure” [25].

4.3.1.7 Displaying the configuration

You can display the hardware configuration and the operating status of the server using the
Machine Administration Menu. This is particularly important for the Solaris part of the server.
In addition, PRIMEPOWER ServerView offers options for displaying the operating status of
the individual partitions under DomainAdmin. For further information, see the manual
“PRIMEPOWER ServerView Suite V2.2 – System Administration within a Domain” [5].

Select System Specific Administration (see figure 22 on page 60) from the menu Machine
Administration Menu (see figure 21 on page 58), to list the servers managed by the SMC.
Then select the relevant server.

U41272-J-Z385-3-76 81

Functions of the System Console Software (SCS) Functions of the System Management Console

Now you can call up information on the hardware and partition configuration:

● Server hardware configuration

After selecting Hardware Configuration Displays, the following menu is opened. This
example is for an SX130 server:

Figure 32: Machine Administration Menu: “Hardware Configuration Displays”

The following options are available:
– Display of server-specific information (Display System Information)

– Display of system-cabinet-specific information (Display Cabinet Specific Information;

valid for SX130 servers only)

– Display of system-board-specific information (Display System Board Specific

Information; valid for SX130 servers only)

For the SX servers as of the SX140 model series both system-cabinet-specific and system­board-specific information is included in the server-specific information.

In this example for the SX130, the server-specific information should be

i

● Partition configuration

displayed.

The assignment of system boards to partition numbers can be viewed with Partition
Display or System Board Status Display under Partition/System Board Administration. The
key information which is displayed is the number of the system board, the current
partition ID and the partition ID on the next system start.

82 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

Example for SX130: displaying system information (Display System Information)

Enter “1”; the server-specific information will be displayed:

PRIMEPOWER800 Serial No:23092; System Clock:225 MHz;
Operation Panel Switch:Lock; Altitude:0 m;
Partition#00 1 System Board;
Hostname:bari1; Host ID:80f30766;
Partition MAC:00.00.0e.25.07.66;
Partition Node address:10100;
CPU Clock:675 MHz; Enable Clock:675 MHz;
Partition#01 1 System Board;
Hostname:bari2; Host ID:80f3071d;
Partition MAC:00.00.0e.25.07.1d;
Partition Node address:10101;
CPU Clock:675 MHz; Enable Clock:675 MHz;
Partition#02 1 System Board;
Hostname:bari3; Host ID:80f309a4;
Partition MAC:00.00.0e.25.09.a4;
Partition Node address:10102;
CPU Clock:675 MHz; Enable Clock:675 MHz;
Partition#03 1 System Board;
Hostname:bari4; Host ID:80f309a5;
Partition MAC:00.00.0e.25.09.a5;
Partition Node address:10103;
CPU Clock:675 MHz; Enable Clock:675 MHz;
Cabinet#0 Serial No:23092; RCI(000101ff);
Partition[ 00 01 02 03 ] Master Clock;

This menu item displays the following information about the server:
Model

Specifies the model name, serial number and clock frequency of the server.

Operation panel

Specifies the position of the mode selector and the height above sea-level at which the
server is installed.

Partition

Displays information on previously defined partitions. This includes partition IDs of the
relevant partitions, the number of system boards, server IDs, MAC addresses, node
addresses and CPU clock frequency.

Cabinet

Shows information about the system cabinet. This includes the cabinet ID, cabinet serial
number, RCI addresses and the ID numbers of the partitions.

U41272-J-Z385-3-76 83

Functions of the System Console Software (SCS) Functions of the System Management Console

4.3.1.8 Error notifications

The system console SMC detects hardware errors on the server and generates messages
when an error occurs. This involves the following functions:

– Displaying detected errors in the message window of the console (monitoring

messages)

– Notifying the administrator or service engineer by e-mail
– Notifying the service provider via Teleservice

The settings for outputting error notifications via message windows or e-mail are defined in
the System-Specific Administration menu (see figure 22 on page 60) under System Notification
Administration:

1. Select System-Specific Administration from the Machine Administration Menu (see figure 21

on page 58).

2. Select the server whose data you wish to view (see figure 21 on page 58).

3. Select System Notification Administration:
This outputs the following screen:

Figure 33: Machine Administration Menu: “System Notification Administration”

84 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

You can make the following settings under System Notification Administration:

● Output error messages in a message window on the system console

● Notify the system administrator by e-mail

Determine whether the system administrator is to be informed by e-mail about errors
which occur.

If a notification is to be made, specify further information about the system adminis­trator, e.g. his/her name and e-mail address.

● Notify the relevant service engineer by e-mail

If a notification is to be made, specify further information about the service engineer,
e.g.his/her name and e-mail address.

● Sender of the e-mail

Specify the e-mail address of the sender.

When notifying by e-mail, it is necessary to enter an SMTP server to which the mails can
be sent; enter this in the file /etc/hosts.

This entry must be created in the following format:

<IP address> <server name> mailhost

The name mailhost is predefined. It instructs Solaris to send mails to this address.

U41272-J-Z385-3-76 85

Functions of the System Console Software (SCS) Functions of the System Management Console

4.3.2 Consoles of the partitions with RC2000

This section describes how the RC2000 system (RC = Remote Console) is handled.

Activating RC2000

This function is called up by selecting RC2000 from the system console menu (see figure 20

on page 56) or by double-clicking the RC2000 icon in the Application Manager (see figure 11
on page 30):

When RC2000 has been activated, a host browser is displayed.

Figure 34: RC2000 main window

Automatic activation with login

When you log in at the system console for the first time, RC2000 is activated with the default
window size and positioning. When you log in on subsequent occasions, RC2000 will be
displayed as it was stored at the last log off.

The RC2000 window will not be automatically displayed if it was not opened when the
system was last closed. Log on for the SCS main window and then activate RC2000 via the
SCS button.

Activating from the Application Manager window

Ê Double-click the RC2000 icon in the Application Manager window.

86 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

Activating the console window of partitions

Proceed as follows to open the console window:

Activating from the menu

1. Select a partition from the host browser (RC2000).

2. Select [Connect] from the Execute menu.

The console window of the partition selected in the host browser is then displayed.

Activating with a double-click

Ê Double-click the partition in the host browser.
The console window of the partition selected in the host browser is then displayed.
Only one console window can be opened for each partition, in which read/write operations

can be carried out. A maximum of 14 console windows can be opened, however, which only
have read permission.

Under the menu item Execute you can edit the access rights for the console window.

i

Closing the console window

Proceed as follows to close the console window again:

Closing via the menu of the host browser

1. Select a partition from the host browser.

2. Select [Disconnect] in the Execute menu.

The console window of the partition selected in the host browser is then closed.

Closing via the menu of the console window

1. Open the application menu in the top left corner of the console window to be closed.

2. Select Exit.

The relevant console window is then closed.

U41272-J-Z385-3-76 87

Functions of the System Console Software (SCS) Functions of the System Management Console

4.3.2.1 OBP

OBP mode only applies to one partition. It is used, for instance, to perform an offline backup.
After a partition is switched on or reset, a POST sequence (POST = Power On Self Test) is

started. This tests the hardware and checks the hardware configuration. The OBP
(OBP = OpenBoot

Power-On / Reset

of the partition

TM

PROM) is then called up. This checks the PCI devices.

POST

Self test diagnostic

Hardware configuration

OBP

Probe PCI devices

OS booting OBP cmd’s

OS Solaris

Figure 35: Sequence of POST, OBP and Solaris startup after switching on or a reset

If the mode selector is set to Unlock or Maintenance, the following OBP prompt appears:

{0} ok

If the mode selector is set to “Lock”, the partition must be terminated with init 0. This
automatically takes you into the OBP mode.

From this mode, Solaris can be started with the relevant command. Specific OBP
commands can also be entered here.

Example of screen outputs until the OBP prompt appears

POST Sequence 03
...
POST Sequence 1a
POST Sequence Complete
Fujitsu Siemens PRIMEPOWER800 2-slot 4x SPARC64 IV 675MHz
OpenBoot 3.14.7-1, 4096 MB memory installed
Ethernet address 0:0:e:25:5:22, Host ID: 80f30522.
{0} ok

88 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

OBP commands

OBP help function

{0} ok help

A help text on the individual commands is output:

{0} ok help
go
boot
boot <device-name>
printenv
setenv <name> <value>
devalias
devalias <name> <value>
show-devs

Many Other commands are available.
{0} ok

System and boot configuration parameters

printenv Shows the possible variable values which can be set

in OBP

setenv [var] [value] Sets the variable values
set-defaults Resets the variables to the default values
set-default boot-device Resets the variable for the boot disk to the default

value

File download and boot

boot [dev] [kernel] [opts] Boots in multiuser mode
boot -s Boots in single user mode
boot -a Boots interactively
boot -r Boots after changing the hardware configuration
boot -b Boots for diagnostics purposes

Loads a mini kernel. Only available to /root.
boot -v Boots with additional information (verbose mode)
boot net0 Boots from the network

Power off and reset

reset-all Hardware reset
power-off Powers the system off

U41272-J-Z385-3-76 89

Functions of the System Console Software (SCS) Functions of the System Management Console

Diagnostics routines

probe-scsi Probes SCSI devices on the first SCSI controller
probe-scsi-all Probes SCSI devices on all SCSI controllers

Show commands

show-post-results Show POST result
show-devs Show all installed devices (including hardware path)
show-disks Show path of disks
show-tapes Show path of tape devices
show-nets Show path of networks

Showing/setting aliases

devalias Shows aliases
devalias <name> <path> Sets aliases (volatile)
nvalias <name> <path> Sets aliases (permanent)
nvunalias <name> Deletes an alias

Troubleshooting for RED State Exception

.registers
.locals
ctrace

Troubleshooting after the system has hung

sync

Miscellaneous

.version Version of OBP, POST, SCF & RCI
.speed Clock frequency of CPU, UPA and PCI
.enet-addr MAC address on basis of Ethernet adapter
banner Shows boot system information
setenv diag-level <value> Sets diagnostics level (values: off, min, max)
setenv diag-switch? <value> Outputs POST information at the console

(values: true, false; default: false)

90 U41272-J-Z385-3-76

Functions of the System Management Console Functions of the System Console Software (SCS)

4.3.2.2 Starting Solaris

Enter the following command in OBP mode:

{0} ok boot disk
disk here is the alias of the boot disk. The full command with the physical device name of

the boot disk would be, for instance:

{0} ok boot /pci@8c,2000/scsi@1/disk@1,0:a

Sequence of the boot operation:

{0} ok boot ...

Boot programs

Kernel initialization

Init process

rc scripts

Multi user mode

OBP reads the first 16 blocks from the root disk to load the
bootblk program. This can access the directory /root (ufs).

{0} ok boot ...

The program bootblk runs the second boot program
/platform/FJSV,GPUSK/ufsboot and loads it into the

memory. The kernel is then loaded.

Boot programs

The hardware-dependent part of ufsboot is loaded first:
/platform/FJSV,GPUSK/kernel/sparcv9/unix.

Then the hardware-independent part is loaded:

kernel initialization

/platform/FJSV,GPUSK/kernel/sparcv9/genunix.

The kernel generates a user process and starts the process

/sbin/init, which in turn starts other processes when the file
/etc/inittab has been read.

The process /sbin/init starts rc scripts (rc = run control)

Init process

which execute a series of other scripts. These scripts check and
mount file systems, start various processes and execute
system tasks.

Figure 36: Boot process sequence

U41272-J-Z385-3-76 91

Functions of the System Console Software (SCS) Functions of the System Management Console

4.3.3 Monitoring messages

If the system console detects a server error, an error message is displayed in the window
Monitoring Messages.

Double-click the icon in the Application Manager to call up the window Monitoring Messages
(see figure 11 on page 30) or select it from the system console menu (see figure 20 on

page 56):

Figure 37: Monitoring messages: Example for SX system error messages

The error messages are not necessarily displayed in the monitoring window in the

i

order in which they occurred.

92 U41272-J-Z385-3-76

Functions of the System Management Console Time synchronization between SMC and partitions

4.4 Time synchronization between SMC and the partitions

All instances running on an SX server have their own separate time management system,
but all use the same time. This affects:

● The System Management Console

● All partitions (BS2000 and, optionally, Solaris)

● The optional SKP-SR

This also applies to the SX series entry-level models (see section “Time cluster with

external time servers” on page 131).

By default, an NTP cluster is configured under these instances via the administration LAN
of the server. Generally, the SMC is the main NTP server. The quality of this NTP server
(stratum) also determines the quality of the BS2000 time emulated by X2000. Without
additional external timers, the SMC is configured as an NTP server with stratum 5 and the
partitions are configured as NTP clients.

The scale for the quality of the NTP server (stratum) ranges from 0 to 15. The best NTP
server quality (level 1) is found on a server with an official time reference, i.e. with a
connected radio clock which receives an official time signal, or a GPS receiver connected
to receive time. For each server which acts, on the one hand, as an NTP client of a better
server and, on the other hand, as a server for additional clients, the stratum value is raised
(therefore devalued) by 1.

The use of an external timer for BS2000 is basically not required as BS2000 automatically
synchronizes with the Solaris time of the X2000 carrier system. When demands on the
precision of the time reference are more stringent, however, the use of an external timer is
recommended for the SMC. When using VM2000, the exact time is implicitly made available
to all VMs.

For external timers the following options come into question:

● An NTP time server with the quality of an external timer

● A 3920 time server which is connected to the admin LAN

● An SKP-SR with a serially-connected radio clock or a 3920 time server

In addition, BS2000 partitions can be integrated into a computer network where the time of
the members is synchronized (DCE cluster or XCS cluster). If S-servers are also available
in this cluster, the SKP-X of these systems should participate in the NTP cluster of the
SX server. If the cluster comprises several SX servers, they should all participate in the
same NTP cluster.

U41272-J-Z385-3-76 93

Time synchronization between SMC and partitions Functions of the System Management Console

The configuration of the SMC as an NTP server and of the partitions as NTP clients as
supplied is described below. If an external timer (with an official time reference, i.e.
stratum 1) is used, the configuration of the SMC must be changed, so that it operates in
addition to its task as an NTP server for the partitions as an NTP client of this external timer.

In this case, the stratum value of the SMC as a server for the partitions is improved to
value 2. In the BS2000 system of a partition, the system time is displayed as synchronized
with an external reference when the stratum value in Solaris/X2000 is better than 5 (the
default of the SMC). Accordingly, the /SHOW-SYSTEM-INFORMATION command in BS2000
outputs the value SERVER-CONN-EXT-REF in the SYNCHRONISATION field of the SYSTEM-
TIME-PARAMETERS section.

NTP server configuration (System Management Console)

During the installation of the System Management Console, the NTP configuration file was
created for the console with the command partition_setup and the option -n.

The command generates the following contents of the file

/opt/FJSVscsl/etc/ntp.conf:

server 127.127.1.0 prefer
fudge 127.127.1.0 stratum 5
enable auth monitor
driftfile /var/ntp/ntp.drift
statsdir /var/ntp/ntpstats/
filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
filegen clockstats file clockstats type day enable

When using an external time server, the IP address of this server must be made known to
the SMC. The following entry is added to the start of the file:

server xxx.xxx.xxx.xxx prefer # IP-Adresse des NTP-Servers

The first line of the file must also be modified as follows:

server 127.127.1.0

Modifications should be entered only in the NTP configuration file on the SMC. No changes
should be made in the NTP configuration files on the partitions.

To activate modification in the NTP configuration file on the SMC the administrator (with root
authorization) SCS must be restarted (here the NTP daemons in the partitions must not be
restarted):

#/etc/init.d/FJSVscsl restart

94 U41272-J-Z385-3-76

Functions of the System Management Console Time synchronization between SMC and partitions

If the time of the System Management Console is more than 1000 seonds ahead of or
behind the time of a partition the time cannot be automatically synchronized via NTP (start
of the NTP daemon of the partitions or of the NTP client is suppressed). In this case the
times must be synchronized manually.

Information on manual time synchronization is provided in the manual “System Console

Software User’s Guide (SCS)” [7].

NTP client (partitions)

The partitions operate as NTP clients. When installing Solaris using the partition_setup
command (parameter -n), the file /etc/inet/ntp.conf was generated with the following
contents:

server XXX.XXX.XXX.XXX # IP address of the system management console
server 127.127.1.0
fudge 127.127.1.0 stratum 9
enable auth monitor
driftfile /var/ntp/ntp.drift
statsdir /var/ntp/ntpstats/
filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
filegen clockstats file clockstats type day enable

NTP diagnostic commands (for the SMC and the partitions)

ntpq and xntpdc

The ntpq and xntpdc commands supply information on the current status of the NTP
daemon on the home server or on another server in the network. Multiple status changes
and commands can also be triggered.

Sample call

ntpq -p [NTP-server]

Here NTP-server designates the server for which the information is to be output. A list of
the reference sources (peers) used by the specified server is output in tabular form together
with the status information for the individual peers in tabular form (see the following
example):

root@fernandoADM # ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
LOCAL(0) LOCAL(0) 5 l 2 64 377 0.00 0.000 10.03
*sunrise bali.mch.fsc.ne 3 u 33 64 377 0.53 0.594 0.23
root@fernandoADM #

Figure 38: NTP diagnostic command ntpq (example)

U41272-J-Z385-3-76 95

Time synchronization between SMC and partitions Functions of the System Management Console

Meaning of the values in the entry:
– Name or address of the peer

– Reference ID (0.0.0.0 if the reference ID is unknown)
– Stratum value of the peer
– Type of peer (local, unicast, multicast or broadcast)
– Number of seconds which have passed since the last polling cycle
– Polling interval in seconds
– Reachability Register (octal)
– Currently ascertained delay (runtime of the query), offset (time difference between the

reference time and the home system time) and the dispersion (order of magnitude of
the fluctuations) of the peer in milliseconds

The sign in the first column of an entry shows the status of this peer in the time selection
procedure:

* Peer is selected for synchronzation
+ Peer is in the candidate list
Blank Peer was rejected as time source

ntptrace

The ntptrace command provides information on where an NTP server gets its time and
traces the entire chain of NTP servers back to its origin

Sample call

ntptrace [NTP-server]

Here NTP-server designates the server from which the chain is to be traced. If no server
name is specified the chain starts with the local NTP server. Per element of the chain the
information output contains a line with the following entries (see also the example below):

– Name of the NTP server
– Stratum value of the NTP server
– Time offset (in seconds) between the NTP server and the local host
– Synchronization difference (in seconds) of the NTP server
– Reference clock ID (only for servers with stratum value 1)

root@fernandoADM # ntptrace
localhost: stratum 4, offset 0.000034, synch distance 0.03627
sunrise: stratum 3, offset 0.000599, synch distance 0.01469
bali.mch.fsc.net: stratum 2, offset 0.000601, synch distance 0.01335

139.23.202.31: stratum 1, offset 0.000957, synch distance 0.00143, refid 'PPS'
root@fernandoADM #

Figure 39: NTP diagnostic command ntptrace (example)

Further information is provided in the Solaris man pages on these commands.

96 U41272-J-Z385-3-76

Functions of the System Management Console Backing up/restoring the SMC

4.5 Backing up/restoring the SMC

If you create data backups at regular intervals, you can restore your data easily in the event
of a system crash. The following sections describe the procedures for creating backups and
explain which data types must be backed up. A DAT drive is available to the SMC for storing
the backed up data.

SMC data (SCS software, SMC disk, Teleservice data) is saved when the system is

i

The SMC supports two backup procedures. The backup cycle depends on the selected
procedure:

● Backing up the system drive after regular maintenance work or after the location of the

● Backing up the configuration data of the System Console Software (SCS) after the user

commissioned or after changes have been made by service staff.

SMC has been changed

has been registered and/or the configuration data has been changed

WARNING!

!

Recovery measures after drive failures or similar events which require the system
to be recovered should only be carried out by a qualified service engineer.

U41272-J-Z385-3-76 97

Backing up/restoring the SMC Functions of the System Management Console

4.5.1 SCS configuration data

This section describes how to back up and restore the SCS configuration data.

4.5.1.1 Backing up the configuration data of the System Console Software (SCS)

A backup of the configuration data of the System Console Software is of benefit if you wish
to replace an incorrect configuration setting with the old configuration. The System Console
Software includes the commands needed to create the backup. Backing up the configu­ration data is particularly recommended when the configuration of the System Console
Software is to be changed. Approximately 1 to 2 MB of data are backed up during a backup
of this type.

In order to back up the configuration data of the System Console Software, you need a DAT
data cartridge.

Proceed as follows to back up the configuration data of the System Console Software:

1. Log on at the SMC as root.

2. Insert a data cartridge in the DAT drive. Check beforehand that the cartridge is not write-

protected, i.e. that the write-protect tab is set at “writeable”.

3. Enter the following command to start the backup process:

SMC# /opt/FJSVscsl/bin/scslbackup -t /dev/rmt/0

A prompt appears when backup is complete.

4. Press the eject button of the DAT tape drive to remove the data cartridge from the drive.

Then activate write protection by putting the write protection tab of the data cartridge
into the “write-protected” position.

4.5.1.2 Restoring configuration data of the System Console Software

To restore SCS configuration data which has been backed up (see previous section) you
will need the DAT data cartridge on which the data has been backed up.

Proceed as follows to restore the backed up configuration data:

1. Log on at the SMC as root.

2. Switch to the ok prompt by entering the following command.

SMC# /usr/sbin/shutdown -g0 -y -i0

3. Enter the following command to start the system in single-user mode.

ok boot -s

4. Enter the root password to switch to single-user mode.

98 U41272-J-Z385-3-76

Functions of the System Management Console Backing up/restoring the SMC

5. Insert the data cartridge containing the backed up configuration data in the DAT drive.

Check beforehand that the data cartridge is write-protected, i.e. that the write protection
tab is set at “writeable”.

6. Enter the following command to start restoring the configuration data:

SMC# /opt/FJSVscsl/bin/scslrestore -t /dev/rmt/0

7. Initiate a reconfiguration of the system components and then restart the system:

SMC# touch /reconfigure
SMC# /usr/sbin/shutdown -g0 -y -i6

The control panel LAN must be deactivated and then reactivated. To do this, use the

Machine Administration Menu (see figure 21 on page 58):
System Network Administration -> System Network Administration Configuration Tools ->
System Network Activation/Inactivation.

8. Use the device management menu of the System Console Software to restore the

monitoring log created by the device management program (this log involves data which
is automatically saved in the partition at regular intervals).

9. If necessary, check and activate the APC system (see section “Switching the server

on/off on a scheduled basis” on page 66).

10. Press the eject button of the DAT tape drive to remove the data cartridge from the drive.

U41272-J-Z385-3-76 99

Backing up/restoring the SMC Functions of the System Management Console

4.5.2 System drive

4.5.2.1 Backing up the system drive of the SMC

This section describes how to back up offline.
When the system drive is backed up, all data saved on the hard disks which are installed in

the SMC is transferred onto DAT data cartridges.
With this procedure, you can back up the data stored on all hard disks. This procedure is

particularly useful for exchanging a faulty hard disk, since you can transfer all data backed
up on the data cartridges onto the new hard disk. The system then regains the configuration
which was valid at the time the backup was created.

This process, during which the data on all hard disks is written onto data cartridges, takes
approximately one hour. All console functions are deactivated whilst the data is being
saved.

The volume of data to be saved is so large that only DDS4 data cartridges (150 m)

i

To back up the data on the system drive, you will need:
– One DAT data cartridge, DDS4, 150 m
– The CD-ROM (1 of 2) with the Solaris software for the SMC
Proceed as follows to create a backup of the system drive:

1. Log on at the SMC as root.

2. Switch to OBP mode by entering the following command:

3. Insert the Solaris CD-ROM in the CD-ROM drive.

4. Insert a data cartridge in the DAT drive. Check beforehand that the cartridge is not write-

5. Start Solaris in single-user mode from the CD-ROM:

should be used.
Before you start the backup, check the amount of data stored on the hard disk.

SMC# /usr/sbin/shutdown -g0 -y -i0

protected, i.e. that the write protection slider is set at “writeable”.

ok boot cdrom -s

100 U41272-J-Z385-3-76