Parameters KCC

Logical Domains Administration
Document number:
Document issue:
Document status:
Date:
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
External document
Copyright 2012 Kapsch CarrierCom France S.A.S, All Rights Reserved
KAPSCH CONFIDENTIAL
The information contained in this document is the property of Kapsch CarrierCom France S.A.S (in the following
referred to as Kapsch). Except as specifically authorized in writing by Kapsch, the holder of this document shall
keep the information contained herein confidential and shall protect same in whole or in part from disclosure and
dissemination to third parties and use same for evaluation, operation and maintenance purposes only.
The content of this document is provided for information purposes only and is subject to modification. It does not
constitute any representation or warranty from Kapsch as to the content or accuracy of the information contained
herein, including but not limited to the suitability and performance of the product or its intended application.
Kapsch and the Kapsch logo are trademarks of Kapsch and/ or its licensors. All other trademarks are the property
of their owners.
PUBLICATION HISTORY
22/Feb/2012
Issue 05.21 / EN, Standard
PRM12/0000104
15/Feb/2012
PRM12/0000092
07/Feb/2012
PRM11/0003316 PRM11/0003281
19/Jan/2012
PRM11/0003305
20/Dec/2011
PRM11/0003239
07/Dec/2011
PRM11/0003172
28/Nov/2011
PRM11/0003158 PRM11/0002854 PRM11/0003134
24/Nov/2011
PRM11/0003095
10/Nov/2011
PRM11/0003014
31/Oct/2011
PRM11/0002996
28/Sep/2011
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 2/122

PRM11/0002728 PRM11/0002580
21/Sep/2011
PRM11/0002779
13/Sep/2011
PRM11/0002590
10/Aug/2011
PRM11/0001576
PRM11/0000398
04/Jul/2011
PRM11/0001700
14/Jun/2011
PRM11/0000396 PRM11/0001053 PRM11/0000074 PRM11/0000270
25/Jan/2011
PRM10/0000732
17/Dec/2010
PRM10/0000261 PRM10/0000448
23/Nov/2010
PRM10/0000239
01/Nov/2010
PRM10/0000239
14/Sep/2010
Created from 04.01 / EN.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 3/122
CONTENTS
1.
2.
3.
INTRODUCTION ............................................................................................................................7
1.1.
SUBJECT ..................................................................................................................................7
1.2.
SCOPE OF THIS DOCUMENT .......................................................................................................7
1.3.
AUDIENCE FOR THIS DOCUMENT ................................................................................................7
RELATED DOCUMENTS ..............................................................................................................8

2.1.
APPLICABLE DOCUMENTS ..........................................................................................................8
2.2.
REFERENCE DOCUMENTS ..........................................................................................................8
TYPOGRAPHIC CONVENTIONS .................................................................................................9

3.1.
GENERAL CONVENTIONS ...........................................................................................................9
3.1.1
Interactive graphic sessions ............................................................................................9
3.1.2
Interactive terminal sessions ...........................................................................................9
3.2.
4.
SEQUENCE TABLE STRUCTURE ................................................................................................10
GENERAL DESCRIPTION ..........................................................................................................12

4.1.
PLEASE READ CAREFULLY .......................................................................................................12
4.2.
PREREQUISITES ......................................................................................................................12
4.2.1
Human resources ..........................................................................................................12
4.2.2
Requisite hardware .......................................................................................................12
4.2.3
Requisite software .........................................................................................................12
5.
6.
7.
ADMINISTRATION TASK MAP ..................................................................................................14

5.1.
LOGICAL DOMAINS INSTALLATION/CONFIGURATION OVERVIEW ...................................................14
5.2.
REMOTE ACCESS THROUGH SGD SOFTWARE ...........................................................................14
5.3.
TASK MAP...............................................................................................................................15
CONTROL DOMAIN INSTALLATION ........................................................................................17

6.1.
GENERAL PRE-INSTALLATION TASKS ........................................................................................17
6.2.
TARGET HOST HARDWARE CHECK ............................................................................................17
6.3.
STARTING INSTALLATION .........................................................................................................18
CONTROL DOMAIN BACKUP ...................................................................................................20

7.1.
GENERAL DESCRIPTION ...........................................................................................................20
7.1.1
Overview .......................................................................................................................20
7.1.2
Supported media ...........................................................................................................20
7.1.3
Prerequisites .................................................................................................................20
7.1.4
Resources .....................................................................................................................20
7.1.5
Online and offline mode ................................................................................................21
7.1.6
Backup on DVD archiving description ...........................................................................21
7.1.7
Backup on NFS archiving description ...........................................................................21
7.1.8
Interval ...........................................................................................................................21
7.1.9
System impact ...............................................................................................................22
7.2.
PRE-BACKUP TASKS ................................................................................................................23
7.3.
BACKUP ON NFS ....................................................................................................................24
7.3.1
Offline mode ..................................................................................................................24
7.3.2
Online mode ..................................................................................................................25
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 4/122

7.4.
BACKUP ON DVD ....................................................................................................................26
7.4.1
Offline mode ..................................................................................................................26
7.4.2
Online mode ..................................................................................................................27
8.
CONTROL DOMAIN RESTORATION.........................................................................................28

8.1.
OVERVIEW..............................................................................................................................28
8.1.1
Supported media ...........................................................................................................28
8.1.2
Prerequisites .................................................................................................................28
8.1.3
Resources .....................................................................................................................28
8.1.4
Control domain restoration overview ............................................................................28
8.1.5
Interval ...........................................................................................................................29
8.2.
OPERATION DETAILED DESCRIPTION ........................................................................................29
9.
CONTROL DOMAIN REMOVING ...............................................................................................30
10.
CONFIGURING SGD USERS .....................................................................................................31
11.
10.1.
PRELIMINARY OPERATIONS ......................................................................................................31
10.2.
CREATING SGD USER .............................................................................................................31
10.3.
REMOVING SGD USER ............................................................................................................32
10.4.
ADDING LOCAL DOMAINS TO SGD USERS PROFILE ...................................................................32
10.5.
REMOVING LOCAL DOMAINS FROM SGD USERS PROFILE ..........................................................33
10.6.
LIST LOCAL DOMAINS IN SGD USERS PROFILE .........................................................................33
10.7.
CHANGING PASSWORD FOR SGD USER ...................................................................................33
10.8.
FINALIZING OPERATIONS..........................................................................................................34
WORKING WITH THE VIRTUAL WORKSTATION ....................................................................35

11.1.
CONNECTING TO THE VIRTUAL WORKSTATION ...........................................................................35
11.2.
DISCONNECTING FROM THE VIRTUAL WORKSTATION..................................................................36
11.3.
SUSPENDING VIRTUAL WORKSTATION WEB-SESSION .................................................................36
11.4.
RESUMING VIRTUAL WORKSTATION WEB-SESSION.....................................................................36
11.5.
ENTERING OBP MODE ON THE VIRTUAL WORKSTATION .............................................................37
12.
EXPORTING CIUS DVD IMAGES TO THE VIRTUAL WORKSTATION ...................................38
13.
GETTING MAC-ADDRESS FOR THE VIRTUAL WORKSTATION ...........................................39
14.
UPDATING TARGET HOST SYSTEM FIRMWARE VERSION .................................................40
15.
16.
14.1.
UPDATING OBP VERSION FOR T5140 SERVER .........................................................................40
14.2.
UPDATING OBP VERSION FOR T3-2 SERVER ............................................................................41
CONFIGURING/DECONFIGURING DNS CLIENT ON CONTROL DOMAIN ............................42

15.1.
CONFIGURING DNS CLIENT .....................................................................................................42
15.2.
DECONFIGURING DNS CLIENT .................................................................................................42
SSH CONFIGURATION...............................................................................................................43
16.1.
SECURE MODE ACTIVATION .....................................................................................................43
16.2.
CHECKING SSH SERVICE ........................................................................................................43
16.3.
NON-SECURE MODE ACTIVATION ..............................................................................................43

External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 5/122

17.
OPERATION SHEETS.................................................................................................................44
POWERING ON/OFF SERVER AND WORKSTATION ................................................................ 45
CONNECTING/DISCONNECTING TO ILOM SERVICE ............................................................... 47
ENTERING OBP MODE ON SERVER VIA ILOM CONSOLE ....................................................... 50
CHECKING SUN SPARC ENTERPRISE T5140 / ORACLE SPARC T3-2 HARDWARE AND
SETTING OBP PARAMETERS ..................................................................................................... 51
OS SHUTDOWN / REBOOT / RUN LEVEL CHANGE .................................................................. 54
CONFIGURING SGD USERS ....................................................................................................... 56
CONTROL DOMAIN INSTALLATION ........................................................................................... 59
ADDING DISK IMAGES TO THE REPOSITORY .......................................................................... 62
CONTROL DOMAIN REMOVING ................................................................................................. 63
RESET T5140/T3-2 HOST ............................................................................................................ 64
SETTING HARDENED MODE ON THE CONTROL DOMAIN ...................................................... 65
EXPORTING CIUS DVD IMAGE FROM THE REPOSITORY ....................................................... 66
CONNECTING ETHERNET CABLES OF VIRTUAL WORKSTATIONS ON T5140 SERVER ...... 67
WORKING WITH THE HOST VIA SGD ........................................................................................ 69
CONNECTING/DISCONNECTING TO THE VIRTUAL WORKSTATION CONSOLE ................... 78
VIRTUAL WORKSTATION MANAGEMENT ................................................................................. 80
GETTING VIRTUAL WORKSTATION MAC-ADDRESS ................................................................ 81
UPDATE OBP VERSION FOR T5140 SERVER........................................................................ 82
CONNECTING/DISCONNECTING TO THE HOST WITH TELNET .............................................. 87
CONTROL DOMAIN BACKUP ON DVD OPERATIONS ............................................................... 88
CONTROL DOMAIN BACKUP ON NFS OPERATIONS ............................................................... 93
CHECK FILE SYSTEM FULL ........................................................................................................ 95
BLANKING DVD-RW MEDIA......................................................................................................... 96
CONTROL DOMAIN RESTORATION ........................................................................................... 97
STOPPING OMC-R APPLICATION ............................................................................................ 102
CONFIGURE/DECONFIGURE DNS CLIENT ON CONTROL DOMAIN ..................................... 103
CONFIGURING SSH SERVICE ON CONTROL DOMAIN .......................................................... 104
UPDATE OBP VERSION FOR T3-2 SERVER ............................................................................ 105
CONNECTING ETHERNET CABLES OF VIRTUAL WORKSTATIONS ON T3-2 SERVER ....... 108
RESTARTING OMC-R APPLICATION ........................................................................................ 110
SETTING OPEN BOOT PROM PARAMETER ............................................................................ 111
SETTING OS HARDENED MODE ............................................................................................ 112
18.
ANNEXES ..................................................................................................................................115
SUPPORTED TIMEZONES......................................................................................................... 116
19.
ABBREVIATIONS AND DEFINITIONS .....................................................................................121

19.1.
ABBREVIATIONS ....................................................................................................................121
19.2.
DEFINITIONS .........................................................................................................................121
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 6/122
1.
INTRODUCTION
1.1.
SUBJECT
The document describes how to perform main administration tasks for logical domains
(LDoms) with SGD software.
A logical domain is a virtual machine comprised of a discrete logical grouping of
resources. Logical domain has its own operating system and identity within a single
computer system.
Each logical domain can be created, destroyed, reconfigured, and rebooted
independently, without requiring you to powercycle the server. You can run a variety of
applications software in different logical domains and keep them independent for
performance and security purposes.
Each logical domain is only permitted to observe and interact with those server
resources that are made available to it by the control domain. The control domain
enforces the partitioning of the server's resources and provides limited subsets to
multiple operating system environments. This partitioning and provisioning is the
fundamental mechanism for creating logical domains. Non-control logical domains are
also called virtual workstations.
Each logical domain can be managed as an entirely independent machine with its own
resources, such as:
Kernel, patches, and tuning parameters
User accounts and administrators
Disks
Network interfaces, MAC addresses, and IP addresses
For detailed information about logical domains see [R6] document.
Oracle Secure Global Desktop software (SGD) provides remote access to desktop
applications on logical domains via a web-browser (see [R4] document for details).
For detailed information about available administration tasks described at the current
document, see 5. Administration task map chapter.
1.2.
SCOPE OF THIS DOCUMENT

This procedure is applicable for V18.0 PC4 OMC-R release.
This procedure applies to hosts with the following hardware architectures:
Sun SPARC Enterprise T5140
Oracle SPARC T3-2
The document does not cover physical deployment of the server. For this purpose
refer to [A1] document.
1.3.
AUDIENCE FOR THIS DOCUMENT

This document is destined to be used by persons who operate with logical domains
(hereinafter called the operator).
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 7/122
2.
RELATED DOCUMENTS
2.1.
APPLICABLE DOCUMENTS
2.2.
[A1]
DS/OMC/APP/000001 OMC-R OEM equipment installation procedure
[A2]
DS/OMC/APP/000003 OMC-R Software Installation Procedure
[A3]
DS/OMC/APP/000016 OMC-R Preventive Maintenance Backup
[A4]
DS/OMC/APP/000017 OMC-R System Global Restoration
[A5]
DS/OMC/APP/000019 OMC-R customization parameter notebook
[A6]
DS/OMC/APP/020095 OMC-R Post-installation Configuration Procedure
REFERENCE DOCUMENTS
[R1]
PE/COM/INF/0012430 100 Mbps LAN for the OMC-R Mandatory in V15.0

and further releases
[R2]
PE/OMC/INF/000066
OMC-R Product catalog
[R3]
820-6687
Oracle Secure Global Desktop 4.5 Release Notes
[R4]
820-6690
Oracle Secure Global Desktop 4.5 User Guide
[R5]
820-6689
Oracle Secure Global Desktop 4.5 Administration

Guide
[R6]
820-7253
Logical Domains 1.2 Administration Guide
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 8/122
3.
TYPOGRAPHIC CONVENTIONS
3.1.
GENERAL CONVENTIONS
Words in italic style (italic) represent a parameter to substitute for its value.
An inscription as the one below indicates on which computer the recommended

actions shall be performed:
ON A LOCAL OMC-R WORKSTATION:

Conditional commands are highlighted with the following syntax:
For each OMC-R workstation:
{
.....
}
or:
If not already done, stop the OMC-R application.
3.1.1 INTERACTIVE GRAPHIC SESSIONS

The graphic interactive commands are described with the following syntax:
Convention used
Meaning
GOTO Title
Go to the window named "Title"
SELECT
Click with the mouse on the buttons or options

named "Save", then "OK".
Save - OK
SELECT_OBJ
omc
SET State = locked
T2 = 30s
Select the object omc
CLOSE
Close the window named "Title"
Title
Enter with the keyboard the values of the

parameters
3.1.2 INTERACTIVE TERMINAL SESSIONS

An interactive session on a terminal can be obtained using two methods:
- Choosing the "Access to Terminal Console" option of the background menu on the
server or the station,
- Open a remote connection to the server or the station from a shell window on any
other host, using the telnet or rlogin command.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 9/122

An interactive session on a terminal (line terminal or Command Tool window) is
described with the following syntax:
Convention used
Meaning
Note: some text
A comment or note that deserves special attention.
Courier New
The Courier New font represents the characters of a terminal

session.
Lines, commands or parameters entered from the keyboard are
in bold style.
The italic style denotes variable output. Words in italic are to be
substituted by actually displayed values.
Input parameters expected to be substituted by proper values
appear in italic and bold style.
Bold
Italic
italic-bold
Press the ENTER key.

[STOP],[a]
The STOP and a key should be pressed simultaneously.
..........
Dots represent a number of skipped lines.
The scissors symbol indicates that the command to be typed is

truncated and continues on the next line.
% or (user) %
C shell prompt.
$ or (user) $
Bourne and Korn shell prompt.
# or (root) #
Root super-user prompt in any shell.
Terminal session sample:

Type at the command prompt of the omc account shell:
/ (omc) % cd my_directory
my_directory (omc) % ls
a.out
i_am_a_short_file_with_a_really_i_mean_really
_no_but_unbelievably_ long_name
........
toto.o
my_directory (omc) % vi my_file
my_directory (omc) %
The typographic conventions of a terminal session are also used to display the content
of a UNIX file.
A shown output of commands may be different depending on your configuration,
Solaris OS and tools version. The represented result of executed commands is been
shown as example only. An expected data in output is marked as bold if needed.
3.2.
SEQUENCE TABLE STRUCTURE

Sequence tables serve to describe what operation is performed at each procedure
step, present the order of individual step operations, give time estimates and mark the
step outcome.
For each major step of the procedure, a sequence table lists operation steps to
perform. Each operation step is described completely in the sheet referenced by its
page number.
The operation detailed in an operation sheet may be performed at different stages of
the procedure and in different contexts; for this reason, a set of input parameters for
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 10/122

the sheet operation serves to indicate the pertinent context.
A sequence table provides for each operation step the time required to perform it. The
time indicated for an operation step is maximum elapsed time and corresponds to a
nominal hardware configuration. A question mark ? specified means that the time
required for operation step is unknown. An asterisk * is used when the time indicated
may change depending on the different conditions like: a hardware platform, a network
bandwidth, data drive used for backup/restore, customer data, a size of database and
so on.
Since the sheets are not in the execution order and can be executed several
times, the sequence tables should be considered as the reference guide during
the procedure.
A sequence table has the following format:
Comment indicating
the status at this stage
of the major step
Step | Operation description
(Total 315 min)
min Sheet OK /
page NOK
Input Parameters
STATUS COMMENT
S1
Description of the operation 1
30
12
OK
Parameter1 = value
Parameter2 : explanations
S2
280
14
OK
S3
17
OK
Parameter1 = value
Name and value of input parameters of the sheet (optional
or none for no argument)
Maximum elapsed time of the operation step

Sheet page number
Result of the operation,
filled in by the operator
Each time an operation has been performed, the operator should note the result in the
OK / NOK column.
If the result is OK , the next operation is described in the following line of the table.
If the result is NOK , the procedure cannot be continued without any investigation.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 11/122
4.
GENERAL DESCRIPTION
4.1.
PLEASE READ CAREFULLY

Though the utmost care was taken to preclude any chance of undesirable events
during the installation procedure, it is impossible to foresee all probable happenings.
Therefore, if you encounter a problem or a situation that the procedure does not cover
in an explicit and accurate manner, call for assistance.
Before commencing on this procedure, ask your support if any special actions
(workarounds, patches, etc) need to be undertaken prior to and/or after the
procedure.
4.2.
PREREQUISITES
4.2.1 HUMAN RESOURCES

It takes one person to perform logical domain administration procedures.
The operator must have a good working knowledge of the OMC-R and Solaris
operating environment.
4.2.2 REQUISITE HARDWARE

The nominal architecture for control domain is Sun SPARC Enterprise T5140 /
Oracle SPARC T3-2.
Before starting any procedures with control domain, complete physical deployment of
target host in accordance with the [A1] document.
The LAN and XLAN bandwidth must be compliant to [R1] document.
4.2.3 REQUISITE SOFTWARE

You need the SGD software located on DVD to install control domain.
Also the CIUS software, located on DVDs containing OMC-R software, is required for
creating CIUS DVD images repository.
A mandatory requirement is to have the support of Java technology and
JavaScript enabled in the web browser used to perform the initial connection to the
SGD server. For detailed information about Java technology requirements refer to
[R4] and [R5] document.
Note: If Internet Explorer on Microsoft Windows platforms is used, it is necessary to
add the SGD server to the list of Trusted Sites in Internet Explorer's Security Settings
before the SGD client can be automatically downloaded and installed.
The SGD client can operate in two modes and it is up to the operator which mode will
be used, there is no difference for the SGD server:
Webtop mode
The SGD client uses a special web page, called a webtop, to display the
controls for SGD. This is the default mode.
Integrated mode
The SGD client displays the controls for SGD in the desktop Start or Launch
menu. Depending on other configuration factors, a web browser might only be
needed for initial authentication, and for determining proxy server settings.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 12/122

In order to switch between these two modes an operator should modify his SGD
profile as described at [R4] document.
Supported client operating systems and browsers are:
Supported Client Platform
Supported Web Browsers
Integrated Mode Support
Microsoft Windows Vista

(Intel x86 32-bit)
Internet Explorer 7.0+

Mozilla 1.5+
Mozilla Firefox 2.0+
Microsoft Windows Start

Menu
Microsoft Windows XP Professional

(Intel x86 32-bit)
Internet Explorer 6.0+, 7.0+

Mozilla 1.5+

Menu
Microsoft Windows 2000

Professional
Internet Explorer 6.0+, 7.0+

Mozilla 1.5+

Menu
Solaris 8 or later OS on SPARC

platforms
Mozilla 1.5+
Sun Java Desktop System

Launch Menu
Solaris 10 OS Trusted Extensions on

SPARC platforms
Mozilla 1.5+
Not supported
Solaris 10 OS on x86 platforms
Mozilla 1.5+
Sun Java Desktop System

Launch Menu
Mac OS X 10.4 or later
Safari 2.0+
Not supported
Fedora Linux 7 (Intel x86 32-bit)
Mozilla 1.5+
Gnome or KDE Start Menu
Red Hat Desktop version 4
Mozilla 1.5+
SUSE Linux Enterprise Desktop 10
Mozilla 1.5+
Ubuntu 7.04
Mozilla 1.5+
Gnome Start Menu
This list is defined by SGD requirements and other operating systems or browsers are
not supported (see [R3] document).
To allow remote secure connection to the SGD server the following ports must be
opened on a firewall if it is present:
Source
Client
Destination
SGD server
Port
Protocol
5307
TCP
Purpose
SSL-based secure, encrypted AIP connections.
Used for control and application display
updates.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 13/122
5.
ADMINISTRATION TASK MAP
5.1.
LOGICAL DOMAINS INSTALLATION/CONFIGURATION

OVERVIEW
The goal of this procedure is to describe how to install/configure target host as a
platform for CIUS and OMC-R workstations of the same or different versions.
This possibility is provided through Logical Domains (LDoms) Sun mechanism.
The following logical domains are configured during installation for operators use:
Control domain
Control domain is a primary logical domain, which manages other logical domains
and allocates virtual resources to other domains through the Logical Domains
Manager. There is only one control domain per server.
Reboot of the control domain means reboot of the server and emergency reboot of
all other domains as a result.
Control domain uses ports nxge0 and nxge4 on T5140 server and igb0 and nxge0
on T3-2 server to connect to network. Redundancy is maintained by means of IPMP.
IP address of the control domain is actually IP of the server.
Virtual workstations
Virtual workstation is a logical domain that can have its own operating system and
identity within a single computer system. Logical domains are managed by control
domain.
Each virtual workstation can be rebooted independently that doesnt require the
server reboot.
Each virtual workstation can be installed as CIUS or OMC-R workstation with STATX
or STATXDATAEXP role at any version. IP address of every virtual workstation must
be unique within network and different from the control domain one.
5.2.
REMOTE ACCESS THROUG H SGD SOFTW ARE

The desktop application (CDE) of CIUS or OMC-R workstations, installed on logical
domains, can be accessed through SGD software via a web-browser.
SGD user accounts must be created on control domain for every CIUS/OMC-R virtual
workstation.
Note: One SGD session only can be opened under one account at the same time.
The number of users that can log in or have running applications is limited by the
installed license keys. Several SGD users can be declared for each virtual workstation
and one user can work with several domains, but not at the same time.
Besides SGD, the following ways to remotely connect to CIUS/OMC-R virtual
workstations are possible:
1. Connection to the CIUS/OMC-R workstation console through control domain.
2. Remote shell utilities/interfaces (telnet, ssh and etc.).
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 14/122
5.3.
TASK MAP
The following task map is an overview of the steps necessary to manage the logical
domains configuration. Use this task map to identify all of the chapters that you need to
perform for SGD administration.
Note: To perform backup of all logical domains you must backup control domain and all
virtual workstations.
Task
Description
For instructions, go to
Control domain installation

Chapter 6, on page 17
Control domain installation

Control domain
reinstallation
Removing the previous

control domain
Installation of the new control

domain
Control domain backup

Control domain backup on
NFS storage
Control domain backup on

DVD disks
Pre-backup tasks
Chapter 7.2, on page 23
Backup on NFS
Pre-backup tasks
Backup on DVD
Control domain restoration

from NFS storage

from DVD disks
SGD administration
Configuring SGD users
Creating the user

Removing the user

External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 15/122
Adding local domains to SGD

users profile

Removing local domains from

SGD users profile

List local domains in SGD

users profile

Changing the password

Working with the virtual
workstation via SGD
Connecting to the virtual

workstation
Disconnecting from the virtual

workstation
Suspending virtual
workstation web-session
Resuming virtual workstation

web-session
Other tasks
Entering OBP mode on the
virtual workstation
Exporting CIUS DVD

images to the virtual
workstation
Getting MAC-address for

the virtual workstation
Updating server system

firmware version
Configuring/Deconfiguring
DNS client on control
domain
Configuring/Deconfiguring
SSH service on control
domain
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 16/122
6.
CONTROL DOMAIN INSTALLATION
6.1.
GENERAL PRE-INSTALLATION TASKS

You can perform prerequisites operations several days before the installation.
If the control domain has already been installed on the target host, it is
necessary to remove it from the host according to the 9. Control domain
removing chapter.
If the control domain was removed prior to the installation, virtual workstations
disks contents will remain the same as before control domain removal.
(Total 4 min)
min Sheet
page
OK /
NOK
Input Parameters
BEGINNING OF PRE-INSTALLATION TASKS

S1
Check installation prerequisites (refer to section 4.2)
S2
Connect Ethernet cables to the target host
12
For T5140
67
For T3-2
108
END OF PRE-INSTALLATION TASKS
6.2.
TARGET HOST HARDWARE CHECK
(Total 22 min)
min Sheet
page
OK /
NOK
Input Parameters
TARGET HOST IS PHYSICALLY INSTALLED

S3
If not already done, power on the target host
45
47
10
50
51
action = on
S4
If not yet done, open the ILOM console

action = connect
target = ILOM
S5
Enter the OBP mode on the target host
S6
Check the target host hardware and set OBP parameters
TARGET HOST IS CORRECTLY INSTALLED
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 17/122
6.3.
STARTING INSTALLATION
This chapter details how to install the control domain on the target host.
Note: The list of available values for the timezone parameter is specified at the
Supported timezones sheet (page 116).
(Total 95 + (*) min))
min Sheet
page
OK /
NOK
Input Parameters
TARGET HOST IS READY FOR CONTROL DOMAIN INSTALLATION

S7
Install control domain on the target host

IP_address:
hostname:
netmask:
timezone:
router_IP_address:
(*)
59
refer to [A5]
refer to [A5]
refer to [A5]
refer to [A5]
refer to [A5]
S8
If necessary, setup routing on the control domain
S9
Set the hardened mode on the control domain
(**)
10
65
80
78
111
78
80
IpAddr_1 = first IP address

IpAddr_2 = second IP address
S10 If you are performing Control domain reinstallation procedure,
perform the steps S11-S15 for each virtual workstation
Otherwise, proceed to the S16
S11 Start the virtual workstation
action = start
ldom_num : target virtual workstation number
S12 Connect to the virtual workstation console
action = connect
S13 Set auto-boot? variable in OBP to true for the virtual workstation
parameter = auto-boot?
value = true
S14 Close the virtual workstation console
action = disconnect
S15 Stop the virtual workstation
action = stop
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 18/122

S16 Disconnect from target host system console
47
action = disconnect
CONTROL DOMAIN IS INSTALLED AND CONFIGURED ON THE TARGET HOST

VIRTUAL WORKSTATIONS ARE COMPLETELY INSTALLED AND READY TO USE
(*) - The duration may vary and depends on speed of DVD drive and DVD disks quality.
(**) - Contact with IT service to define routing on the control domain.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 19/122
7.
CONTROL DOMAIN BACKUP
7.1.
GENERAL DESCRIPTION
7.1.1 OVERVIEW
The aim of this backup is to save the control domain file systems. This backup does
not save the storage file system or file systems of the OMC-R workstations installed
on the virtual workstations. To backup virtual workstations use [A3] procedure.
Any files located on the /storage file system will be lost after the control domain
restoration.
The file systems dedicated to the OMC-R workstations are not concerned by
this type of backup. This means that any OMC-R workstations suffering a data
loss need to be restored separately with help of [A4] procedure after the control
domain restoration.
Note: The following files defined in internal exclude list are not saved by backup tool:
All core files present on the disk
All messages.* files from directory /var/adm
Directory /var/crash
7.1.2 SUPPORTED MEDIA

Backup of the control domain can be performed on NFS server or on DVD disks.
7.1.3 PREREQUISITES
The following prerequisites:
ILOM password must be known.
The passwords for root and croot users must be known.
In case of NFS backup, the NFS server has to be configured and running.
7.1.4 RESOURCES
The following hardware and human resources are required:
One technician, familiar with the UNIX system.
In case of backup on NFS, configured NFS server with shared directory to

store backups.
In case of backup on DVD:

o
Certain number of DVD disks is required to back up file systems.

Generally 1 or 2 DVD disks are required per control domain.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 20/122

However, the real quantity of the disks depends on size of the file
systems.
Please use the following types of DVD media:
DVD+RW 4x or higher
DVD-RW 4x or higher
DVD+R 4x-8x
DVD-R 4x-8x
Other types of DVD cannot be used.
7.1.5 ONLINE AND OFFLINE MODE

Control domain backup can be performed in the online and the offline mode.
The online mode means that the OMC-R workstations installed on virtual workstations
can be running during the backup. In this case, there will be no downtime, and the
operating system on control domain will stay in multi-user mode.
Note: During the online backup the performance of operating system on control
domain may degrade.
The offline backup mode means that the control domain must be rebooted to single
user mode and all the OMC-R workstations configured on the virtual workstations will
be stopped.
7.1.6 BACKUP ON DVD ARCHIVING DESCRIPTION

The backup must be performed by the UNIX user.
The backup includes two main steps: creating images and burning images.
The creating images step must be performed by the UNIX root user. If offline backup
is performed, the operating system will be put in the single-user mode to create DVD
images. Otherwise if backup is performed in the online mode the system will remain in
the multi-user mode.
The burning images step is performed in multi-user mode and does not require the
OMC-R to be stopped.
7.1.7 BACKUP ON NFS ARCHIVING DESCRIPTION

The backup must be performed by the UNIX user.
The backup consists of saving control domain system partitions (/, /home, /var), disks
configuration information and disks partitioning.
7.1.8 INTERVAL
Control domain backup should be performed before major changes in control domain
configurations, for example:
After control domain installation
Before and after control domain software update
Before and after disk substitution on a control domain

External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 21/122
7.1.9 SYSTEM IMPACT

OMC-R workstations installed on the virtual workstation will be stopped in case
of offline backup.
The operation can last up to several hours depending on the size of data to be saved,
the type of media used being in case of backup on DVD or the NFS server
performance and network throughput in case of backup on NFS.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 22/122
7.2.
PRE-BACKUP TASKS
This chapter describes operations made before backup.
The pre-backup tasks can be run out the day before the maintenance backup.
(Total 3 + (*) + (**) min))
min Sheet
page
OK /
NOK
Input Parameters
BEGINNING OF PRE-BACKUP TASKS

S1
Check if a file system is full on control domain
S2
If you are going to perform DVD backup, carry out estimation of the
backup data size
95
(*)
88
(**)
96
step = estimation
S3
If you are going to perform DVD backup and use DVD-RW disks, blank
them
END OF PRE-BACKUP TASKS

(*) Estimation of the backup size can last depending on the size of data to be saved and contents of
exclude and include lists.
(**) The time necessary to blank DVD-RW disks depends on the amount of them.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 23/122
7.3.
BACKUP ON NFS
This chapter describes how to back up the control domain to the NFS server storage.
7.3.1 OFFLINE MODE

This chapter describes how to perform the NFS backup in the offline mode.
During the backup the OMC-R workstations installed on virtual workstations will
be stopped and the operating system on a control domain will be put in single
user mode.
(Total 23 + (*) min))
min Sheet
page
OK /
NOK
Input Parameters
TARGET HOST IS READY FOR BACK UP

S1
Stop OMC-R application on every workstation installed on virtual

workstations of the target host
102
S2
If not yet done, open the target host system console
47
54
(*)
93
54
10
110
action = connect
target = system console
S3
Boot the operating system in the single-user mode

run_level = s
S4
Perform the backup on the target host

mode = offline
NFS_server_IP: IP address of NFS server
share: shared directory name on NFS server
S5
Reboot the operating system of the target host

run_level = 6
S6
Restart the OMC-R application on every workstation installed on

virtual workstations of the target host
args = -S
THE BACKUP IS COMPLETE AND THE TARGET HOST IS IN MULTI-USER MODE

(*)The backup can last up to several hours depending on the size of data to be saved, network throughput
and NFS server performance.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 24/122
7.3.2 ONLINE MODE

This chapter describes how to perform the NFS backup in the online mode. During the
backup the OMC-R workstations installed on virtual workstations are up and running.
(Total (*) min))
min Sheet
page
OK /
NOK
Input Parameters
TARGET HOST IS READY FOR BACKUP

S1
Perform the backup on the target host
(*)
93
mode = online

(*)The backup can last up to several hours depending on the size of data to be saved, network throughput
and NFS server performance.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 25/122
7.4.
BACKUP ON DVD
This chapter describes all steps necessary to backup control domain on DVD.
The three main steps to perform a backup are:
- Estimation of the backup data size
- Creation of backup DVD images
- Burning of backup DVD images
Backup DVD images are created in the /storage/BackupDVD/hostname (where
hostname is the name of the local machine) directory (named the work directory
hereafter) therefore, this directory must have enough free space to store the images.
The amount of free space needs to be not less than 4.37 * (X+1) Gb (where X is an
estimated number of DVD disks, which can be known at step S2 Estimation of the
backup data size of 7.2 Pre-backup tasks chapter).
The backup can be performed in the online or offline mode.
7.4.1 OFFLINE MODE

This chapter describes how to perform the backup in the offline mode.
During the backup the OMC-R workstations installed on virtual workstations will
be stopped and the operating system on a control domain will be put in single
user mode.
(Total 23 + (*) + (**) min))
min Sheet
page
OK /
NOK
Input Parameters
TARGET HOST IS READY FOR BACK UP

S1

102
S2
If not yet done, open the target system console
47
54
(*)
88
54
action = connect
S3
Boot the operating system in the single-user mode

run_level = s
S4
Create backup DVD images

mode = offline
step = images_creation
S5
Reboot the operating system of the target host

run_level = 6
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 26/122
THE TARGET HOST IS IN MULTI-USER MODE

S6
Burn backup DVD images
(**)
88
10
110
step = burning
S7
Restart the OMC-R application on every workstation installed on

virtual workstations of the target host
args = -S

(*) The backup can last up to several hours depending on the size of data to be saved.
(**) It takes about 20 minutes to burn 1 DVD disk (+20 minutes for each disk to verify it).
7.4.2 ONLINE MODE

This chapter describes how to perform the backup in the online mode. During the
backup the OMC-R workstations installed on virtual workstations are up and running.
(Total (*) + (**) min))
min Sheet
page
OK /
NOK
Input Parameters
TARGET HOST IS READY FOR BACKUP

S1
Create backup DVD images
(*)
88
(**)
88
mode = online
step = images_creation
S2
Burn backup DVD images

step = burning

(*) The backup can last up to several hours depending on the size of data to be saved.
(**) It takes about 20 minutes to burn 1 DVD disk (+20 minutes for each disk to verify it).
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 27/122
8.
CONTROL DOMAIN RESTORATION
8.1.
OVERVIEW
The aim of these actions is to restore the control domain file systems.
Any files located on the /storage file system will be lost after the control domain
restoration.
Virtual workstation file systems are left intact during restoration, so if virtual
workstation file system is corrupted, it is necessary to perform the OMC-R
workstation restoration on corresponding virtual workstation with help of [A4]
procedure.
8.1.1 SUPPORTED MEDIA

Control domain restoration can be performed from NFS server or from DVD disks.
8.1.2 PREREQUISITES
The following prerequisites:
ILOM password must be known.
The passwords for root and croot users must be known.
In case of restoration from NFS, the NFS server has to be configured and
running.
8.1.3 RESOURCES
The following hardware and human resources are required:
One technician, familiar with the UNIX system.
To boot up a host before file system restoration a bootable media (Solaris

boot CD or SGD DVD) is required.
In case of NFS restoration, configured NFS server containing backup data.
In case of restoration from DVD, DVD disks containing backup data.
8.1.4 CONTROL DOMAIN RESTORATION OVERVIEW

The following operations must be performed for a control domain restoration:
Control domain file systems restoration from NFS server or DVD disks.
Recreating CIUS images repository.
If any installed OMC-R workstations are malfunctioning, file systems

restoration on this workstation.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 28/122
8.1.5 INTERVAL
Restoration procedure may be used after a major damage (unsuccessful software
update, system hardware failure, faulty boot disk ) in order to restore a control
domain.
8.2.
OPERATION DETAILED DESCRIPTION
(Total 12 + (*) min)
min Sheet OK /
page NOK
Input Parameters
SOLARIS MAY BE RUNNING OR NOT ON THE TARGET HOST

S1

102
S2
47
54
(*)
97
(*)
97
47
action = connect
S3
If not yet done, shut down the operating system of the target host
run_level = 0
S4
Restore control domain on target host:

from an NFS server
media = nfs
IP_address: IP address of restored computer
Netmask: Valid network mask of computer
Router_IP: Valid IP address of network router
from a DVD
media = dvd
S5
Disconnect from the target host system console

action = disconnect
CONTROL DOMAIN IS RESTORED ON THE TARGET HOST

(*) The restoration can last up to several hours depending on the size of data to be restored and the
quality of the DVD disks being used in case of restoration from DVD or network throughput and NFS
server performance in case of restoration from NFS.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 29/122
9.
CONTROL DOMAIN REMOVING

This chapter details how to remove the control domain from the target host.
The chapter is applicable for the Control domain reinstallation procedure only.
For details how to perform the reinstallation procedure refer to the
5.Administration task map chapter.
Control domain removing stops all the virtual workstations and makes them
inaccessible but it does not change the virtual workstations disks contents. Thus
the virtual workstations can be re-started after the control domain is installed
again.
(Total 45 min)
min Sheet
page
OK /
NOK
Input Parameters
CONTROL DOMAIN IS AVAILABLE

S1

102
S2
47
63
20
54
47
15
64
47
action = connect
S3
Remove the control domain from the target host
S4
Shutdown the operating system of the target host

run_level = 0
S5
If not yet done, open the ILOM console

action = connect
target = ILOM
S6
Reset the target host
S7
Disconnect from target host system console

action = disconnect
CONTROL DOMAIN IS REMOVED
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 30/122
10. CONFIGURING SGD USERS

It is necessary to create SGD user to operate with any logical domain via SGD.
The SGD user associates with the users SGD session, their application sessions, and
their entries in the application server password cache.
The chapter describes how to perform the following operations:
Creating SGD user
Removing SGD user
Adding local domains to SGD users profile
Removing local domains from SGD users profile
Getting a list of local domains in SGD users profile
Changing password for SGD user
Note: For detailed information about SGD users administration refer to [R5] document.
10.1. PRELIMINARY OPERATIONS

(Total 2 min)
min Sheet
page
OK /
NOK
Input Parameters

S1
If not yet done, open a telnet session to the control domain
87
action = connect
host = IP address of the control domain
username = root
END OF PRELIMINARY OPERATIONS
10.2. CREATING SGD USER

(Total 4 + (*) min)
min Sheet
page
OK /
NOK
Input Parameters

S1
If OS hardened mode is activated on the target virtual workstation,

deactivate it
S2
If console is opened on target virtual workstation, close it
(*)
[A6]
78
action = disconnect
ldom_num = target virtual workstation number
OS HARDENED MODE IS NOT ACTIVATED ON TARGET VIRTUAL

WORKSTATION
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 31/122

S3
Create SGD user
56
(*)
[A6]
action = create
user_id = user ID
user_name = user name
user_passwd = user password
domain_name = virtual workstation name
S4
If OS hardened mode was deactivated on the target virtual

workstation, resume it
SGD USER IS CREATED

(*) - Refer to corresponding document to get info how much time it takes.
10.3. REMOVING SGD USER

(Total 2 min)
min Sheet
page
OK /
NOK
Input Parameters

S1
Remove SGD user
56
action = remove
SGD USER IS REMOVED
10.4. ADDING LOCAL DOMAINS TO SGD USERS PROFILE

(Total 3 + (*) min)
min Sheet
page
OK /
NOK
Input Parameters

S1
If OS hardened mode is activated on the target virtual workstation,

deactivate it
S2
If console is opened on target virtual workstation, close it
(*)
[A6]
78
action = disconnect
OS HARDENED MODE IS NOT ACTIVATED ON TARGET VIRTUAL

WORKSTATION
S3
Add local domains to SGD users profile
56
action = bind
domain_name = local domains list, separated by comma
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 32/122

S4
If OS hardened mode was deactivated on the target virtual

workstation, resume it
(*)
[A6]
SGD USER IS CREATED

(*) - Refer to corresponding document to get info how much time it takes.
10.5. REMOVING LOCAL DOMAI NS FROM SGD USERS

PROFILE
(Total 2 min)
min Sheet
page
OK /
NOK
Input Parameters

S1
Remove local domains from SGD users profile
56
action = unbind
domain_name = local domains list, separated by comma
SGD USER IS REMOVED
10.6. LIST LOCAL DOMAINS IN SGD USERS PROFILE

(Total 2 min)
min Sheet
page
OK /
NOK
Input Parameters

S1
Get a list of local domains in SGD users profile
56
action = list
10.7. CHANGING PASSWORD FOR SGD USER

(Total 1 min)
min Sheet
page
OK /
NOK
Input Parameters

S1
Change password for SGD user
56
action = change password

user_passwd = new password for SGD user
PASSWORD IS CHANGED
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 33/122
10.8. FINALIZING OPERATIONS

(Total 1 min)
min Sheet
page
OK /
NOK
Input Parameters

S1
Close the control domain telnet session (if it was opened during on
step S1 of chapter 10.1 Preliminary operations on page 31)
87
action = disconnect
END OF FINALIZING OPERATIONS
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 34/122
11. WORKING WITH THE VIRTUAL WORKSTATION

The chapter describes how to work with SGD in webtop mode. In this mode the SGD
client uses a special web page, called a webtop, to display the controls for SGD. This is
the default mode.
The following operations are described in the chapter:
Connecting to the virtual workstation with a web-browser
Disconnecting from the virtual workstation web-session
Suspending the virtual workstation web-session
Resuming the virtual workstation web-session
Some applications can be configured to keep running, even when they are not
displayed. These are resumable applications. To close an applications window
without ending the application, you suspend the application. To display the window
again and start using the application, you resume the application.
Note: For detailed information about working with the virtual workstation via SGD refer
to [R5] document
11.1. CONNECTING TO THE VIRTUAL WORKSTATION

This chapter details how to connect to the virtual workstation via SGD with a webbrowser. The list of supported web-browsers is described at 4.2.3. Requisite
software chapter.
(Total 13 min)
min Sheet
page
OK /
NOK
Input Parameters
THE CONTROL DOMAIN IS AVAILABLE.

THE VIRTUAL WORKSTATION IS INSTALLED
S1
If not yet done, create SGD user
S2
Connect to the virtual workstation with a web-browser
31
10
69
action = connect
SGD_IP_address : IP address of the control domain
SGD_user : SGD user name
SGD_user_password : password of the user
Unix_user = root
Unix_user_password : root password
THE VIRTUAL WORKSTATION DESKTOP IS AVAILABLE
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 35/122
11.2. DISCONNECTING FROM THE VIRTUAL WORKSTATION

(Total 10 min)
min Sheet
page
OK /
NOK
Input Parameters
THE CONTROL DOMAIN WEB-SESSION IS AVAILABLE

S1
Disconnect from the virtual workstation web-session
10
69
action = disconnect
SGD_IP_address = IP address of the control domain
THE VIRTUAL WORKSTATION WEB-SESSION IS CLOSED
11.3. SUSPENDING VIRTUAL WORKSTATION WEBSESSION

(Total 10 min)
min Sheet
page
OK /
NOK
Input Parameters
THE CONTROL DOMAIN WEB-SESSION IS AVAILABLE

S1
Suspend virtual workstation web-session
10
69
action = suspend
THE VIRTUAL WORKSTATION WEB-SESSION IS SUSPENDED
11.4. RESUMING VIRTUAL WORKSTATION WEB-SESSION

(Total 10 min)
min Sheet
page
OK /
NOK
Input Parameters
THE CONTROL DOMAIN WEB-SESSION IS AVAILABLE.

SUSPENDED VIRTUAL WORKSTATION WEB-SESSION IS AVAILABLE
S1
Resume virtual workstation web-session
10
69
action = resume
THE SUSPENDED VIRTUAL WORKSTATION WEB-SESSION IS RESUMED
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 36/122
11.5. ENTERING OBP MODE ON THE VIRTUAL

WORKSTATION
(Total 6 min)
min Sheet
page
OK /
NOK
Input Parameters
THE CONTROL DOMAIN WEB-SESSION IS AVAILABLE.

SUSPENDED VIRTUAL WORKSTATION WEB-SESSION IS AVAILABLE
S1
Connect to the virtual workstation console
78
54
action = connect
S2
Shut down the Solaris OS on it

run_level = 0
THE SUSPENDED VIRTUAL WORKSTATION WEB-SESSION IS RESUMED
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 37/122
12. EXPORTING CIUS DVD IMAGES TO THE

VIRTUAL WORKSTATION
The chapter details how to export CIUS DVD images from the repository on the control
domain to a virtual workstation.
(Total 7 + (*) min)
min Sheet
page
OK /
NOK
Input Parameters
THE CONTROL DOMAIN IS OPERATIONAL

S1
If not yet done, open a telnet session to the control domain
87
(*)
62
80
80
66
80
87
action = connect
username = root
S2
If not yet done, add CIUS DVD images to the repository

disk_type = CIUS_DVD
S3
Check the virtual workstation state

action = list
S4
If the virtual workstation is started, stop it

action = stop
S5
Export the CIUS DVD image

omc_version = corresponding OMC-R version
dvd_num = number of the exported CIUS DVD
S6
If the virtual workstation has been stopped, start it

action = start
S7
Close the control domain telnet session

action = disconnect
THE CIUS DVD DISK IMAGES HAVE BEEN EXPORTED

(*) - The duration is up to 15 minutes per DVD disk.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 38/122
13. GETTING MAC-ADDRESS FOR THE VIRTUAL

WORKSTATION
This chapter details how to get MAC-address for the virtual workstation.
Note: You must use the MAC address of the virtual network (vnet) device as reported by
the ldm command for your jumpstart configuration and not the one reported in the
banner for the guest.
(Total 1 min)
min Sheet
page
OK /
NOK
Input Parameters
THE CONTROL DOMAIN IS AVAILABLE

S1
Get MAC-address for the virtual workstation
81
ldom_num = virtual workstation number
THE VIRTUAL WORKSTATION MAC-ADDRESS IS KNOWN
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 39/122
14. UPDATING TARGET HOST SYSTEM

FIRMWARE VERSION
System Firmware is essentially software that is embedded on a hardware device and
directly controls it (resets, initializes and configures) before the operating is booted.
The firmware is what actually boots the OS, and it is usually contained in some sort of
Flash PROM on a system board.
Unlike an OS, which is designed to run on lots of different configurations of hardware
and occupies a lot of room (10s or 100s of megabytes) on the disk, firmware is usually
space-constrained to a few megabytes (sometimes less than that), so it usually
contains only the code needed for that specific hardware configuration. That is why
each Sun system gets its own separate release of firmware. Firmware specific to one
type of system will usually not function on a different system.
System Firmware updating is required because of:
Expanded compatibility and enhancements
Better reliability and system availability
Better system performance
Additional system features
Security fixes
Other bug fixes
This chapter details how to update system firmware version on the target host.
14.1. UPDATING OBP VERSION FOR T5140 SERVER

(Total (*) min)
min Sheet
page
OK /
NOK
Input Parameters

S1
Update T5140 system firmware
(*)
82
THE T5140 SYSTEM FIRMWARE VERSION HAS BEEN UPDATED

(*) - The updating of the system firmware version may take up to 40 minutes.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 40/122
14.2. UPDATING OBP VERSION FOR T3-2 SERVER

(Total (*) min)
min Sheet
page
OK /
NOK
Input Parameters

S1
Update T3-2 system firmware
(*)
105
THE T3-2 SYSTEM FIRMWARE VERSION HAS BEEN UPDATED

(*) - The updating of the system firmware version may take up to 40 minutes.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 41/122
15. CONFIGURING/DECONFIGURING DNS CLIENT

ON CONTROL DOMAIN
The DNS service is used to centralize information about IP addresses and hostnames.
This chapter describes how to configure DNS client or remove DNS client settings on
control domain.
This procedure describes only the configuration of control domain as DNS client. It
does not explain how to install, configure and manage the DNS servers.
You must declare the control domain on the DNS server before you start the
procedure.
15.1. CONFIGURING DNS CLIE NT

(Total 2 min)
min Sheet
page
OK /
NOK
Input Parameters

S1
Configure DNS client on control domain
103
operation = add
domain_name = DNS server domain name
primary_ip = DNS server primary IP
secondary_ip_1 = DNS server first additional IP (optional)
secondary_ip_2 = DNS server second additional IP
(optional)
THE DNS CLIENT IS CONFIGURED
15.2. DECONFIGURING DNS CLIENT

(Total 2 min)
Min Sheet
page
OK /
NOK
Input Parameters

S1
Deconfigure DNS client on control domain
103
operation = remove
THE DNS CLIENT SETTINGS ARE REMOVED
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 42/122
16. SSH CONFIGURATION

This chapter details how to configure or check SSH service on control domain. SSH
service can be configured in one of the following states: secure mode, non-secure
mode. If control domain is just installed or SSH service never was configured after
installation then SSH service state is non-secure.
16.1. SECURE MODE ACTIVATION

Carry out the following steps to enable SSH secure mode on the control domain.
(Total 1 min)
min Sheet
page
OK /
NOK
Input Parameters
BEGINNING OF SSH CONFIGURATION

S1
Enable the SSH secure mode on control domain
104
action = enable
SSH SERVICE IS SWITCHED TO SECURE MODE ON THE CONTROL DOMAIN
16.2. CHECKING SSH SERVICE

Carry out the following steps to check SSH mode on control domain.
(Total 1 min)
Min Sheet
page
OK /
NOK
Input Parameters
BEGINNING OF SSH CHECK

S1
Check the SSH secure mode on control domain
104
action = check
SSH SERVICE CHECK IS PERFORMED ON THE CONTROL DOMAIN
16.3. NON-SECURE MODE ACTIVATION

Carry out the following steps to disable SSH secure mode on the control domain.
(Total 1 min)
min Sheet
page
OK /
NOK
Input Parameters
BEGINNING OF SSH CONFIGURATION

S1
Disable SSH secure mode on control domain
104
action = disable
SSH SERVICE IS SWITCHED TO NON-SECURE MODE ON THE CONTROL DOMAIN

External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 43/122
17. OPERATION SHEETS

The operation sheets are not arranged in the execution order. Always refer to the
operations sequence table, to determine what operations come next and their input
values.
The sheets used in this specific procedure also apply to other procedures (other
hardware configurations). Therefore, you may find some conditional sections or
instructions that pertain to other procedures.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 44/122
POWERING ON/OFF SERVER AND WORKSTATION

SCOPE
This sheet details how to power on or off a computer (server or workstation).
INPUT PARAMETERS
action
on | off
INITIAL STATUS
If (action = off), the operating system is halted, and the computer is at the OBP level.
If (action = on), the computer is powered OFF.
ACTIONS
If (action = off):
{
On the Sun workstation:
1.
Power OFF the workstation, using the frontside switch on the Sun Ultra-45
workstation.
2.
Power OFF the graphic display.
On the Sun Fire server:

1.
Turn the front key to the OFF position on the Sun Fire server.
2.
Power OFF the graphic display, if available.
On the Sun SPARC Enterprise T5140 or Oracle SPARC T3-2 server:

1.
Press and hold the frontside button on the server until the server is not switched off.
}
Else If (action = on):
{
On the Sun workstation:
1.
Power ON the graphic display.
2.
Power ON the SUN workstation, using the frontside switch on the Sun Blade or
Sun Ultra-45 workstation.
On the Sun Fire server:
1.
Power ON the graphic display, if available.
2.
Turn the front key to the ON position (|) on the Sun Fire server.
3.
Press the frontside button on the SUN server.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 45/122

On the Sun SPARC Enterprise T5140 or Oracle SPARC T3-2 server:
1.
Press the frontside button on the server.
FINAL STATUS
The Sun computer (Sun server or Sun workstation) is powered ON or powered OFF.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 46/122
CONNECTING/DISCONNECTING TO ILOM SERVICE

PRESENTATION
The purpose of this sheet is to describe how to establish SSH connection to ILOM, open the servers
system console and close it.
Only the one connection to the servers system console via ILOM can be established
at one period of time. All new connections will be opened in view-mode. Before
opening the new console session, close the previous one (including the connection
via serial port).
ILOM supports a maximum of 5 active sessions, including serial, Secure Shell (SSH),
and web interface sessions.
To get access to ILOM or system console you need to configure SSH service
between the supervisory workstation and ILOM. Note that SSH configuring on the
supervisory workstation is out of the scope of this document.
INPUT PARAMETERS
action
target
connect | disconnect
ILOM | system console
INITIAL STATUS
The servers power cords are plugged into power supplies.
For target = system console, server must be turned ON.
ILOM IP address and ILOM password are known.
A root shell session on the supervisory workstation is available.
ACTIONS
If action = connect:
{
1.
If not already done, open a root shell session on the supervisory workstation.
2.
If supervisory workstation is an OMC-R host with enabled SSH service, customize it to

connect to the server by SSH:
2.1.
Make a copy of SSH configuration file on the supervisory workstation:

Type at the command prompt of the root account shell on the
supervisory workstation:
# cp /etc/ssh/ssh_config /etc/ssh/ssh_config.orig
2.2.
Check the parameter StrictHostKeyChecking in /etc/ssh/ssh_config file on

# cat /etc/ssh/ssh_config
...
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 47/122

If this parameter is absent, add it to /etc/ssh/ssh_config file with the value no. For
this - add the line StrictHostKeyChecking no to /etc/ssh/ssh_config through any
editor (e.g. vi).
If a value of this parameter is not equal to no, modify it to no through any editor
(e.g. vi).
3.
Establish SSH connection to ILOM:

Type at the command prompt of the root account shell on the supervisory
workstation:
... # ssh -l root <ILOM IP address>

... password: <ILOM password>
...
->
4.
If target = system console, start the servers system console via ILOM. You may need to
log in to proceed.
Note: the output of the command, provided below, may differ depending of the server
state.
-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
Serial console started.
To stop, type #. <Return>
<hostname> console login: root

Password: <roots password>
...
#
5.
If supervisory workstation is an OMC-R host with enabled SSH service and the file
/etc/ssh/ssh_config was customized to connect the supervisory workstation to the ILOM,
5.1.
5.2.
Change the SSH configuration on the supervisory workstation back:

# cp /etc/ssh/ssh_config.orig /etc/ssh/ssh_config
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 48/122

}
If action = disconnect:
{
If the servers system console is opened on the supervisory workstation, close it.
To do this, type the (<Return>, #, dot) to the opened system console:
1.
#.
->
2.
Type exit to the ILOM console to close the ILOM connection:

-> exit
TROUBLESHOOTING
1.
If the following message appears during connecting to the system console:

...
Console session already in use. [view mode]
That means that the other console session has already been opened. Perform the following
steps:
1.1.
Type the (<Return>, #, dot) to the currently opened system console
Console session already in use. [view mode]

#.
->
1.2.
Stop the system console via opened ILOM session
-> stop /SP/console

Are you sure you want to stop /SP/console (y/n)? y
1.3.
2.
Retry the step of connecting to the system console
If the following message appears during connecting to the system console:

...
shell: Maximum number of sessions exhausted
That means that new ILOM session cannot be opened. You need to either reuse one of the
existing unused ILOM sessions or close some of them before opening a new one.
FINAL STATUS
The SSH connection to ILOM/system console is established/closed.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 49/122
ENTERING OBP MODE ON SERVER VIA ILOM CONSOLE

SCOPE
The purpose of this sheet is to describe the way to enter OBP mode via ILOM console.
INPUT PARAMETERS
None
INITIAL STATUS
The servers supervisory workstation is turned ON. Servers ILOM console is opened on the
supervisory workstation.
ACTIONS
ON A SUPERVISORY STATION
1.
Disable auto boot:

-> set /HOST/bootmode script="setenv auto-boot? false"
Set 'script' to 'setenv auto-boot? false'
2.
Reset the server:

-> reset /SYS
Are you sure you want to reset /SYS (y/n)? y
Performing reset on /SYS
3.
Start the servers system console:

Are you sure you want to start /SP/console (y/n)? y
Serial console started. To stop, type #.
...
After booting, the server will stay in the OBP mode
... ok
TROUBLESHOOTING
None
FINAL STATUS
The server is in OBP mode
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 50/122
CHECKING SUN SPARC ENTERPRISE T5140 / ORACLE

SPARC T3-2 HARDWARE AND SETTING OBP
PARAMETERS
SCOPE
The purpose of this sheet is to check the hardware configuration of Sun SPARC Enterprise T5140
or Oracle SPARC T3-2 server (according to the hardware product specification) and to reset Open
Boot Prom parameters.
INITIAL STATUS
The server is in OBP mode
The system console of the server is available and opened on the supervisory workstation.
ACTIONS
1.
Set default OBP parameters:

... ok set-defaults
2.
Check the hardware configuration.

2.1.
Launch the following command:

... ok setenv diag-switch? false
diag-switch? = false
... ok setenv auto-boot? false
auto-boot? = false
... ok reset-all
The console will be erased and then the system will be restarted in a special mode in
which the internal configuration is displayed.
Disregard any warning messages about Ethernet link.
2.2.
Check the memory size displayed within banner information:

...
...
...
2.3.
3.
, XXX MB memory available, ...
Check that the memory size XXX is in accordance with the machine hardware
specification (see [R2] for details).
Check the servers internal SCSI devices.
If the server is a Sun SPARC Enterprise T5140:

{
3.1

Make sure that the disks have at least 146 GB of free space available and their SCSI target
numbers are correct, according to the sample below.
Make sure that the DVD drive (Removable Read Only Device) is available.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 51/122
Note: A shown below output of the command depends on your configuration and may be
different. The represented result of executed command is shown as example only.
... ok probe-scsi-all
/pci@400/pci@0/pci@8/scsi@0
MPT Version 1.05, Firmware Version 1.27.00.00
Target 0
Unit 0 Disk
SASAddress
Target 1
Unit 0 Disk
SASAddress
Target 2
Unit 0 Disk
SASAddress
Target 3
Unit 0 Disk
SASAddress
HITACHI H101414SCSUN146GSA25
5000cca000997831 PhyNum 0
286739329 Blocks, 146 GB
SEAGATE ST914603SSUN146G0868
5000c50017215725 PhyNum 1
286739329 Blocks, 146 GB
HITACHI H101414SCSUN146GSA25
5000cca0009943f1 PhyNum 2
286739329 Blocks, 146 GB
SEAGATE ST914603SSUN146G0868
5000c5001721028d PhyNum 3
286739329 Blocks, 146 GB
/pci@400/pci@0/pci@1/pci@0/usb@0,2/hub@4/device@4/storage@0
Unit 0
Removable Read Only device
TSSTcorpCDDVDW TS-T633A SR00
}
If the server is a Oracle SPARC T3-2:
{
3.1

Make sure that the disks have at least 300 GB of free space available and their SCSI target
numbers are correct, according to the sample below.
Make sure that the DVD drive (Removable Read Only Device) is available.
Note: A shown below output of the command depends on your configuration and may be
different. The represented result of executed command is shown as example only.
... ok probe-scsi-all
/pci@400/pci@2/pci@0/pci@e/scsi@0
FCode Version 1.00.54, MPT Version 2.00, Firmware Version 5.00.17.00
Target 9
Unit 0
Disk
SEAGATE ST930003SSUN300G 0B70
585937500 Blocks,
300 GB
SASDeviceName 5000c500332198fb SASAddress 5000c500332198f9 PhyNum
0
Target a
Unit 0
TEAC
DV-W28SS-R
1.0C
SATA device PhyNum 7
Target b
Unit 0
Disk
SEAGATE ST930003SSUN300G 0B70
585937500 Blocks,
300 GB
SASDeviceName 5000c5003324d20b SASAddress 5000c5003324d209 PhyNum
1
Target c
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 52/122

Unit 0
Disk
300 GB
SASDeviceName
2
Target d
Unit 0
Disk
300 GB
SASDeviceName
3
Target e
Unit 0
Disk
300 GB
SASDeviceName
4
Target f
Unit 0
Disk
300 GB
SASDeviceName
5
SEAGATE
ST930003SSUN300G 0B70
5000c50033220073
SEAGATE
SEAGATE
5000c5003322c1cf
PhyNum
585937500 Blocks,
SASAddress 5000c5003321ff25
ST930003SSUN300G 0B70
PhyNum
585937500 Blocks,
SASAddress 5000c5003321ccc1
ST930003SSUN300G 0B70
5000c5003321ff27
SEAGATE
SASAddress 5000c50033220071
ST930003SSUN300G 0B70
5000c5003321ccc3
585937500 Blocks,
PhyNum
585937500 Blocks,
SASAddress 5000c5003322c1cd
/pci@400/pci@1/pci@0/pci@b/pci@0/usb@0,2/hub@2/hub@3/storage@2
Unit 0
AMI
Virtual CDROM
PhyNum
1.00
}
4.
Restore the factory default configuration.

... ok setenv auto-boot? true
auto-boot? =
true
... ok setenv auto-boot-on-error? true
auto-boot-on-error? = true
... ok setenv boot-device disk
boot-device =
disk
TROUBLESHOOTING
None
FINAL STATUS
The hardware configuration of the server is checked.
The server is powered on and halted at the OBP level.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 53/122
OS SHUTDOWN / REBOOT / RUN LEVEL CHANGE

SCOPE
This sheet describes how to shutdown, reboot the operating system or change the run level to
continue the operating system startup.
INPUT PARAMETERS
run_level
New operating system run level ( 0 | 6 | 2 | 3 | 4 | s )
INITIAL STATUS
A root session is available.
If the server is used without a graphic display or a keyboard, the remote console is available on the
ACTIONS
For a server used with a graphic display and a keyboard, or for a workstation:
1.
If not already done, open a root shell session on the computer.
2.
Shut down, reboot or change the operating system run level

Type at the command prompt of the root account shell on the computer:
# init run_level
For a server used without a graphic display and a keyboard:
1.
Shut down, reboot or change the operating system run level

workstation:
# init run_level
1.1.
If the following message is appear and run_level = 0, press o to continue
program terminated
r)eboot, o)k prompt h)alt?
TROUBLESHOOTING
If the init 0 or init 6 command does not result in the operating system shutdown, use the following
workaround:
For init 0:
Type at the command prompt of the root account shell or in the supervisory
workstation remote console:
# sync
# sync
# halt
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 54/122

For init 6:
Type at the command prompt of the root account shell or in the supervisory
workstation remote console:
# sync
# sync
# reboot
FINAL STATUS
The operating system is halted or rebooted, depending on the run_level parameter.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 55/122
CONFIGURING SGD USERS

SCOPE
This sheet is intended to help you configure SGD users on the control domain or combined server.
The following operations are available: adding, removing and changing a password for SGD user. It is
also possible to manage SGD user profile.
INPUT PARAMETERS
Note: some of parameters below are optional depending on chosen action.
action
create, remove, bind, unbind, list hosts or change password
user_id
ID of a user to be configured
user_name
name of a user to be configured
user_passwd password of a user to be configured
domain_name name of a virtual workstation (in format ldom<ldom_num>, where <ldom_num> is a
digit in the following ranges within the hardware platform: from 1 to 6 on T5140 server
and from 1 to 10 on T3-2 server) or the combined server hostname. Specified user is
being configured for this computer.
user_id and user_name parameters must be unique within the current control
domain. These parameters must not intersect with existing Solaris users on the
control domain or combined server (check /etc/passwd files for details).
INITIAL STATUS
Combined server or the control domain and the specified virtual workstations are available.
A root account shell is available on the control domain or combined server.
For removing and changing password user user_name must exist.
Console is closed on target virtual workstation.
ACTIONS
1.
If not already done, open a shell session of the root account on the control domain or
combined server.
2.
Perform the specified action:
If action = create
{
2.1.
Create specified SGD user with the command:
Type at the command prompt of the root account shell:
# /usr/local/ssgd/mk_user.sh -C -U<user_id> -N<user_name>

-P<user_passwd> -H<domain_name>
}
If action = remove
{
Note: all active sessions of the user being deleted will be closed.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 56/122
2.1.
Remove specified SGD user with the command:
# /usr/local/ssgd/rm_user.sh -f -N<user_name>
}
If action = bind
{
2.1.
Add specified local domain to the SGD users profile with the command:
# /usr/local/ssgd/mk_user.sh -A -N<user_name> -H<domain_name>

}
If action = unbind
{
2.1.
Remove specified local domain from the SGD users profile with the command:
Type at the command prompt of the root account shell on the control domain:
# /usr/local/ssgd/mk_user.sh -R -N<user_name> -H<domain_name>

}
If action = list hosts
{
2.1.
Get the list of local domains, bound to the SGD users profile with the command:
# /usr/local/ssgd/mk_user.sh -L -N<user_name>
The list of hosts will be presented in output of the command in the following format:
<date/time> PID <PID> : List of hosts bound to the user user_name:
<domain names list>
}
If action = change password
{
2.1.
Change password for specified SGD user with the command:
# passwd user_name
New Password: user_passwd
Re-enter new Password: user_passwd
passwd: password successfully changed for user_name
}
TROUBLESHOOTING
1.
If the following message appears during the SGD users creating (the output might vary):
ERROR: The console of domain ldom<number> is busy.
1.1. Close all console sessions on the virtual workstation according to the chapter
CONNECTING/DISCONNECTING TO THE VIRTUAL workstation console.
1.2. Remove created UNIX user:
# /usr/local/ssgd/rm_user.sh -N<user_name>
1.3. Perform the action again.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 57/122
FINAL STATUS
Specified SGD user has been configured.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 58/122
CONTROL DOMAIN INSTALLATION

SCOPE
This sheet is intended to help you install a control domain using the SGD DVD.
INPUT PARAMETERS
Mandatory:
IP_address
hostname
netmask
The IP address of the host where the control domain will be installed
The hostname of the host where the control domain will be installed
The netmask of the host where the control domain will be installed
Optional:
router_IP_address
The IP address of the default router for the host where the control domain will
be installed. This parameter is mandatory if the operator wants to access the
control domain, otherwise - optional.
timezone
The timezone of the host where the control domain will be installed (for
example: WET, EST, MST, GMT, GMT+3, US/Mountain, Brazil/East. Default
value: MET). Refer to the Supported timezones chapter for a full list of
acceptable values of the timezone parameter.
Any incorrectly specified parameter value may result in the control domain
installation failure. Please, do not start the control domain installation unless you
are completely sure that all parameter values are correct.
INITIAL STATUS
The server is physically installed, powered on and stands at the OBP level.
The SGD DVD is available.
ACTIONS
1.
Insert the SGD DVD in the hosts DVD drive and boot from the DVD:
If installation is being performed on a T5140 server:

{
{}ok boot cdrom - install -- SSGD ip=IP_address h=hostname
n=netmask [t=timezone] [r=router_IP_address]
}
If installation is being performed on a T3-2 server:
{
{}ok boot dvd - install -- SSGD ip=IP_address h=hostname
n=netmask [t=timezone] [r=router_IP_address]
}
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 59/122
2.
After Solaris installation the host will automatically reboot and primary logical domain
configuration will be start.
3.
After primary logical domain configuration, the host will automatically reboot again and guest
logical domains configuration will start.
Wait until the following message appears on the console:
#################################################################
#
#
# Control domain installation has completed
#
#
#
#################################################################
4.
Remove the SGD DVD from the DVD drive:

4.1. If not yet done, login as root user on the system.
4.2. Eject DVD from the DVD drive:
Type the command at the opened system console on the control domain:
# eject cdrom
4.3.
Take off the DVD disk from the DVD-RW drive.
TROUBLESHOOTING
1.
If the control domain installation was interrupted displaying some error message or the Solaris
installation (the first stage of the control domain installation) was switched into the interactive
mode, the most probable reason is that boot cdrom - install command was wrongly typed.
Verify that the format of the typed command is correct paying attention to the values of all
parameters.
For example, if you want to install the control domain with the following parameters:
Hostname - controlDomain
IP address - 47.164.35.123
Netmask - 255.255.255.0
Timezone - MET
Router IP address - 47.164.35.1
Then, the command should have the following format:
{}ok boot cdrom - install -- SSGD ip=47.164.35.123 h=controlDomain
n=255.255.255.0 t=MET r=47.164.35.1
2.
Check the content of the system log files located in the following directories:
/a/var/sadm/system
(Before the boot)
/var/sadm/system/logs
(After the boot)
3.
Check
the
content
of
the
/var/local/oam/ssgd_install.log
4.
If the following message has appeared in system console of control domain:
log
file
from
SGD
installation
tool
!!!! ERROR : The firmware version is out-of-date !!!!
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 60/122

It is necessary to upgrade the firmware version to the specified one or greater according to the
chapter 14. Updating Target host system firmware version
After that run SGD installation tool on the opened control domains system console:
Type the command at the system console on the control domain:
# /usr/local/tip/bin/ssgd_install.sh -Y
Wait for the end of installation.
Then remove the SGD DVD from the DVD drive.
5.
Ignore the following message which might appear on the system console or in the system log
files:
Failed to list SAVECORE dir contents. ERROR 0
FINAL STATUS
The control domain has been installed on the server.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 61/122
ADDING DISK IMAGES TO THE REPOSITORY

SCOPE
This sheet is intended to help you to add disk images to the repository on the control domain.
INPUT PARAMETERS
disk_type
type of added disk image(s)
INITIAL STATUS
The control domain is available.
A root account shell is available on the control domain.
The added media(s) are available.
ACTIONS
1.
If not already done, open a shell session of the root account on the control domain.
2.
Add the required disk image(s) to the repository:

Note: If disk_type = CIUS_DVD, it is necessary to perform the actions below for each CIUS
st
nd
DVD (1 and 2 ).
For each disk to be added:
{
2.1. Insert the disk to the control domain DVD drive.
Note: Wait about 20 seconds to let the OS to recognize the disk.
2.2.
Make an image for the disk:
Type at the command prompt of the root account shell on the control
domain:
# /usr/local/ldoms/mk_image.sh -f
2.3.
Eject DVD from the DVD drive:
Type at the command prompt of the root account shell on the control
domain:
# eject cdrom
2.4.
Take off the DVD from the DVD drive.
TROUBLESHOOTING
1.
If the following message appears (the output might vary):

!!! WARNING : You must re-export DVD image file for domain ldom<X> !!!
It is necessary to re-export the DVD image for the specified virtual workstations (ldom<X>)
according to the sheet Exporting CIUS DVD image from the repository
FINAL STATUS
The required disk images have been added to the repository on the control domain.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 62/122
CONTROL DOMAIN REMOVING

SCOPE
This sheet is intended to help you to remove a control domain from the server.
INPUT PARAMETERS
None.
INITIAL STATUS
ACTIONS
1.
2.
Open a new shell session of the root account on the control domain.
Remove the control domain with the following command:
# /usr/local/ldoms/clear_ldoms.sh
TROUBLESHOOTING
None.
FINAL STATUS
The control domain has been removed from the server.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 63/122
RESET T5140/T3-2 HOST

PRESENTATION
This sheet details how to reset T5140/T3-2 host.
INPUT PARAMETERS
None.
INITIAL STATUS
The servers supervisory workstation is turned on. Servers ILOM console is opened on the
ACTIONS
ON A SUPERVISORY STATION
1.
Power off the server:

-> stop /SYS
Are you sure you want to stop /SYS (y/n)? y
2.
Power on the server:

-> start /SYS
Are you sure you want to start /SYS (y/n)? y
TROUBLESHOOTING
None.
FINAL STATUS
The host is started.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 64/122
SETTING HARDENED MODE ON THE CONTROL DOMAIN

SCOPE
The intent of this sheet is to help you activate the hardened mode on the control domain that allows
the use of servers redundant hardware components.
To perform this step it is necessary to have 2 additional (free) IP addresses that
are not used in networking.
INPUT PARAMETERS
IpAddr_1
IpAddr_2
First IP address
Second IP address
INITIAL STATUS
There is no telnet connection to or from the control domain.
ACTIONS
1.
If not already done, open a shell session of root account on the control domain.
2.
Carry out the following command:

# cd /
# /usr/local/maint/set_hardened.sh -E -F<IpAddr_1> -S<IpAddr_2>
TROUBLESHOOTING
The log file of the tool is /var/tmp/set_hardened.log, consult it to get the exhaustive information
about the error(s) that occurred.
FINAL STATUS
The hardened mode is configured on the control domain.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 65/122
EXPORTING CIUS DVD IMAGE FROM THE REPOSITORY

SCOPE
This sheet is intended to help you export CIUS DVD image from the repository on the control domain.
INPUT PARAMETERS
ldom_num
omc_version
dvd_num
number of LDOM where a CIUS DVD image is to be exported

version of OMC-R application to identify required CIUS DVD (V17 / V18)
number of CIUS DVD
INITIAL STATUS
The required CIUS DVD image is available at the repository.
ACTIONS
1.
2.
Export necessary CIUS DVD image to a virtual workstation <ldom_num>.

# /usr/local/ldoms/export_image.sh -Dldom<ldom_num> -v<omc_version>

-d<dvd_num>
TROUBLESHOOTING
1.
If the following message appeared:

#====================================================================#
#
!!! The domain is running now !!!
#
#
It must be stopped before image exporting
#
# Please stop all applications running on domain ldom<ldom_num> and #
#
shutdown the domain
#
#====================================================================#
Press <Return> key to continue when ready...
Press <Return> key to continue the exporting.
FINAL STATUS
The required CIUS DVD image has been exported to the <ldom_num> virtual workstation.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 66/122
CONNECTING ETHERNET CABLES OF VIRTUAL

WORKSTATIONS ON T5140 SERVER
SCOPE
This sheet is intended to help you to connect Ethernet cables on SPARC Enterprise T5140 server.
INPUT PARAMETERS
None.
INITIAL STATUS
There is a Sun SPARC Enterprise T5140 server with 2 Ethernet boards and 8 Ethernet cables (one
th
cable has been already connected to the 0 port).
ACTIONS
1.
Connect the Ethernet cables from your network switch or hub to Ethernet Ports 1, 2, 3, 4, 5, 6, 7
(specified at the picture as nxge1, nxge2, nxge3, nxge4, nxge5, nxge6, nxge7) on the rear of the
chassis.
Note: The Ethernet ports 1, 2, 3, 5, 6, 7 are used by the virtual workstations; the port 4 is an
additional port for hardened mode on the control domain.
The following table describes a correspondence between Ethernet Ports and virtual workstation
numbers:
Ethernet Port
Virtual workstation number
1
2
3
5
6
7
1
2
3
4
5
6
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 67/122
TROUBLESHOOTING
None.
FINAL STATUS
The Ethernet cables have been connected to the Ethernet boards.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 68/122
WORKING WITH THE HOST VIA SGD

SCOPE
This sheet is intended to help you connect/disconnect/suspend/resume the virtual workstation or
combined server via SGD.
Described actions have been performed on Microsoft Windows XP operating system
with Firefox 3.0.5 web-browser. In other operating systems and browsers base step
sequence is the same but some distinctions are possible.
INPUT PARAMETERS
Note: Some of the parameters below are optional depending on requested action.
action
SGD_IP_address
SGD_user
SGD_user_password
Unix_user
Unix_user_password
connect / disconnect / suspend / resume

control domain IP address in case of virtual workstations or IP
address of combined server.
Name of the SGD user.
Password of the SGD user.
Name of Unix user existing on the virtual workstation. If the parameter
is not defined, use "omc" user's name.
Password for the selected Unix user.
INITIAL STATUS
In case of virtual workstations: The control domain and the target virtual workstation are available.
In case of combined server: Combined server is available and operational.
ACTIONS
if action = connect:
{
1.
Type SGD_IP_address at address bar of the web-browser. The following page appears:
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 69/122
Note: If Java technology is not enabled in your browser, a warning message is

shown. You must enable Java technology in your browser before proceeding.
Click to Log in reference. The SGD Login dialog box is shown:
Note: If JavaScript is not enabled in your browser, a warning message is displayed

beneath the login dialog box.
2.
Type in SGD_user and SGD_user_password correspondingly.
3.
Click the Login button.

While SGD is starting up, the splash screen is shown.
4.
If the following window appears:
Click Yes to agree the connection. Once you have clicked Yes, you do not see the security
message again unless there is a problem with the connection.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 70/122

The SGD Client icon is displayed in the task bar (in case of Windows OS):
After that in case of successful connection the following web-application is available:
5.
To open connection to the host desktop, click the link with the domains hostname.
The following progress bar is shown:
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 71/122

If the following dialog box appears, enter defined Unix_user and Unix_user_password:
When the connection has been ready, a desktop session is opened.

}
if action = disconnect
{
1.
If not yet done, open a SGD web-session.
2.
There are two ways to close the SGD connection with host:
2.1.
If host desktop session is opened, close corresponding window with Close button.
Opened SGD connection is closed.
2.2.
Click on the picture (marked by red) to close the SGD connection with host:
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 72/122

}
if action = suspend
{
1.
2.
Click on the picture (marked by red) to suspend the SGD session with host:
}
if action = resume
{
1.
2.
Click on the picture (marked by red) to resume the suspended SGD session with host:
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 73/122

}
TROUBLESHOOTING
1.
If the following message appears:
1.1.
In case of Windows OS, add the SGD server to the Windows hosts file:
1.1.1 Open %windir%\system32\drivers\etc\hosts file: Press Start button, click Run, type
following command and press [ENTER]:
Type under Windows user with local administrator rights:
notepad %windir%\system32\drivers\etc\hosts
1.1.2 If SGD_hostname is already present in this file, update IP address with new
SGD_IP_address.
1.1.3 If file does not contain SGD_hostname, append to the file this record:
<SGD_IP_address> <SGD_hostname>
Where <SGD_hostname> and <SGD_IP_address> are hostname and IP of control domain
in case of virtual workstations or hostname and IP of the combined server.
1.2.
Try to re-login by clicking the LOGIN button:
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 74/122

1.3. If connection is still failed, contact with your local TAS team.
2.
If there is a security problem with the connection to the SGD server, a Potentially Unsafe
Connection message is displayed:
Click the Accept button to proceed.

3.
If the following message appears during the connecting to the SGD server:
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 75/122

That means another SGD servers web-session has been opened and the current session has
been closed.
4.
If the following message appears during the connecting to the SGD server:
That means number of users that can log in is limited by license(s) and has exceeded. To log in
you should use one or both of the following:
Install another or additional SGD license(s).
Find some unused session(s) and close it.
5.
If the following message appears during the connection to the SGD server on the step 5
and Unix_user = croot:
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 76/122
Check the state of OS hardened mode. If OS hardened mode is enabled, disable OS

hardened mode in accordance with sheet Setting OS Hardened mode
FINAL STATUS
The required action has been performed.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 77/122
CONNECTING/DISCONNECTING TO THE VIRTUAL

WORKSTATION CONSOLE
SCOPE
This sheet is intended to help you connect/disconnect to virtual workstation console.
INPUT PARAMETERS
action
ldom_num
connect / disconnect
virtual workstation number
INITIAL STATUS
<ldom_num> virtual workstation is started.
ACTIONS
If action = connect
{
1.
2.
Get a port number for <ldom_num> virtual workstation:

# /opt/SUNWldm/bin/ldm list ldom<ldom_num>

NAME
STATE FLAGS
CONS
VCPU
ldom<ldom_num> active -t---- <port_num> 16
MEMORY
3G
UTIL
6.2%
UPTIME
3m
<port_num> - the port number.

3.
Connect to <ldom_num> virtual workstation:

# telnet localhost <port_num>

...
Connecting to console "ldom<ldom_num>" in group "ldom<ldom_num>"
....
Press ~? for control options ..
Note: symbol means that you must press Return key.
In case when the Solaris OS is stopped or was not yet installed, the following prompt will
appear:
... ok
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 78/122

It means that the virtual workstation is in OBP mode.
In case when the Solaris is online, enter the login credentials to access console:
...
<hostname> console login: root
Password: <roots password>
...
#
}
{
1.
Press Enter or Return key on the keyboard to clear a terminal buffer.
2.
Type at the opened virtual workstation console session ~ + .(sequentially). The following
message will appear:
Connection to localhost closed by foreign host.
TROUBLESHOOTING
1.
If the following message appears during the connecting to the virtual workstation console:
You do not have write access
That means that another console session is opened on the virtual workstation.
Perform the actions below to get write access to the console:
1.1.
Press Enter or Return key on the keyboard to clear a terminal buffer.
1.2.
Type ~ + w (sequentially) at the opened virtual workstation console for entering to the
console command mode.
Warning: another user currently has write permission
to this console and forcibly removing him/her will terminate
any current write action and all work will be lost.
Would you like to continue?[y/n] y
FINAL STATUS
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 79/122
VIRTUAL WORKSTATION MANAGEMENT

SCOPE
This sheet is intended to help you start, stop or list a state of the virtual workstation.
INPUT PARAMETERS
action
ldom_num
start | stop | list

virtual workstation number
INITIAL STATUS
ACTIONS
1.
2.
Perform the corresponding action for the virtual workstation <ldom_num>.

# /opt/SUNWldm/bin/ldm <action> ldom<ldom_num>

If action = list, the following output will be shown (the output may vary and depends on certain
virtual workstation):
NAME
ldom<ldom_num>
STATE
bound
FLAGS
------
CONS
5005
VCPU
16
MEMORY
3G
UTIL
UPTIME
bound - virtual workstation is stopped

active - virtual workstation is started
TROUBLESHOOTING
None.
FINAL STATUS
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 80/122
GETTING VIRTUAL WORKSTATION MAC-ADDRESS

SCOPE
This sheet is intended to help you get virtual workstation MAC-address.
INPUT PARAMETERS
None.
INITIAL STATUS
The virtual workstation is in OBP mode.
ACTIONS
1.
Open a new shell session of the root account on the control domain.
2.
Get MAC-address for <ldom_num> virtual workstation:

# /opt/SUNWldm/bin/ldm list-domain -o network

-e ldom<ldom_num> | grep vnet0
vnet0
ldom5-vsw0@primary
network@0 <MAC_address>
th
4 column is the required MAC-address <MAC_address>.

Note: the output may vary and depends on virtual workstation number
TROUBLESHOOTING
In case of any errors, please, call your local TAS team.
FINAL STATUS
MAC-address of the virtual workstation is known.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 81/122
UPDATE OBP VERSION FOR T5140 SERVER

SCOPE
This sheet details how to update the version of Open Boot PROM on T5140 server.
Note: A shown output of commands may be different depending on your configuration. The
represented result of executed commands is been shown as example only.
INITIAL STATUS
The OMC-R application is not running.
A croot session is available on the OMC-R server.
ACTIONS
ON A SERVER
1.
If not yet done, open a shell session of croot account on the OMC-R server.
2.
Download the Sun System Firmware image to the System Controller:

2.1.
Set the current directory:

Type at the command prompt of the croot account shell on the OMC-R server:
... (root) # cd /usr/local/firmware/T5140/145676-01/

2.2.

... (root) # sysfwdownload Sun_System_Firmware*pkg

You will see the downloading progress:
.......... (6%).......... (12%)....
Wait until the download completes successfully. This should take about 3-5 minutes.
When the download has finished the following message will appear:
Download completed successfully.
3.
Exit the Operational System:

... (root) # init 0
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 82/122
FROM A SUPERVISORY WORKSTATION

4.
Establish SSH connection to ILOM under root:

Under root login on the supervisory workstation:

...
->
5.
Create ALOM CMT Compatibility Shell.

Type at the ILOM CLI under root:
-> create /SP/users/admin role=Administrator cli_mode=alom

Creating user...
Enter new password: <password>
Enter new password again: <password>
Created /SP/users/admin
6.
Close connection to ILOM under root:

-> exit
7.
Establish SSH connection to ILOM under admin:

... (root)# ssh -l admin <ILOM IP address>

Password: <password>
...
sc>
8.
From the System Controller CLI, issue the power off:

Type at the ILOM CLI under admin:
sc> poweroff
Are you sure you want to power off the system [y/n]? y
Wait until the following message appears (this may take about 2-5 minutes):
sc> Chassis | critical: Host has been powered off
9.
Set the key switch position:

sc> setkeyswitch -y normal

Keyswitch is in the NORMAL position.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 83/122
10.
Flash update the downloaded Sun System Firmware image:

sc> flashupdate -s 127.0.0.1

NOTE: A flashupdate takes about 6 minutes to load a new file.
Some commands are disabled until the file load is complete.
The SC will be reset to complete the upgrade.
Are you sure you want to load the specified file (y/n)? y
As the download process progresses, a series of periods appears across your screen.
.......................
When the download process is finished, ILOM will display a message about successful
operation and about automatic reset of service processor is planned (the output may be various
and depends on initial firmware version):
Audit | major: Upgrade Succeeded
Operation succeeded
New firmware images were loaded. The SC will reset now to complete the
upgrade.
The ILOM connection will be broken. Wait about 2 minutes until reset Service Processor.
11.


...
->
12.
Remove ALOM CMT Compatibility Shell.

-> delete /SP/users/admin

Are you sure you want to delete /SP/users/admin (y/n)? y
Deleted /SP/users/admin
13.
Start the Operational System:

-> start /SYS

Starting /SYS
Wait about 15 minutes until Operational System is booted.
14.

-> exit
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 84/122
TROUBLESHOOTING
1.
The following message may appear during creating ALOM CMT Compatibility Shell:
create: /SP/users/admin already exists
Create failed
It means that the user already exists and there is no need to create it again.
If the user exists but you have forgotten the password, then remove the user:
-> delete /SP/users/admin role=Administrator

Are you sure you want to delete /SP/users/admin (y/n)? y
Deleted /SP/users/admin
Then you should create the user again:
-> create /SP/users/admin role=Administrator cli_mode=alom

Creating user...
Enter new password: <password>
Enter new password again: <password>
Created /SP/users/admin
2.
The following message may appear during downloading the Sun System Firmware image to the
System Controller:
sysfwdownload: send/receive failed(2) - "ret = -7"
It means that internal error has occurred. You should use the following steps:
2.1.
Reset the service processor:
sc> resetsc
2.2.
Try to download the Sun System Firmware image to the System Controller again in
accordance with the step from main procedure.
Note: If mentioned above error has repeated again, please, contact your local TAS.
3.
If the following message appears during updating the downloaded Sun System Firmware
image, ignore it:
Using the following information for flash update
image file:
/coredump/ILOM_flash.pkg
sector_size:
0x20000
image_start:
0x0
flash_start:
0xfe0000
header_offset: 0x0
flash_size:
0x1000000
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 85/122
4.
If the following message appears during starting operating system, ignore it:
-> start /SYS
start: Target already started
FINAL STATUS
The OBP version on T5140 server has been updated.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 86/122
CONNECTING/DISCONNECTING TO THE HOST WITH

TELNET
SCOPE
This sheet is intended to help you connect/disconnect to the host with telnet from the supervisory
workstation.
INPUT PARAMETERS
Mandatory:
action
host
username
connect / disconnect
hostname or IP address of the target host (optional when action is disconnect)
name of the user to be connected to the host (optional when action is disconnect)
INITIAL STATUS
The target host is available.
A username account shell is available on the host.
A root shell session on the supervisory workstation is available.
ACTIONS
If action = connect
{
1.
2.
Perform the following command to open a telnet session on the target host:
workstation:
... # telnet -l <username> <host>

...
Escape character is '^]'.
Password: <username_password>
Enter the password for username to proceed.
}
{
1.
Type Ctrl + ] at the opened telnet session. The following prompt appears:
telnet>
2.
Type quit to close the telnet session:

telnet> quit
TROUBLESHOOTING
None.
FINAL STATUS
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 87/122
CONTROL DOMAIN BACKUP ON DVD OPERATIONS

PRESENTATION
The purpose of this sheet is to back up control domain file systems on DVD.
Required resources:
- At least, one DVD disk to back up the control domain. Actual number of DVD disks depends
on the file systems size.
Please use the following types of DVD media:
DVD+RW / DVD-RW 4x or higher
DVD+R / DVD-R 4x-8x
Other types of DVD cannot be used.
Disks of the DVD-R, DVD+R and DVD-RW types must be blank.
If you use the DVD-RW disks, you should have blanked them on one of the
previous steps in the procedure. Please, return to this step, if you have not
performed it.
DVD+RW disks can be either blank or not blank, it does not matter.
Estimated backup size (including estimated quantity of DVD disks), which is
calculated during estimation or images creation step, is an approximate figure
and it might vary during the real backup procedure.
INPUT PARAMETERS
step:
indicates what backup step is performed:

estimation
- backup data size estimation
images_creation
- images creation
burning
- burning images
backup mode:
online
- backup is performed in online mode
offline
- backup is performed in offline mode
mode:
INITIAL STATUS
A root or croot account shell is available on the control domain.
ACTIONS
Perform appropriate section correspondingly to the value of the step parameter:
If step = estimation:
{
1.
Run the following command:
Type at the command prompt of the root or croot account shell on the computer:
# /usr/local/tip/bin/tip_backup.tcl -Y -C
The tool will display information about its processing in detail. At the end, you will be able to see
a table with estimated information regarding:
- Distribution of the partition dumps among DVD disks:
o At first, DVD number is written.
o Then DVD contents are listed. For each backed up partition its name and the
size of dump in megabytes are specified. If you see [vol #x] after the partition
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 88/122
name, it means that the partition dump is assumed to be split among several
DVD disks; in this case, x is a partition dump volume number
o After the list of contents, summed up information about filled and remained free
space on the DVD is given
Excluded and included backup data:
o Lists of data excluded by default, excluded and include by a user (with sizes in
kilobytes)
o Total sizes of excluded and included data (in megabytes)
Total size of data on DVD disks
Total time necessary to create DVD images
An example of the tool output is given below:

============================================
Table of DVD contents (preliminary estimate)
============================================
DVD #1:
------/
4064.0 MB
/var
88.34 MB
/home
13.51 MB
Totally filled/DVD capacity: [ 4166.0 / 4460.0 ] MB
Remained free space on DVD: 294.1 MB
****** Excluded data (Kbytes):
/var/crash/maramba
1
Total excluded: 1
Total DVD data size: 4.068 GB
****** Estimated time to create DVD images: 31 min 22 sec
You must study the output and make a decision, if the proposed number of DVD disks and
backup time are acceptable. If this is not the case, you may change excluded and included data
lists and repeat this step.
Note: Real amount of disks for backup and time necessary to create images may be bigger
than estimated values due to specifics of the ufsdump tool, which is used to dump partitions.
}
If step = images_creation:
{
1.
If mode = offline, execute the command:
# svcadm enable -rs svc:/ldoms/ldmd

2.
If mode = online:
Type at the command prompt of the root or croot account shell on the
computer:
# /usr/local/tip/bin/tip_backup.tcl -Y -online
}
If mode = offline:
{
computer:
# /usr/local/tip/bin/tip_backup.tcl -Y
}
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 89/122

The tool will display the table with the backup contents and the time that the backup will take.
After this table you will see the question:
Are you ready to start the backup?: ("yes" or "no")
You need to answer yes to start the images creation process.
To decline the images creation, you may answer no.
}
If step = burning:
{
1.
# /usr/local/tip/bin/tip_backup.tcl -Y -burn
For every image found in the work directory, the tool will ask:
{
Please, insert backup DVD#X into the DVD-RW drive and
type 'burn' to start burning (or 'exit' to exit from the tool)
It means that you need to insert next DVD into the DVD-RW drive and type:
burn
1.1.
When the disk is ready it will be automatically ejected. Take it off.

If you decide not to proceed with burning DVD disks, you may type:
exit
}
2.
Mark all recorded DVD disks (e.g. with a felt-tip pen).
3.
Verify recorded disks.

Note: Verification takes about 20 minutes for each disk, if they all are of a good
quality. If there are read errors on the disks, verification may last for a longer period of
time, since the OS attempts to re-read faulty sectors several times.
To start verification, run the following command:
# /usr/local/tip/bin/tip_backup.tcl -Y -verify
For every backup DVD, the tool will ask:
{
type 'ver' to start its verification (or 'exit' to exit from
the tool):
Note: Wait about 20 seconds to let the OS to recognize the DVD.

It means that you need to insert backup DVD #X into the DVD-RW drive and type:
ver
If you decide not to proceed with verifying DVD disks, you may type:
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 90/122

exit
Depending on the result of verification, you will see either:
Backup DVD #X verification has successfully passed
- that means that the disk is fully readable and can be used for restoration.
ERROR
ERROR
cannot
ERROR
: Backup DVD #X verification has failed

: The disk has bad (non-readable) sectors and
be used for restoration
: You must burn image for DVD #X on another DVD disk
- that means that the disk cannot be used for restoration. In this case, after
verification finishes, you can burn image for DVD #X on another DVD disk and
verify it anew with the following commands (you should act as in the general case
of the -burn option, as described above):
Type at the command prompt of the root or croot account shell on
the computer:
# /usr/local/tip/bin/tip_backup.tcl -Y -burnX
(where X is a number of the defective backup DVD)
the computer:
# /usr/local/tip/bin/tip_backup.tcl -Y -verifyX
(where X is a number of the defective backup DVD)
If verification has failed again, try to burn the image for DVD #X on another disk
and verify it anew.
}
4.
After all images are successfully burned, it is recommended that you remove images from
the work directory:
# /usr/local/tip/bin/tip_backup.tcl -Y -purge
}
TROUBLESHOOTING
1.
The log files of the tool are in /var/local/oam/tip_backup (or the log files may be in
/tmp/tip_backup for the images_creation step).
2.
If you get the following error from the tool:

Error burning DVD#x
Disk's quality may be poor, you can try burning another one.
type 'burn' to start burning (or 'exit' to exit from the tool)
Please, try burning another DVD. If several consecutive attempts to burn DVD fail, it may mean
a DVD-RW drive hardware problem or some other specific problem. Contact your local TAS for
support.
3.
If the DVD disk is not ejected automatically, please try:

External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 91/122

# eject cdrom
If that fails, try to eject the disk with the eject button on the DVD-RW drive.
If that also fails:
1) Switch to OBP:
computer:
# init 0
2) Start loading the OS from the hard disk:
<#.> ok boot disk
Resetting ....
3) Press the eject button on the DVD-RW drive while the OS is being loaded.
4.
If the following error message appeared:

... ERROR
: no space left on device
It means that some partitions are full, so it is necessary to remove unnecessary files from these
partitions to free the disk space and after that restart failed operation.
FINAL STATUS
The necessary step is completed.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 92/122
CONTROL DOMAIN BACKUP ON NFS OPERATIONS

PRESENTATION
The purpose of this sheet is to back up control domain file systems on NFS.
INPUT PARAMETERS
NFS_server_IP
share
mode:
IP address of NFS server

shared directory name on NFS server
backup mode:
online
- backup is performed in online mode
offline
- backup is performed in offline mode
INITIAL STATUS
ACTIONS
1.
If mode = offline, execute the command:

# svcadm enable -rs svc:/ldoms/ldmd

2.
If mode = online:
{
# /usr/local/tip/bin/tip_backup.tcl -Y -online
-NFS/net/<NFS_server_IP>/<share>
}
If mode = offline:
{
# /usr/local/tip/bin/tip_backup.tcl -Y
-NFS/net/<NFS_server_IP>/<share>
}
The tool will display the table with the backup contents and the time that the backup will take.
After this table you will see the question:
Are you ready to start the backup?: ("yes" or "no")
You need to answer yes to start the backup process.
To decline the NFS backup, you may answer no.
TROUBLESHOOTING
1.
The log files of the tool are in /var/local/oam/tip_backup (or the log files may be in
/tmp/tip_backup).
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 93/122
FINAL STATUS
The NFS backup is performed.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 94/122
CHECK FILE SYSTEM FULL

PRESENTATION
The purpose of this sheet is to check if file systems are full.
INITIAL STATUS
A root account shell is available.
ACTIONS
1.
Check the percentage of use of the local file systems:

# df -k | grep -v cdrom
Note: An output of this command on your machine will generally differ from the example given
below. The output depends on role of machine and file systems condition.
1.1.
Pay attention to value of capacity column of each file system (see example below).
# df -k | grep -v cdrom
Filesystem
kbytes
/dev/dsk/c2t10d0s0
25159
/dev/dsk/c2t10d0s3
241607
/proc
0
fd
0
/dev/dsk/c2t10d0s5
317799
/dev/dsk/c2t10d0s4
384871
/dev/dsk/c2t10d0s6
484719
swap
631176
/dev/dsk/c2t11d0s0
288855
/dev/dsk/c2t11d0s1
1089439
/dev/dsk/c2t11d0s3
605119
used
23262
193653
0
0
31510
253555
960
177464
90439
75331
605123
avail capacity
0
100%
23794
90%
0
0%
0
0%
254510
12%
92829
74%
435288
1%
453712
29%
169531
35%
959637
8%
0
100%
Mounted on
/
/usr
/proc
/dev/fd
/var
/opt
/home
/tmp
/MD/base
/CMN/base
/OMC/base
If a file system is full (capacity is 80% for swap file system and 100% for other file systems),
then clean the file system by deleting useless files.
FINAL STATUS
No one of the file systems must be full.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 95/122
BLANKING DVD-RW MEDIA

PRESENTATION
The purpose of this sheet is to blank DVD-RW disks.
Required resources:
- DVD-RW disks to blank
This sheet cannot be applied to DVD+RW disks, since they are blanked automatically
during the burning process and cannot be blanked manually.
If the machine to backup is a virtual workstation then mentioned below command

must be performed on the control domain.
The DVD-RW should be blanked on the same computer, where backup will be
performed.
INPUT PARAMETERS
None
INITIAL STATUS
The shell session is available on the computer.
ACTIONS
Perform the following steps for each DVD-RW disk to blank:
{
1. Insert the DVD-RW disk to the DVD-RW drive.
2. Blank the DVD-RW disk:
the computer:
# /bin/cdrw -b fast
}
TROUBLESHOOTING
None
FINAL STATUS
DVD-RW disks are blanked.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 96/122
CONTROL DOMAIN RESTORATION

PRESENTATION
The purpose of this sheet is to restore control domain file systems from DVD disks or NFS server.
The restoration is composed of two phases:
- file systems restoration (when the /, /home and /var partitions are restored)
- LDOMS configuration restoration (when virtual workstations are reconfigured)
Required resources:
- The Solaris Boot CD or SGD DVD
- For restoration from DVD, a set of backup DVD disks
- For restoration from NFS, a NFS server with backup
INPUT PARAMETERS
media:
IP_address
Netmask
Router_IP
NFS_server_IP
share
Restoration media:
nfs
- restoration is performed from NFS server
dvd
- restoration is performed from DVD disks
IP address of computer
Valid network mask of computer
Valid IP address of network router
IP address of NFS server from which restoration is performed
shared directory name on NFS server which contains right backup
INITIAL STATUS
The computer is in the OBP mode.
ACTIONS
1.
Insert Solaris Boot CD or SGD DVD into the DVD-RW drive.
2.
Load the operating system from the disk:

If restoration is being performed on a T5140 server:
{
... ok boot cdrom -s
.....
Rebooting ....
.....
SINGLE USER MODE
#
}
If restoration is being performed on a T3-2 server:
{
... ok boot dvd -s
.....
Rebooting ....
.....
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 97/122

SINGLE USER MODE
#
}
2.
Determine the disk device for DVD drive (denoted further in the text as <dvd_device>):
If restoration is being performed on a T5140 server, the disk device is c0t0d0s0
If restoration is being performed on a T3-2 server, the disk device is c2t7d0s0
3.
Eject the bootable media:

Type at the command prompt of the root account on the console terminal:
# umount /cdrom
# eject /dev/dsk/<dvd_device>
4.
Create mount point:

# mkdir /tmp/root/mount_point
If media = nfs:
{
5.1. Configure network card:
If restoration is being performed on a T5140 server:
{
# ifconfig nxge0 inet <IP_address> netmask <Netmask> up

}
If restoration is being performed on a T3-2 server:
{
# ifconfig igb0 inet <IP_address> netmask <Netmask> up

}
5.2. Set up routing:
# route add default <Router_IP>
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 98/122

5.3. Mount NFS directory:
# mount -F nfs -r <NFS_server_IP>:/<share>/control_domain

/tmp/root/mount_point
}
If media = dvd:
{
st
5.1. Insert 1 backup DVD.

st
5.2. Mount 1 backup DVD:

# mount -F ufs -r /dev/dsk/<dvd_device> /tmp/root/mount_point

}
6.
Extract the restoration tool and its configuration files:

# tar xvf /tmp/root/mount_point/backup.tar

7.
Start the file systems restoration:

# /tmp/Nortel/tip_restore.sh -Y -system
The tool will display details about the backup data that you restore. For example (for NFS
backup):
Media type: NFS
Backup date: 22/12/2009
Solaris version: 5.10
Hardware type: SUNW,T5140
Host name: maramba
Host ID: 84e47726
Host type: Control Domain
Then you will see the question:
Are you ready to start the restoration? (type "yes" or "no"):
To start the restoration, answer yes. To cancel the restoration, answer no.
The system restoration step will be started.
The restoration tool uses the ufsrestore utility to restore dumped partitions. The
ufsrestore utility may display warning messages. These warning messages do not
actually report any error, therefore, disregard them.
If media = dvd:
{
8.
If you see the message:

The current DVD number is X
Please, insert DVD #Y into the DVD-RW drive [ENTER]
{
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 99/122

Insert DVD #Y into the DVD-RW drive and press [ENTER].
}
}
After the system restoration step is performed, the tool will boot the operating system into
the multi-user mode from the hard disk.
9.
Login to the operating system under the root user:

on the console terminal
hostname console login: root

Password: <root password>
.....
10. Start the virtual workstations configuration restoration:
# /usr/local/tip/bin/tip_restore.sh -Y -ldom
11. If the following message was displayed:
ATTENTION: please power-cycle the system and re-execute the script
Then perform following actions:
{
11.1.
Connect to the ILOM console (see p. 47) and reset the server:
-> reset /SYS
Are you sure you want to reset /SYS (y/n)? y
Performing reset on /SYS
After the system has rebooted, perform following actions:
11.2.
Login to the operating system under the root user:

on the console terminal
hostname console login: root

Password: enter the root password
.....
11.3.
Restart the virtual workstations configuration restoration:

Type at the command prompt of the root account on the console
terminal:
# /usr/local/tip/bin/tip_restore.sh -Y -ldom
}
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 100/122
12. The following message will be displayed:

ATTENTION: guest domains configuration will start after reboot
Wait until the system reboots and the following messages are shown at the system
console:
09/12/22 09:07:31 PID 2689 : Exiting with code 0 : OK
09/12/22 09:07:31 PID 2689 : Cleaning temp. files...
If media = dvd:
{
13. Take off the backup DVD from the DVD-RW drive.
}
TROUBLESHOOTING
1.
If messages like below are displayed in ILOM console after system part of restoration, ignore
them.
Nov 18 08:14:17 niagara picld[231]: PICL snmpplugin: cannot fetch
object value (err=-1, OID=<1.3.6.1.4.1.42.2.70.101.1.1.4.1.3>,
row=165)
Nov 18 08:14:17 niagara picld[231]: PICL snmpplugin: cannot fetch
object value (err=-1, OID=<1.3.6.1.4.1.42.2.70.101.1.1.4.1.4>,
row=165)
2.
The log files of the tool are in /var/local/oam/tip_restore (or the log files may be in
/tmp/tip_restore or /_tip_restore_to_remove for the file systems restoration
step).
FINAL STATUS
Control domain file systems and virtual workstation configuration are restored.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 101/122
STOPPING OMC-R APPLICATION

SCOPE
This sheet details how to stop the OMC-R application on OMC-R server or on an OMC-R workstation.
INITIAL STATUS
The OMC-R application is running.
An omc session is available on the OMC-R computer to stop.
ACTIONS
1.
If not already done, open a shell session of omc account on the OMC-R computer to stop.
2.
Carry out the command.

Type at the command prompt of the omc account shell on the OMC-R computer to
stop:
... (omc) % appstop std

...
OMC-R is completely stopped
... (omc) %
TROUBLESHOOTING
1.
The log file for the OMC-R application stop is /CMN/base/diagnostic/diag_init.
2.
The history log file (including all OMC-R computer starts and stops) of an OMC-R computer is
/CMN/base/diagnostic/diag_restart_omc.
FINAL STATUS
The OMC-R application is now stopped on the specified computer (the OMC-R server or the OMC-R
workstation).
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 102/122
CONFIGURE/DECONFIGURE DNS CLIENT ON CONTROL

DOMAIN
SCOPE
This sheet details how to configure or remove the DNS client settings on control domain.
INPUT PARAMETERS
operation = add | remove
domain_name : DNS server domain name (not applicable if operation = remove)
primary_ip : DNS server primary IP (not applicable if operation = remove)
secondary_ip_1 : DNS server first additional IP (optional, not applicable if operation = remove)
secondary_ip_2 : DNS server second additional IP (optional, not applicable if operation = remove)
INITIAL STATUS
The SGD software is installed and control domain is configured and accessible via network.
The DNS server is configured and accessible via network.
ACTIONS
1.
If not yet done, open the root shell session on control domain.
2.
Perform the command on the control domain:
If operation = add
{
Type at the command prompt of the root account shell on control domain:
# /usr/local/tip/bin/tip_configDns.sh -Aadd
-N<domain_name> -P<primary_ip> [-F<secondary_ip_1>]
[-S<secondary_ip_2>]
}
If operation = remove
{
# /usr/local/tip/bin/tip_configDns.sh -Aremove
}
TROUBLESHOOTING
None.
FINAL STATUS
The DNS client settings are added/removed on control domain.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 103/122
CONFIGURING SSH SERVICE ON CONTROL DOMAIN

SCOPE
This sheet details how to enable, disable or check the SSH secure mode on the control domain.
Checking the SSH mode allows to identify whether SSH secure mode is enabled or disabled on the
control domain.
INPUT PARAMETERS
action action to perform for SSH service ( enable | disable | check )
INITIAL STATUS
The SGD software is installed and control domain is configured and accessible via network.
ACTIONS
1.
If not yet done, open the root shell session on control domain.
2.
Launch SSH configuring tool:
If action = enable
{
# /usr/local/tip/bin/tip_configSSH.sh -Aenable
}
If action = disable
{
# /usr/local/tip/bin/tip_configSSH.sh -Adisable
}
If action = check
{
# /usr/local/tip/bin/tip_configSSH.sh -Acheck
}
TROUBLESHOOTING
None.
FINAL STATUS
The SSH secure mode is enabled, disabled or checked on control domain.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 104/122
UPDATE OBP VERSION FOR T3-2 SERVER

SCOPE
This sheet details how to update the version of Open Boot PROM on Oracle SPARC T3-2 server.
Note: A shown output of commands may be different depending on your configuration. The
represented result of executed commands is been shown as example only.
INITIAL STATUS
A croot session is available on the OMC-R server.
ACTIONS
ON A SERVER
1.
If not yet done, open a shell session of croot account on the OMC-R server.
2.

2.1.
Set the current directory:

... (root) # cd /usr/local/firmware/T3-2/145667-06/

2.2.

... (root) # sysfwdownload Sun_System_Firmware*pkg

You will see the downloading progress:
.......... (6%).......... (12%)....
Wait until the download completes successfully. This should take about 3-5 minutes.
When the download has finished the following message will appear:
Download completed successfully.
3.
Shutdown the Operating System:

... (root) # init 0
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 105/122
FROM A SUPERVISORY WORKSTATION

4.


...
->
5.
Power off the server (it will take about 60 seconds to completely power the server off):
-> stop /SYS

Are you sure you want to stop /SYS (y/n)? y
Stopping /SYS
6.
Set the key switch position to normal:

-> set /SYS keyswitch_state=Normal

7.
Flash update the downloaded Sun System Firmware image:

-> load -source /SP/firmware/localimage

NOTE: An upgrade takes several minutes to complete. ILOM
will enter a special mode to load new firmware. No
other tasks can be performed in ILOM until the
firmware upgrade is complete and ILOM is reset.
Are you sure you want to load the specified file (y/n)? y
Preserve existing configuration (y/n)? y
When the update has finished the following message will appear:
Firmware update is complete.
ILOM will now be restarted with the new firmware.
-> /sbin/reboot
8.
Wait about 5 minutes until ILOM is restarted and re-establish SSH connection to ILOM:

...
->
9.
Power on the server:

-> start /SYS

Starting /SYS
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 106/122
Wait about 15 minutes until Operating System is booted.

10.

-> exit
TROUBLESHOOTING
If the following message appears during starting operating system, ignore it:
-> start /SYS
start: Target already started
FINAL STATUS
The OBP version on T3-2 server has been updated.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 107/122
CONNECTING ETHERNET CABLES OF VIRTUAL

WORKSTATIONS ON T3-2 SERVER
SCOPE
This sheet is intended to help you to connect Ethernet cables on Oracle SPARC T3-2 server.
INPUT PARAMETERS
None.
INITIAL STATUS
There is an Oracle SPARC T3-2 server with 2 Ethernet boards and 8 Ethernet cables (one cable
has been already connected to the igb0 port).
ACTIONS
1.
Connect the Ethernet cables from your network switch or hub to Ethernet Ports: igb1, igb2, igb3,
nxge1, nxge2 on the rear of the chassis.
Note: The Ethernet ports igb1, igb2, igb3, nxge1, nxge2 are used by the virtual workstations;
the port nxge0 is an additional port for hardened mode on the control domain.
The following table describes a correspondence between Ethernet Ports and virtual workstations
numbers (one port per two virtual workstations):
Ethernet Port
Virtual workstation number
igb1
igb2
igb3
nxge1
nxge2
1 and 2
3 and 4
5 and 6
7 and 8
9 and 10
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 108/122
TROUBLESHOOTING
None.
FINAL STATUS
The Ethernet cables have been connected to the Ethernet boards.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 109/122
RESTARTING OMC-R APPLICATION

SCOPE
The purpose of this sheet is to help you start the OMC-R application on an OMC-R server or OMC-R
workstation.
INPUT PARAMETERS
args
Arguments of the command tool; may include the following options:

[-nodbcc]
No database check performed
[-S]
The OMC-R is started on the OMC-R server; on OMC-R server with a
graphic display, it displays the OMC-R startup supervision window
without confirmation
none
A confirmation message will appear:
"Do you want to supervise the OMC-R starting?" offering you three
options: Yes, No and Cancel. Choose Yes.
INITIAL STATUS
An omc session is available on the computer to restart.
ACTIONS
1.
Open a new shell session of the omc account, on the computer to restart.
2.
Run the starting script on the computer to restart (on the OMC-R server or on the
OMC-R workstation).
Type at the command prompt of the omc account shell on the computer to
restart:
... (omc) % /usr/local/oam/bin/ds_startOmc.sh [args]
TROUBLESHOOTING
1.
The log file of the OMC-R application starting is /CMN/base/diagnostic/diag_init.
2.
The history log file (including all OMC-R computer starts and stops) for the OMC-R
computer is /CMN/base/diagnostic/diag_restart_omc.
FINAL STATUS
The OMC-R application is now running on OMC-R server or on the OMC-R workstation.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 110/122
SETTING OPEN BOOT PROM PARAMETER

PRESENTATION
The purpose of this sheet is to set specified Open Boot PROM parameter.
INPUT PARAMETERS
parameter
value
a name of the Open Boot PROM parameter to be set up

a value that corresponds to the parameter
INITIAL STATUS
The computer is in OPB mode.
ACTIONS
1.
Set required OBP parameter:

... ok setenv <parameter> <value>
TROUBLE SHOOTING
None
FINAL STATUS
The specified Open Boot PROM parameter has been set up.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 111/122
SETTING OS HARDENED MODE

SCOPE
The purpose of this sheet is to help you to configure the Operating System hardened mode on the
OMC-R computer.
INPUT PARAMETERS
action
check | activate | deactivate | resume

Check action is available only for OMC-R V17 or greater.
INITIAL STATUS
The OMC-R application is running or not.
A root session is available on the OMC-R computer.
Before activating the OS hardened mode for all functions or activate OS hardened
mode for NFS function only, leave all automounted file systems inactive for 10 minutes
(default value for automount), so the automounter can unmount them.
ACTIONS
ON THE OMC-R COMPUTER

1.
If not already done, open a root shell session on the computer.
2.
If (action = activate) or (action = resume)

2.1
Check that there are no the automounted file systems:

# cd /
# /usr/bin/ls /net
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 112/122
2.2
If there arent any file systems mounted in /net, continue from step 3.
If some file systems are present, check that they are not busy:
# cd /
# /usr/sbin/fuser /net/*
/net/<IP/hostname>:
<Process ID list>
...
# /usr/sbin/fuser -c /net/*/*
/net/<IP/hostname>/<share name>:
...
2.3
<Process ID list>
If <Process ID list> is not empty, it means that some processes are using
automounted file systems. Close all the processes or make them release the
automounted file system.
Note: to check that the automounted file systems are released, repeat step 2.2
2.4
3.
Wait 10 minutes while the automounter can unmount them.
Run the tool with arguments corresponding to required action:

Action
check
activate
deactivate
Args
-check
-harden
-unharden
resume
-harden savgrp
Purpose
to check OS hardened mode
to activate OS hardened mode
to save current OS hardened status and deactivate OS hardened
mode
to activate the OS hardened mode and restore saved
OS hardened status
Also, the following additional options may be used with action argument:
Option
-A
-B<hosts list>
Description
Specifies that action will be performed on all OMC-R hosts
Specifies list of OMC-R hosts where operation will be performed.
Hostnames are separated by space symbol in a list.
For example, -Bhost#1 host#2 host#3
# /usr/local/SECURITY/bin/set_os_hardened.sh [option] <args>

...
OK
Note: After activation of OS hardened mode all user authentication related messages will be written
to the /var/log/inetdlog file.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 113/122
TROUBLESHOOTING
1.
The log file for the tool is /usr/local/SECURITY/log/set_os_hardened.log.

The optional log files are:
/usr/local/SECURITY/log/set_os_hardened.log1
2.
For more information about tools options and usage, use the following command:
# /usr/local/SECURITY/bin/set_os_hardened.sh -H
3.
If some warnings like below are displayed:

...
fix-modes: WARNING: Can't find required uid/gid uucp
...
fix-modes: WARNING: Incomplete entry at
...
Ignore them if the result for the function FIX-MODES is OK.
FINAL STATUS
The OS hardened mode is configured.
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 114/122
18. ANNEXES
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 115/122
SUPPORTED TIMEZONES
SCOPE
This sheet provides the information about the supported TIMEZONEs.
Note: The traditional Solaris meaning of TZ=GMT+n is "The name of my timezone is 'GMT', and my
timezone is n hours behind GMT/UTC, and there is no daylight savings time.
For TZ=GMT-n it is The name of my timezone is GMT, and my timezone is n hours ahead
GMT/UTC, and there is no daylight savings time.
Africa
America/Whitehorse
Europe/Brussels
Africa/Abidjan
America/Santiago
Europe/Bucharest
Africa/Accra
America/Tijuana
Europe/Budapest
Africa/Addis_Ababa
America/Ensenada
Europe/Copenhagen
Africa/Algiers
America/Mazatlan
Europe/Gibraltar
Africa/Bangui
America/Mexico_City
Europe/Kaliningrad
Africa/Banjul
America/Anchorage
Europe/Kiev
Africa/Bissau
America/Adak
Europe/Luxembourg
Africa/Blantyre
America/Atka
Europe/Madrid
Africa/Brazzaville
America/Phoenix
Europe/Malta
Africa/Bujumbura
America/Chicago
Europe/Minsk
Africa/Casablanca
America/Fort_Wayne
Europe/Monaco
Africa/Ceuta
America/Indianapolis
Europe/Oslo
Africa/Conakry
America/New_York
Europe/Paris
Africa/Dakar
America/Knox_IN
Europe/Riga
Africa/Dar_es_Salaam
America/Detroit
Europe/Samara
Africa/Djibouti
America/Los_Angeles
Europe/Simferopol
Africa/Douala
America/Havana
Europe/Sofia
Africa/El_Aaiun
America/Jamaica
Europe/Stockholm
Africa/Freetown
America/Denver
Europe/Tallinn
Africa/Gaborone
America/Shiprock
Europe/Tirane
Africa/Harare
Antarctica
Europe/Uzhgorod
Africa/Johannesburg
Antarctica/Casey
Europe/Vaduz
Africa/Kampala
Antarctica/Davis
Europe/Vienna
Africa/Khartoum
Antarctica/DumontDUrville Europe/Vilnius
Africa/Kigali
Antarctica/Mawson
Europe/Volgograd
Africa/Kinshasa
Antarctica/Palmer
Europe/Zaporozhye
Africa/Lagos
Antarctica/Rothera
Europe/Zurich
Africa/Libreville
Antarctica/Syowa
Europe/Prague
Africa/Lome
Antarctica/Vostok
Europe/Bratislava
Africa/Luanda
Antarctica/McMurdo
Europe/Helsinki
Africa/Lubumbashi
Antarctica/South_Pole
Europe/Mariehamn
Africa/Lusaka
Arctic
Europe/Nicosia
Africa/Malabo
Arctic/Longyearbyen
Europe/Chisinau
Africa/Maputo
Asia
Europe/Tiraspol
Africa/Maseru
Asia/Aden
Europe/Rome
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 116/122

Africa/Mbabane
Asia/Almaty
Europe/San_Marino
Africa/Mogadishu
Asia/Amman
Europe/Vatican
Africa/Monrovia
Asia/Anadyr
Europe/Belgrade
Africa/Nairobi
Asia/Aqtau
Europe/Ljubljana
Africa/Ndjamena
Asia/Aqtobe
Europe/Podgorica
Africa/Niamey
Asia/Baghdad
Europe/Sarajevo
Africa/Nouakchott
Asia/Bahrain
Europe/Skopje
Africa/Ouagadougou
Asia/Baku
Europe/Zagreb
Africa/Porto-Novo
Asia/Bangkok
Europe/Dublin
Africa/Sao_Tome
Asia/Beirut
Europe/London
Africa/Tunis
Asia/Bishkek
Europe/Belfast
Africa/Windhoek
Asia/Brunei
Europe/Guernsey
Africa/Asmara
Asia/Choibalsan
Europe/Isle_of_Man
Africa/Asmera
Asia/Colombo
Europe/Jersey
Africa/Bamako
Asia/Damascus
Europe/Warsaw
Africa/Timbuktu
Asia/Dili
Europe/Lisbon
Africa/Cairo
Asia/Dubai
Europe/Istanbul
Africa/Tripoli
Asia/Dushanbe
Europe/Moscow
America
Asia/Gaza
Factory
America/Argentina
Asia/Harbin
GB
America/Argentina/La_Rioja
Asia/Hovd
GB-Eire
America/Argentina/Rio_Gallegos Asia/Irkutsk
GMT
America/Argentina/San_Juan
Asia/Jakarta
GMT+0
America/Argentina/Tucuman
Asia/Jayapura
GMT+1
America/Argentina/Ushuaia
Asia/Kabul
GMT+10
America/Argentina/San_Luis
Asia/Kamchatka
GMT+11
America/Argentina/Salta
Asia/Karachi
GMT+12
America/Argentina/Buenos_Aires Asia/Kashgar
GMT+2
America/Argentina/Catamarca
GMT+3
Asia/Katmandu
America/Argentina/ComodRivadavia
Asia/Krasnoyarsk
GMT+4
America/Argentina/Jujuy
Asia/Kuala_Lumpur
GMT+5
America/Argentina/Mendoza
Asia/Kuching
GMT+6
America/Argentina/Cordoba
Asia/Kuwait
GMT+7
America/Indiana
Asia/Magadan
GMT+8
America/Indiana/Marengo
Asia/Manila
GMT+9
America/Indiana/Petersburg
Asia/Muscat
GMT-0
America/Indiana/Vevay
Asia/Novosibirsk
GMT-1
America/Indiana/Vincennes
Asia/Omsk
GMT-10
America/Indiana/Winamac
Asia/Oral
GMT-11
America/Indiana/Tell_City
Asia/Phnom_Penh
GMT-12
America/Indiana/Indianapolis
Asia/Pontianak
GMT-13
America/Indiana/Knox
Asia/Pyongyang
GMT-14
America/Kentucky
Asia/Qatar
GMT-2
America/Kentucky/Monticello
Asia/Qyzylorda
GMT-3
America/Kentucky/Louisville
Asia/Rangoon
GMT-4
America/North_Dakota
Asia/Riyadh
GMT-5
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 117/122

America/North_Dakota/Center
Asia/Sakhalin
GMT-6
America/North_Dakota/New_Salem Asia/Samarkand
GMT-7
America/Anguilla
Asia/Taipei
GMT-8
America/Antigua
Asia/Tashkent
GMT-9
America/Araguaina
Asia/Tbilisi
GMT0
America/Aruba
Asia/Urumqi
Greenwich
America/Asuncion
Asia/Vientiane
HST
America/Bahia
Asia/Vladivostok
Hongkong
America/Barbados
Asia/Yakutsk
Iceland
America/Belem
Asia/Yekaterinburg
Indian
America/Belize
Asia/Yerevan
Indian/Antananarivo
America/Blanc-Sablon
Asia/Ashgabat
Indian/Chagos
America/Boa_Vista
Asia/Ashkhabad
Indian/Christmas
America/Bogota
Asia/Chongqing
Indian/Cocos
America/Boise
Asia/Chungking
Indian/Comoro
America/Cambridge_Bay
Asia/Dhaka
Indian/Kerguelen
America/Campo_Grande
Asia/Dacca
Indian/Mahe
America/Cancun
Asia/Macau
Indian/Maldives
America/Caracas
Asia/Macao
Indian/Mauritius
America/Cayenne
Asia/Thimphu
Indian/Mayotte
America/Cayman
Asia/Thimbu
Indian/Reunion
America/Chihuahua
Asia/Makassar
Iran
America/Costa_Rica
Asia/Ujung_Pandang
Israel
America/Cuiaba
Asia/Ulaanbaatar
Jamaica
America/Curacao
Asia/Ulan_Bator
Japan
America/Danmarkshavn
Asia/Saigon
Kwajalein
America/Dawson
Asia/Ho_Chi_Minh
Libya
America/Dawson_Creek
Asia/Calcutta
MET
America/Dominica
Asia/Kolkata
MST
America/Eirunepe
Asia/Nicosia
MST7MDT
America/El_Salvador
Asia/Riyadh87
Mexico
America/Fortaleza
Asia/Riyadh88
Mexico/BajaNorte
America/Glace_Bay
Asia/Riyadh89
Mexico/BajaSur
America/Godthab
Asia/Hong_Kong
Mexico/General
America/Goose_Bay
Asia/Tehran
Mideast
America/Grand_Turk
Asia/Jerusalem
Mideast/Riyadh87
America/Grenada
Asia/Tel_Aviv
Mideast/Riyadh88
America/Guatemala
Asia/Tokyo
Mideast/Riyadh89
America/Guayaquil
Asia/Shanghai
NZ
America/Guyana
Asia/Seoul
NZ-CHAT
America/Hermosillo
Asia/Singapore
Navajo
America/Inuvik
Asia/Istanbul
PRC
America/Iqaluit
Atlantic
PST8PDT
America/Juneau
Atlantic/Azores
Pacific
America/La_Paz
Atlantic/Bermuda
Pacific/Apia
America/Lima
Atlantic/Canary
Pacific/Easter
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 118/122

America/Maceio
Atlantic/Cape_Verde
Pacific/Efate
America/Managua
Atlantic/Madeira
Pacific/Enderbury
America/Martinique
Atlantic/South_Georgia
Pacific/Fakaofo
America/Menominee
Atlantic/St_Helena
Pacific/Fiji
America/Merida
Atlantic/Stanley
Pacific/Funafuti
America/Moncton
Atlantic/Faroe
Pacific/Galapagos
America/Miquelon
Atlantic/Faeroe
Pacific/Gambier
America/Monterrey
Atlantic/Jan_Mayen
Pacific/Guadalcanal
America/Montevideo
Atlantic/Reykjavik
Pacific/Guam
America/Montreal
Australia
Pacific/Johnston
America/Montserrat
Australia/Currie
Pacific/Kiritimati
America/Nassau
Australia/Eucla
Pacific/Kosrae
America/Nipigon
Australia/Lindeman
Pacific/Majuro
America/Nome
Australia/Lord_Howe
Pacific/Marquesas
America/Panama
Australia/LHI
Pacific/Midway
America/Pangnirtung
Australia/Sydney
Pacific/Nauru
America/Paramaribo
Australia/ACT
Pacific/Niue
America/Port-au-Prince
Australia/Canberra
Pacific/Norfolk
America/Port_of_Spain
Australia/NSW
Pacific/Noumea
America/Porto_Velho
Australia/Darwin
Pacific/Palau
America/Puerto_Rico
Australia/North
Pacific/Pitcairn
America/Rainy_River
Australia/Brisbane
Pacific/Ponape
America/Rankin_Inlet
Australia/Queensland
Pacific/Port_Moresby
America/Recife
Australia/Adelaide
Pacific/Rarotonga
America/Resolute
Australia/South
Pacific/Saipan
America/Santo_Domingo
Australia/Hobart
Pacific/Yap
America/Scoresbysund
Australia/Tasmania
Pacific/Tahiti
America/St_Kitts
Australia/Melbourne
Pacific/Tarawa
America/St_Lucia
Australia/Victoria
Pacific/Tongatapu
America/St_Vincent
Australia/Perth
Pacific/Truk
America/Swift_Current
Australia/West
Pacific/Wake
America/Tegucigalpa
Australia/Broken_Hill
Pacific/Wallis
America/Thule
Australia/Yancowinna
Pacific/Honolulu
America/Thunder_Bay
Brazil
Pacific/Pago_Pago
America/Tortola
Brazil/Acre
Pacific/Samoa
America/Yakutat
Brazil/DeNoronha
Pacific/Kwajalein
America/Yellowknife
Brazil/East
Pacific/Auckland
America/Buenos_Aires
Brazil/West
Pacific/Chatham
America/Catamarca
CET
Poland
America/Atikokan
CST6CDT
Portugal
America/Coral_Harbour
Canada
ROK
America/Jujuy
Canada/Atlantic
Singapore
America/Louisville
Canada/Central
Turkey
America/Mendoza
Canada/Eastern
UCT
America/Cordoba
Canada/Mountain
US
America/Rosario
Canada/Newfoundland
US/Alaska
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 119/122

America/St_Thomas
Canada/Pacific
US/Aleutian
America/Virgin
Canada/East-Saskatchewan
US/Arizona
America/Guadeloupe
Canada/Saskatchewan
US/Central
America/Marigot
Canada/Yukon
US/East-Indiana
America/St_Barthelemy
Chile
US/Eastern
America/Santarem
Chile/Continental
US/Hawaii
America/Rio_Branco
Chile/EasterIsland
US/Indiana-Starke
America/Porto_Acre
Cuba
US/Michigan
America/Noronha
EET
US/Pacific
America/Sao_Paulo
EST
US/Pacific-New
America/Manaus
EST5EDT
US/Samoa
America/Halifax
Egypt
US/Mountain
America/Winnipeg
Eire
UTC
America/Toronto
Europe
Universal
America/Edmonton
Europe/Amsterdam
W-SU
America/St_Johns
Europe/Andorra
WET
America/Vancouver
Europe/Athens
Zulu
America/Regina
Europe/Berlin
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 120/122
19. ABBREVIATIONS AND DEFINITIONS

19.1. ABBREVIATIONS
CIUS
DVD
DNS
ILOM
GUI
LAN
LDom
Mbps
OBP
OEM
OMC-R
OS
SGD
T5140
T3-2
XLAN
Centralized Installation and Upgrade Service

Digital Versatile
Domain Name System
Integrated Lights Out Manager
Graphical User Interface
Local Area Network (Ethernet)
Logical Domain
Megabit per second (Mbit/s)
Open Boot Prom (processor monitor of Sun computers)
Original Equipment Manufacturers
Operation and Maintenance Centre - Radio part
Operating System
Oracle Secure Global Desktop
Sun SPARC Enterprise T5140 server
Oracle SPARC T3-2 server
eXtended Local Area Network
19.2. DEFINITIONS
Sun SPARC
Enterprise server
Sun SPARC Enterprise T5140 server.
Supervisory
workstation
Sun workstation dedicated to monitor the system

console of a host used without graphic display or
keyboard.
IPMP
A facility provided by the Solaris Operating System to

provide fault-tolerance and load balancing with network
interface cards
(or IP network
multipathing)
at the OBP level
System under the control of the processor monitor. The

operating system is not running, as after a shutdown ( init
0).
T5140 SGD server
Sun SPARC Enterprise T5140 server with installed SGD &

LDOM software on control domain and configured with 6
virtual workstations intended for OMC-R and/or CIUS
workstations
Virtual workstation
Workstation with installed OMC-R and/or CIUS application on

one virtual workstations configured on T5140/T3-2 SGD
server
JumpStart
Sun Microsystems' Solaris JumpStart technology is used to

automate the installation of the Solaris Operating System
and other associated software on multiple nodes of a
network.
Target host
The computer where the SGD & LDOM software will be

installed and configured
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 121/122
END OF DOCUMENT
External document
DS/OMC/APP/024553
05.21 / EN
Standard
22/Feb/2012
Page 122/122

Parameters KCC

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Parameters KCC

Hochgeladen von

Copyright:

Verfügbare Formate

Logical Domains Administration

Copyright 2012 Kapsch CarrierCom France S.A.S, All Rights Reserved

Logical Domains Administration

Logical Domains Administration

Logical Domains Administration

SCOPE OF THIS DOCUMENT .......................................................................................................7

AUDIENCE FOR THIS DOCUMENT ................................................................................................7

RELATED DOCUMENTS ..............................................................................................................8

APPLICABLE DOCUMENTS ..........................................................................................................8

REFERENCE DOCUMENTS ..........................................................................................................8

TYPOGRAPHIC CONVENTIONS .................................................................................................9

SEQUENCE TABLE STRUCTURE ................................................................................................10

GENERAL DESCRIPTION ..........................................................................................................12

PLEASE READ CAREFULLY .......................................................................................................12

ADMINISTRATION TASK MAP ..................................................................................................14

LOGICAL DOMAINS INSTALLATION/CONFIGURATION OVERVIEW ...................................................14

REMOTE ACCESS THROUGH SGD SOFTWARE ...........................................................................14

CONTROL DOMAIN INSTALLATION ........................................................................................17

GENERAL PRE-INSTALLATION TASKS ........................................................................................17

TARGET HOST HARDWARE CHECK ............................................................................................17

STARTING INSTALLATION .........................................................................................................18

CONTROL DOMAIN BACKUP ...................................................................................................20

PRE-BACKUP TASKS ................................................................................................................23

Logical Domains Administration

CONTROL DOMAIN RESTORATION.........................................................................................28

OPERATION DETAILED DESCRIPTION ........................................................................................29

CONTROL DOMAIN REMOVING ...............................................................................................30

CONFIGURING SGD USERS .....................................................................................................31

PRELIMINARY OPERATIONS ......................................................................................................31

CREATING SGD USER .............................................................................................................31

REMOVING SGD USER ............................................................................................................32

ADDING LOCAL DOMAINS TO SGD USERS PROFILE ...................................................................32

REMOVING LOCAL DOMAINS FROM SGD USERS PROFILE ..........................................................33

LIST LOCAL DOMAINS IN SGD USERS PROFILE .........................................................................33

CHANGING PASSWORD FOR SGD USER ...................................................................................33

WORKING WITH THE VIRTUAL WORKSTATION ....................................................................35

CONNECTING TO THE VIRTUAL WORKSTATION ...........................................................................35

DISCONNECTING FROM THE VIRTUAL WORKSTATION..................................................................36

SUSPENDING VIRTUAL WORKSTATION WEB-SESSION .................................................................36

RESUMING VIRTUAL WORKSTATION WEB-SESSION.....................................................................36

ENTERING OBP MODE ON THE VIRTUAL WORKSTATION .............................................................37

EXPORTING CIUS DVD IMAGES TO THE VIRTUAL WORKSTATION ...................................38

GETTING MAC-ADDRESS FOR THE VIRTUAL WORKSTATION ...........................................39

UPDATING TARGET HOST SYSTEM FIRMWARE VERSION .................................................40

UPDATING OBP VERSION FOR T5140 SERVER .........................................................................40

UPDATING OBP VERSION FOR T3-2 SERVER ............................................................................41

CONFIGURING/DECONFIGURING DNS CLIENT ON CONTROL DOMAIN ............................42

CONFIGURING DNS CLIENT .....................................................................................................42

DECONFIGURING DNS CLIENT .................................................................................................42

SECURE MODE ACTIVATION .....................................................................................................43

CHECKING SSH SERVICE ........................................................................................................43

NON-SECURE MODE ACTIVATION ..............................................................................................43

Logical Domains Administration

ABBREVIATIONS AND DEFINITIONS .....................................................................................121

Logical Domains Administration

SCOPE OF THIS DOCUMENT

AUDIENCE FOR THIS DOCUMENT

Logical Domains Administration

DS/OMC/APP/000001 OMC-R OEM equipment installation procedure

DS/OMC/APP/000003 OMC-R Software Installation Procedure

DS/OMC/APP/000016 OMC-R Preventive Maintenance Backup

DS/OMC/APP/000017 OMC-R System Global Restoration

DS/OMC/APP/000019 OMC-R customization parameter notebook

DS/OMC/APP/020095 OMC-R Post-installation Configuration Procedure