Dsomcapp000016 1111e

OMC-R Preventive Maintenance Backup
Document number: DS/OMC/APP/000016

Document issue: 11.11 / EN
Document status: Standard
Date: 20/Jun/2007
External document
Copyright© 2006-2007 Nortel Networks, All Rights Reserved
Printed in France
NORTEL CONFIDENTIAL
The information contained in this document is the property of Nortel Networks. Except as specifically authorized in
writing by Nortel Networks, 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 Nortel Networks as to the content or accuracy of the information
contained herein, including but not limited to the suitability and performances of the product or its intended
application.
This is the Way. This is Nortel, Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks. All
other trademarks are the property of their owners.
PUBLICATION HISTORY
20/Jun/2007
Issue 11.11/ EN, Standard
CR Q01663209-01
01/Sep/2006
CR Q01439578 Q01437179
17/Aug/2006
CR Q01437130
28/Jul/2006
CR Q01422102
26/Jul/2006
CR Q01415474 Q01418608-01
20/Jul/2006
CR Q01416294
18/Jul/2006
CR Q01403802 Q01405343-01
07/Jul/2006
CR Q01405806
22/Jun/2006
CR Q01392901 Q01395592
23/May/2006
Feature 28022 “Backup and restoration on DVD”
19/May/2006
Nortel Networks confidential
DS/OMC/APP/000016 11.11 / EN Standard 20/Jun/2007 Page 2/84

Merged CR Q01368197
Feature 29547 “Terminal Server Specification”
Created for v16.0_chr on the basis of DS/OMC/APP/16 v10.20

CONTENTS
1. INTRODUCTION............................................................................................................................6
1.1. OBJECT ....................................................................................................................................6
1.2. SCOPE .....................................................................................................................................6
2. RELATED DOCUMENTS ..............................................................................................................7

2.1. APPLICABLE DOCUMENTS ..........................................................................................................7
2.2. REFERENCE DOCUMENTS ..........................................................................................................7
3. TYPOGRAPHIC CONVENTIONS .................................................................................................8

3.1. GENERAL CONVENTIONS ...........................................................................................................8
3.1.1 Interactive terminal sessions...........................................................................................8
3.1.2 Interactive graphic sessions............................................................................................9
3.2. SEQUENCE TABLE CONVENTION .................................................................................................9
4. GENERAL DESCRIPTION ..........................................................................................................11

4.1. PLEASE READ CAREFULLY .......................................................................................................11
4.2. OMC-R FILE SYSTEM BACKUP ON DAT....................................................................................11
4.2.1 Prerequisites .................................................................................................................11
4.2.2 Resources .....................................................................................................................11
4.2.3 Overview .......................................................................................................................12
4.2.4 Archiving description .....................................................................................................12
4.2.5 Interval...........................................................................................................................13
4.2.6 System impact...............................................................................................................13
4.3. OMC-R FILE SYSTEM BACKUP ON DVD ...................................................................................13
4.3.1 Prerequisites .................................................................................................................13
4.3.2 Resources .....................................................................................................................13
4.3.3 Overview .......................................................................................................................14
4.3.5 Interval...........................................................................................................................14
4.3.6 System impact...............................................................................................................14
4.4. OMC-R ENVIRONMENT DATA ARCHIVING ..................................................................................14
4.4.1 Prerequisites .................................................................................................................14
4.4.2 Resources .....................................................................................................................15
4.4.3 Overview .......................................................................................................................15
4.4.5 Interval...........................................................................................................................16
4.4.6 System impact...............................................................................................................16
4.5. OMC-R DAILY DATA ARCHIVING ...............................................................................................16
4.5.1 Prerequisites .................................................................................................................16
4.5.2 Resources .....................................................................................................................16
4.5.3 Overview .......................................................................................................................17
4.5.5 Interval...........................................................................................................................17
4.5.6 System impact...............................................................................................................18
4.6. PCUOAM CONFIGURATION BACKUP ........................................................................................18
4.6.1 Prerequisites .................................................................................................................18
4.6.2 Resources .....................................................................................................................18
4.6.3 Overview .......................................................................................................................18

4.6.5 Interval...........................................................................................................................19
4.6.6 System impact...............................................................................................................19
4.7. SYNTHESIS .............................................................................................................................19
5. PRE-BACKUP TASKS ................................................................................................................20
6. OPERATION DETAILED DESCRIPTION ...................................................................................21

6.1. OMC-R FILE SYSTEM BACKUP .................................................................................................21
6.1.1 Server file system backup .............................................................................................21
6.1.1.1. FOR A DUAL OMC-R SERVERS CONFIGURATION ............................................. 21
6.1.1.2. FOR A SINGLE/INTEGRATED OMC-R SERVER CONFIGURATION.................... 23
6.1.2 OMC-R/PCUOAM/SDO workstation file system backup ..............................................24
6.1.2.1. U5/SB150/SB1500 FILE SYSTEM BACKUP ON DAT ............................................ 24
6.1.2.2. U45 FILE SYSTEM BACKUP DVD .......................................................................... 24
6.2. OMC-R ENVIRONMENT DATA ARCHIVING ..................................................................................27
6.3. OMC-R DAILY DATA ARCHIVING ...............................................................................................27
6.4. PCUOAM CONFIGURATION BACKUP ........................................................................................28
7. POST OPERATIONS...................................................................................................................29
8. SHEETS .......................................................................................................................................30
XYPLEX DEPORTED CONSOLE OPENING ................................................................. 31
Stopping OMC-R ............................................................................................................. 34
LOCAL FILE SYSTEM BACKUP..................................................................................... 35
DISKS ARRAY DEVICE BACKUP .................................................................................. 39
OS SHUTDOWN / REBOOT / RUN LEVEL CHANGE.................................................... 41
INSTALLING/REMOVING EXTERNAL DAT DRIVE....................................................... 43
XYPLEX DEPORTED CONSOLE CLOSING.................................................................. 46
HOW TO…....................................................................................................................... 47
EXIT AND CLEAN ........................................................................................................... 49
INTER-SERVER SWITCHOVER..................................................................................... 50
starting LOCAL OMC-R APPLICATION .......................................................................... 51
UNIX CONSOLE LOGIN ................................................................................................. 52
DISKS ARRAY DEVICE ASSIGNATION ........................................................................ 53
CHECK FILE SYSTEM FULL .......................................................................................... 54
DISKS ARRAY CHECKING............................................................................................. 55
How to enable AutoStart.................................................................................................. 58
DDS Tape and Drive unit compatibility............................................................................ 59
DISKS ARRAY Checking on SFV880 ............................................................................. 61
DISKS ARRAY Checking on SFV890 ............................................................................. 64
OPERATING SYSTEM BOOT FROM OBP .................................................................... 67
OMC-R DATA ARCHIVING\RESTORING ...................................................................... 68
LX-8020S DEPORTED CONSOLE OPENING ............................................................... 72
LX-8020S CONSOLE CLOSING ..................................................................................... 73
FILE SYSTEM BACKUP ON DVD OPERATIONS.......................................................... 74
DEFINING EXCLUDED AND INCLUDED DATA LISTS WHEN PERFORMING BACKUP
ON DVD ........................................................................................................................... 80
BLANKING DVD-RW MEDIA .......................................................................................... 82
9. ABBREVIATIONS AND DEFINITIONS.......................................................................................83

9.1. ABBREVIATIONS ......................................................................................................................83
9.2. DEFINITIONS ...........................................................................................................................83

1. INTRODUCTION
This procedure is valid for single, dual and integrated server OMC-R
configuration.
1.1. OBJECT
The aim of this document is to describe the different kinds of backup that must be
performed to save data or the OMC-R configuration, the procedures to perform them,
and the scheduling for each of them.
Preventive backup can be performed on following data types:

Unix file system used to save the content of the applicative and system
partitions of an OMC-R computer
OMC-R environment data (i.e. network and OMC-R configuration and also file
system)
OMC-R daily data
PCUOAM configuration backup (MDM and PCUSN configuration files)
SVM configuration backups, disks partitioning, SVM configuration, applicative
tree on file-systems
Each data backup can be restored separately for some particular uses:
Previous daily data consultation (notifications, alarms, ...)
Specific BDE (i.e. network and OMC-R configuration) restoration
For a global restoration, to be done after a major damage for example, the operator
has to use the [A2] procedure.
1.2. SCOPE
This procedure is applicable to OMC-R server(s) in single, integrated or dual
configuration.
This procedure can be run either on an OMC-R workstation or a server, which
hardware configurations can be:
⇒ dual E4500 servers with two T3 disks trays
⇒ single E4500 server with two T3 disks trays
⇒ Sun Fire™ 880 server with two T3 disks trays
⇒ Sun Fire™ 890 server with 12 internal disks (HDI configuration)
This procedure is applicable to OMC-R server(s) with and without a graphic display
and a keyboard alike. Hardware installation issues (e.g. how to add or remove a
graphic display and a keyboard) are explained in the [A1] procedure.

2. RELATED DOCUMENTS
2.1. APPLICABLE DOCUMENTS
[A1] DS/OMC/APP/000001 OMC-R OEM equipment installation procedure
[A2] DS/OMC/APP/000017 OMC-R system global restoration
[A3] DS/OMC/APP/000019 OMC-R customization parameter notebook
[A4] DS/OMC/APP/000003 OMC-R software installation procedure
2.2. REFERENCE DOCUMENTS

[R1] 411-9001-032 Nortel GSM OMC-R Routine Maintenance and
Troubleshooting (NTP32)

3. TYPOGRAPHIC CONVENTIONS
3.1. GENERAL CONVENTIONS
Words in italic style (italic) mean a parameter to substitute by its value.
The following syntax indicates on which computer the actions should be run:
) ON A LOCAL OMC-R WORKSTATION:

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

An interactive session on a terminal can be obtained using two methods:
- Choosing the "Access to Unix" 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.
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 text to pay especial attention to.
Courier New All characters of a terminal session are in Courier New font.
The lines, commands, or parameters entered with the keyboard
Bold
are in bold style.
A variable output display is in italic style. Words in italic have to
Italic
be substituted by real values.
An input parameter, which should be substituted by its value, is
italic-bold
in italic and bold style.
↵ The ENTER key has to be pressed.
[STOP],[a] The STOP and a key have to be pressed simultaneously.
.......... A group of dots replace a certain number of lines.
A command line is truncated and continues on the next line.
% or (user) % The C shell prompt
$ or (user) $ The Bourne and Korn shell prompt
# or (root) # The root super-user prompt in any shell

Terminal session sample:

Under omc login:
/ (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.
3.1.2 INTERACTIVE GRAPHIC SESSIONS

The graphic interactive commands are described with the following syntax:
Convention used Meaning

GOTO « Title » Go to the window named "Title"
Click with the mouse on the buttons or options
SELECT « Save - OK »
named "Save", then "OK".
SELECT_OBJ « omc » Select the object « omc »
SET State = locked Enter with the keyboard the values of the
T2 = 30s parameters
CLOSE « Title » Close the window named "Title"
3.2. SEQUENCE TABLE CONVENTION

For each major step of the procedure, a sequence table lists the operation steps to
perform. Each operation step is described completely in the sheet referenced by its
page number.
A sheet may have to be executed at different stages of the procedure and in different
contexts; for this reason, a set of input parameters for the sheet may indicate the
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 mn) mn Sheet OK /
page NOK
Input Parameters
STATUS COMMENT
S1 Description of the operation 1 30 12 OK
Parameter1 = value
Parameter2 : explanations
Parameter1 = value
Maximum elapsed time of the operation step

Name and value of input para-
meters of the sheet (optional
or « none » for no argument) 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 can not be continued without any investigation.

4. GENERAL DESCRIPTION
4.1. PLEASE READ CAREFULLY
Despite the utmost care taken to preclude any chance of undesirable events during
this procedure it is impossible to foresee all possible happenings. Therefore, if you
face a problem or a situation that the procedure does not cover in an explicit and
accurate manner, call for assistance.
Before executing this procedure, ask your support about any special actions
(workarounds, patches...) to be undertaken prior to and after the procedure.
4.2. OMC-R FILE SYSTEM BACKUP ON DAT

This type of backup is applicable for OMC-R servers and SB1500/SB150/U5
workstations.
4.2.1 PREREQUISITES
Passwords for root and croot user.
4.2.2 RESOURCES
One technician, familiar with the UNIX system and OMC-R commands
A DAT drive is required on the computer to back up (an external DAT drive on
OMC-R workstation)
Generally one DAT cartridge per computer to back up the file systems.
Quantity of the tapes depends on size of the file systems and the type of the
tape being used
One DAT cartridge to back up the SVM configuration
One DAT cartridge for environment and daily data backup
One DAT cartridge for PCUOAM configuration backup
Please use the following tapes depending on DAT drive you have on a
computer:
• For DDS-3 DAT drive: DDS-3 (125m) tape.
Please don’t use DDS-1 (60m) tape as it may not suffice
• For DDS-4 DAT drive: DDS-4 (150m) tape

• For DAT 72 drive: DAT 72 (170m) tape

Please refer to the sheet “DDS TAPE AND DRIVE UNIT COMPATIBILITY”
(page 59) to find more information about tapes and drives compatibility.
4.2.3 OVERVIEW
This backup is necessary for saving the file system of OMC-R computers. This backup
doesn’t manage the OMC-R environment data (saved on raw devices), and therefore
is not sufficient for a complete OMC-R restoration (a database reinstallation is
necessary).
4.2.4 ARCHIVING DESCRIPTION

The backup must be performed by the UNIX root user while the OMC-R is stopped.
The system (OMC-R server or OMC-R workstation) will be put in single-user mode to
perform the complete backup and then in multi-user mode if a backup of the disks
array device is performed.
The backup can be performed on an OMC-R server or an OMC-R workstation. For
workstation, a DAT drive must be connected to the workstation itself, no remote DAT
drive can be used.
Four types of backup are defined:
System backup : system partitions (/, /usr, /var, /opt and /home) are dumped
Local application backup: applicative partitions (/MD/base, /OMC/base,

/CMN/base, /misc (/MISCELLANEOUS for Integrated configuration)) are
dumped
Complete backup : system partitions and applicative partitions are dumped
Disks array device backup: this backup applies to disks that are located in a
disks array device (T3 or HDI). It only saves disks partitioning, SVM
configuration and applicative tree on file-systems. It does not save file-
systems built on disks of the disks array device; all data residing on
those file-systems are saved using OMC-R environment and daily data
archiving tool. So, environment and daily data archiving is mandatory to
complete the backup of disks array device.
Only one backup can be performed on a DAT cartridge (no label is necessary).
If interrupted, a backup can be run again, but the data stored on the DAT cartridge
before the interruption cannot be restored.
A complete backup of a computer can only be restored on the computer with
the same disks configuration.
A backup of disks array device can be only restored on the active/integrated
server.

4.2.5 INTERVAL
A file system backup should be performed on an OMC-R computer before and after
each major change in the OMC-R installation and configuration, for example:
OMC-R installation on a server or an OMC-R workstation
OMC-R upgrade on a server or an OMC-R workstation
Disk substitution on a server or an OMC-R workstation
MDM installation
This type of backup is necessary when performing a global restoration

procedure on a system as described in the [A2] document, after any major
sinister.
4.2.6 SYSTEM IMPACT

The OMC-R application must be stopped on the local host.
The operation can last up to several hours depending on the size of data to be saved
and the type of tape drive being used.
4.3. OMC-R FILE SYSTEM BACKUP ON DVD

This type of backup is applicable for Sun Ultra™ 45 workstations only.
4.3.1 PREREQUISITES
Passwords for root and croot user.
4.3.2 RESOURCES
A DVD-RW drive is required on the U45 workstation to back up
Certain number of DVD disks is required to back up file systems of the U45
workstation. Generally:
o 1 DVD disk if the role of the U45 workstation is STATION
o 2 DVD disks if the role of the U45 workstation is CIUS

However, real quantity of the disks depends on size of the file systems
Please use the following types of DVD media:

• DVD+RW 4x
• DVD-RW 4x

• DVD+R 4x-8x
• DVD-R 4x-8x
Other types of DVD cannot be used.
4.3.3 OVERVIEW
This backup is necessary for saving the file system of U45 workstation. This backup is
not applicable to computers with any other hardware architecture.

The backup includes two main steps: “creating images” and “burning images”. The
“creating images” step must be performed by the UNIX root user while the OMC-R is
stopped. The system will be put in single-user mode to create DVD images and then
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.
During the backup, partitions /, /var, /OMC/maps, /OMC and /home are dumped.
4.3.5 INTERVAL
A file system backup should be performed on an OMC-R computer before and after
each major change in the OMC-R installation and configuration, for example:
OMC-R installation on an U45 workstation

OMC-R upgrade on an U45 workstation
Disk substitution on an U45 workstation
This type of backup is necessary when performing a global restoration

procedure on a system as described in the [A2] document, after any major
sinister accident.
4.3.6 SYSTEM IMPACT

The OMC-R application must be stopped during the “Creating images” step on
the local host.
The operation can last up to several hours depending on the size of data to be saved.
4.4. OMC-R ENVIRONMENT DATA ARCHIVING
4.4.1 PREREQUISITES
Password for OMC-R user administrator.

4.4.2 RESOURCES
One DAT cartridge (if not using a backup server as the backup media)
Please use the following tapes depending on DAT drive you have on a computer:


Please refer to the sheet “DDS TAPE AND DRIVE UNIT COMPATIBILITY” (page
59) to find more information about tapes and drives compatibility.
4.4.3 OVERVIEW
This backup deals with the OMC-R environment data (the network and the OMC-R
configuration data).
The permanent data saved are collection of files containing parameters to configure
the OMC-R application, and databases containing the network description. This
backup is usually called the BDE backup.
This type of backup must be systematically performed after a backup of disks

array device.

This operation can only be performed on the active server.
The OMC-R must be running while performing the OMC-R environment data backup.
Following data will be backed up:

MD-R data : Event Forwarding Discriminators, mdWarning, configuration files
(Purge configuration, MMI configuration, applicative communication layers
configuration, synthetic counters...), applicative tables of the mediation device
database, Management Information Tree
Manager data : operator or NORTEL synthetic counters formulas, command
files, user and terminal profiles, applicative tables of the manager database
Common data : configuration parameters of the SYBASE system databases
and common functions
None of the data saved by this backup may be purged by the OMC-R.
The data can be backed up either:

On a labelled DAT cartridge (into the DAT drive of the active server)
On a mounted file system handled by a backup server
See [R1] for details of how to deal with each of the backup media types.
Several backups can be performed on the media. Note that if a backup is aborted
because there is no more space left on the media, the data being saved cannot be
restored, but the other backups (if any) on the media are not damaged.
The DAT cartridge must be labelled before performing any backup on it.
4.4.5 INTERVAL
Several factors determine how often you should perform the backup at your site. For
example, you should perform this procedure before and after each of the following
operations:
OMC-R and BSS upgrade
Network extension
Frequency plan change
This type of backup should be done, at least, once a week.
4.4.6 SYSTEM IMPACT

and the type of tape drive being used. The OMC-R doesn’t have to be stopped.
No commands that modify the OMC-R environment database (BDE) are

permitted during the backup.
4.5. OMC-R DAILY DATA ARCHIVING
4.5.1 PREREQUISITES
Passwords for OMC-R administrator.
4.5.2 RESOURCES

computer:
4.5.3 OVERVIEW
The aim of this backup is to save daily data (observations, alarms...) before they are
purged, in order to restore them for later consultation.
This backup deals with the data collected during the last four days.
Data of the day when the backup is performed are not saved.

This operation can only be performed on the active server.
The OMC-R must be running while performing the OMC-R daily data backup.
The following data are backed up:
Performance Management data (observation counters, call trace and call path
trace results)
Fault Management data (fault notifications)
Other data (system session logs, job results, user mail)
This backup deals only with data, which are purged by the OMC-R.
On a labelled DAT cartridge

4.5.5 INTERVAL
Archiving is required every fourth day after 0:00 am.

Remember that the data concerned by the archiving operation are purged after a few
days, depending on the customer configuration (default value is 3 days). Therefore,
they must be saved before they are purged, otherwise they are definitively lost.
4.5.6 SYSTEM IMPACT

and the type of tape drive being used.
4.6. PCUOAM CONFIGURATION BACKUP
4.6.1 PREREQUISITES
Passwords for OMC-R administrator.
4.6.2 RESOURCES
computer:

4.6.3 OVERVIEW
This backup deals with MDM software configuration files and PCUSN view files.

This operation can only be performed on the OMC-R server (on active server in case
of single or dual OMC-R configuration).
The OMC-R must be running on both the active server and the PCUOAM workstation
(in case of single or dual OMC-R configuration) or on the integrated server (in case of
integrated OMC-R configuration).
The following data are backed up:

MDM software configuration files

PCUSN configuration and view files
On a labelled DAT cartridge

4.6.5 INTERVAL
Several factors determine how often you should perform the backup at your site. For
example, you should perform this procedure before and after each major change on
the PCUOAM workstation of the following operations:
PCUOAM workstation installation
MDM installation, upgrade or patch application

OMC-R installation, upgrade or patch application
Disk substitution
Network extension
Disaster plan
4.6.6 SYSTEM IMPACT

None.
4.7. SYNTHESIS
An OMC-R backup consists of:
One File System DAT cartridge per computer to back up,
One Disks array Device DAT cartridge,
One Environment Data DAT cartridge,
One Daily Data DAT cartridge.
One PCUOAM configuration DAT cartridge.
If there is an Ultra-45 workstation in the configuration, a number of DVD disks.

5. PRE-BACKUP TASKS
This operation is the first one for any operation described in this document.
The pre-backup tasks can be run out the day before the maintenance backup.
Step | Operation description (Total 16 min) mn Sheet OK /

page NOK
Input Parameters
BEGINNING OF PRE-BACKUP TASKS

S1 How to… 3 47
S2 If the OMC-R computer is used without graphic display or keyboard 5
AND if not already done, open a telnet session to the Terminal server
port on which the OMC-R computer (whose system console is
supervised) is connected, from the supervisory workstation:
• If Xyplex Terminal server is used 31
terminal_server_hostname = Xyplex host name, refer to

[A3]
port_number: port number of the connected server
• If LX-8020S Terminal server is used 72

terminal_server_hostname = LX-8020S host name, refer to
[A3]
S3 Check if a file system is full 3 54
S4 Check compatibility between DDS tapes and drives you use 3 59
S5 For each OMC-R computer with activated “OS hardened” mode, 2 [A4]
deactivate “OS hardened” mode
END OF PRE-BACKUP TASKS

6. OPERATION DETAILED DESCRIPTION

6.1. OMC-R FILE SYSTEM BACKUP
6.1.1 SERVER FILE SYSTEM BACKUP

The aim is to back up the local file system on the server and the disks array device
configuration (disks partitioning, SVM configuration, applicative tree on file-systems).
The backup of disks array device does not dump any file-system; it must be
completed by issuing the environment AND daily data archiving described
respectively in chapters § 6.2 and § 6.3.
6.1.1.1. FOR A DUAL OMC-R SERVERS CONFIGURATION
Step | Operation description (Total 143 + * min) min Sheet OK /

page NOK
Input Parameters
THE OMC-R IS RUNNING ON THE ACTIVE SERVER
S6 Check the disks array devices 5 55
S7 Switch the OMC-R on the preferential active server 30 50
S8 Shut down the operating system on the preferential active server 2 41
run_level = 0
THE OMC-R IS RUNNING ON THE PASSIVE SERVER

S9 Back up the local file system on the preferential active server (*) 35
bkp_type = all
normal_boot = yes
S10 Login to the operating system on the preferential active server 2 52
user = omc
S11 Shut down the OMC-R on the passive server 3 34
THE OMC-R IS STOPPED ON EACH OMC-R SERVER

S12 Update the preferential active server data on the passive server 2 53
preferential_active_server: hostname of the preferential
active server
S13 Start the OMC-R software on the preferential active server 30 51
args = -BLUEWIN -nodbcc
THE OMC-R IS RUNNING ON THE ACTIVE SERVER

S14 Shut down the operating system on the preferential passive server 2 41
run_level = 0
S15 Back up the local file system on the preferential passive server (*) 35
bkp_type = all
normal_boot = yes
S16 Login to the operating system on the preferential passive server 2 52
user = omc
S17 Shut down the OMC-R on the active server 5 34
THE OMC-R IS STOPPED ON EACH OMC-R SERVER

S18 Back up the disk array device, from the preferential active server (*) 39
(**)
S19 Configure the automatic OMC-R software startup on the passive OMC- 20 58
R server and reboot the passive OMC-R server
S20 Configure the automatic OMC-R software startup on the active OMC-R 40 58
server and reboot the active OMC-R server
THE BACKUP IS COMPLETE AND THE OMC-R IS RUNNING

(*) The backup can last up to several hours depending on the size of data to be saved and the type of
tape drive being used.
(**) The size of data will be displayed by the script used for performing backup and can be used to
calculate the backup time using information from sheet “DDS TAPE AND DRIVE UNIT
COMPATIBILITY” (page 59)

6.1.1.2. FOR A SINGLE/INTEGRATED OMC-R SERVER CONFIGURATION

page NOK
Input Parameters
THE OMC-R IS RUNNING
S21 If not already done, shut down the OMC-R on the OMC-R server 5 34
S22 Check the disks array devices: 5
on E4503 with T3 disks array 55
on Sun Fire 880 with T3 disks array 61
on Sun Fire 890 with HDI 64
S23 Back up the disk array device, from the preferential active /integrated (*) 39
server (**)
S24 Shut down the operating system of the OMC-R server 2 41
run_level = 0
S25 Back up the local file system on the OMC-R server (*) 35
bkp_type = all
normal_boot = yes
S26 Login to the operating system on the OMC-R server 2 52
user = croot
S27 Configure the automatic OMC-R software startup on the OMC-R server 20 58
and reboot the OMC-R server

(*) The backup can last up to several hours depending on the size of data to be saved and the type of tape
drive being used.
(**) The size of data will be displayed by the script used for performing backup and can be used to
calculate the backup time using information from sheet “DDS TAPE AND DRIVE UNIT COMPATIBILITY”
(page 59)

6.1.2 OMC-R/PCUOAM/SDO WORKSTATION FILE SYSTEM

BACKUP
6.1.2.1. U5/SB150/SB1500 FILE SYSTEM BACKUP ON DAT
The aim is to back up the local file system on an OMC-R workstation. This major step
must be applied on every U5, SB150 and SB1500 OMC-R workstation.
Note: If you perform backup of CIUS workstation, disable the CIUS service, if not yet
done

page NOK
Input Parameters
S28 If not yet done, shut down the OMC-R on the OMC-R or PCUOAM 5 34
workstation
THE OMC-R IS STOPPED

S29 Shut down the operating system 2 41
run_level = 0
S30 Connect a DAT drive on the OMC-R workstation 2 43
args = none
S31 Back up the local file system (*) 35
bkp_type = all
normal_boot = no
run_level = 0
S33 If necessary, disconnect the DAT drive from the OMC-R workstation 2 43
args = none
S34 Reboot the operating system 5 67
args = r

For PCUOAM workstation, MDM configuration backup is required:
See chapter § 6.4
6.1.2.2. U45 FILE SYSTEM BACKUP DVD
This chapter describes all steps necessary to make a backup of Ultra-45 workstation file
systems on DVD. The three main steps to perform a backup are:

- Estimation of the backup data size

- Creation of backup DVD images
- Burning backup DVD images
These three steps have 2 optional parameters:

excl_file – name of the file with the excluded data list. If you need to exclude
certain data from the set of backup files, create the file as specified at step
S36 “Prepare excluded and included data lists”.
incl_file – name of the file with the included data list. If you need to include certain
data to the set of backup files, create the file as specified at step S36 “Prepare
excluded and included data lists”.
Backup on DVD is possible only if sizes of the “/” and “/var” partitions (taken
separately) do not exceed the capacity of 1 DVD (4.7 Gb). If it is not the case,
you need to remove unnecessary files from these partitions or put them into the
backup exclude list (see step S36 “Prepare excluded and included data lists”).
Backup DVD images are created in the /home/backup/DVD 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
S37 “Estimation of the backup data size”).
Note: By default, tip_backup_dvd.sh excludes the following files defined in its internal
exclude list:
All core files present on the disk
All wtmpx files present on the disk

All utmpx files present on the disk
All messages.* files from directory /var/adm
All gcore files from directory /CMN/base/diagnostic

Directory /var/crash
Directory /home except files in directories /home/omc, /home/CIUS,
/home/TT_DB and /home/users/data (hence, work directory
/home/backup/DVD is excluded by default)
If you need to backup certain data from this list, you can use included data list for this
purpose (step S36 “Prepare excluded and included data lists”).
Note: If the CIUS service is enabled on the backed up workstation, you must disable it


page NOK
Input Parameters
THE COMPUTER TO BACKUP IS IN THE MULTI-USER MODE
S35 Install PE_BOOT_DVD image into the work directory 3 74
step = installing_boot_image
S36 If necessary, prepare excluded and included data lists 5 80
[excl_file: name of the file with the excluded data list]
[incl_file: name of the file with the included data list]
S37 Carry out estimation of the backup data size (*) 74
step = estimation

THE OPERATOR DECIDES TO MAKE A BACKUP
S38 If you are going to use DVD-RW disks for backup, blank them (**) 82
S39 If not yet done, shut down the OMC-R on the workstation 2 34
THE OMC-R IS STOPPED

run_level = 0
S41 Boot the operating system in the single-user mode 5 67
args = s
S42 Create backup DVD images (***) 74
step = images_creation

S43 Burn backup DVD images (****) 74
step = burning
THE BACKUP ON DVD IS COMPLETE

(*) 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.
(***) Estimated time necessary to create DVD images was displayed on step S37.
(****) It takes about 30 minutes to burn 1 DVD disk (+15 minutes for each disk to verify it).

6.2. OMC-R ENVIRONMENT DATA ARCHIVING
Step | Operation description (Total (*) min) min Sheet OK /

page NOK
Input Parameters
S44 Archive the OMC-R environment data for the current day, from the (*) 68
preferential active server
RefDocLabel = [R1]
THE BACKUP IS COMPLETED AND THE OMC-R IS RUNNING

6.3. OMC-R DAILY DATA ARCHIVING

page NOK
Input Parameters
S45 Archive the OMC-R daily data for the last 1, 2 or 3 days (up to your (*) 68
choice) before today, from the preferential active server
RefDocLabel = [R1]

(*) The duration depends on the number of days and of amount of the daily data.

6.4. PCUOAM CONFIGURATION BACKUP

page NOK
Input Parameters
THE OMC-R IS RUNNING ON INTEGRATED SERVER OR
ON ACTIVE SERVER AND PCUOAM WORKSTATION
S46 Back up the PCUOAM configuration data on the DAT cartridge or on a (*) 68
file system, on the preferential active server (or on the integrated
server)
RefDocLabel = [R1]

(*) The backup can last up to several hours depending on number of views for all PCUSNs and the
type of tape drive being used.

7. POST OPERATIONS
This operation is the last one for any operation described in this document
Step | Operation description (Total 8 min) min Sheet OK /

page NOK
Input Parameters
BEGINNING OF POST OPERATIONS

S47 For each OMC-R computer with deactivated “OS hardened” mode, 2 [A4]
resume “OS hardened” mode
S48 If the OMC-R computer is used without graphic display or keyboard 5
AND if not already done, close the telnet session to the Terminal
server port on which the OMC-R computer (whose system console is
supervised) is connected, from the supervisory workstation:
• If Xyplex Terminal server is used 46
• If LX-8020S Terminal server is used 73

S last Exit and clean 1 49
END OF POST OPERATIONS

8. SHEETS
The operation sheets are not arranged in the execution order. Always refer to the
operations sequence table, to determine the operations to execute and their input
parameters values.
The sheets used in this specific procedure also apply to other procedures (other
hardware configurations). Therefore, it may happen that you find some conditional
sections or sentences that are available only in other procedures.

XYPLEX DEPORTED CONSOLE OPENING

PRESENTATION
The purpose of this sheet is to get a deported console, by opening a telnet connection on one of the
Xyplex terminal server ports, on a supervisory workstation or any machine owning a screen and a
keyboard.
Two different consoles can be opened from the Xyplex terminal server:
• The terminal server deported console on port 0,which allows the terminal server
configuration itself,
• Any deported console of a machine which TTYA port is connected to any port (except port
0) of the terminal server
INPUT PARAMETERS
terminal_server_hostname Hostname of the Xyplex terminal server
port_number Number of the Xyplex port connected to the OMC-R server
INITIAL STATUS
The supervisory workstation is available and its Ethernet link is connected to the network.
ACTIONS
) ON THE SUPERVISORY WORKSTATION
1. If a shell window is not available: Open a shell session using croot login.
2. Update the appropriate environment variable of the deported console to use the "vi" editor:
Under (c)root login:
...(root) # setenv TERM sun-cmd ↵
3. Enter the following command to launch the deported console connection, where telnet_port =
2000 + port_number*100:
Example: port_number = 15: telnet_port = 3500
Under deported server console:

... (root) # telnet terminal_server_hostname telnet_port ↵
Trying terminal_server_IPadd...
Negociating binary mode with remote host.
Connected to terminal_server_Hostname.
Escape character is ‘^]’.
↵
(Machine_Hostname_prompt)

4. If the telnet port 0 connection is attempted: the Xyplex deported console is to be opened at
telnet port 2000
4.1 Type the "access" password to access the Xyplex port 0:
... (root) # telnet terminal_server_hostname 2000 ↵
↵
#access ↵
Enter username>
4.2 Type the username to access the Xyplex:

Enter username> console ↵
4.3 Type the following command to obtain the privilege mode:

Xyplex> set privilege ↵
4.4 Type the "system" password to get the privilege mode:

Password> system ↵
Welcome to the Xyplex Terminal Server.

For information on software upgrades contact your local
representative,
or call Xyplex directly at
in USA: (800) 338-5316

in Europe: +44 81 759-1633
in Asia: +65 336-0431
Xyplex>>
TROUBLE SHOOTING
1. If nothing appears on the graphic screen after a carriage return, enter simultaneously both Ctrl
and w keys to recover the machine prompt:
Escape character is ‘^]’. ↵
[Ctrl][w] ↵
2. If the telnet connection on the port is refused, perform the following steps:
2.1 Open a port 0 telnet connection as explain on step 3 using port_number = 0.
2.2 Set the privilege mode as explained on step 4.
2.3 Logout from the troubling port:

Xyplex>> logout port port_number ↵

Xyplex>>
2.4 Logout from port 0:

Xyplex>> set nopriv ↵
Xyplex> quit ↵
Xyplex -020- Logged out port 0 on server X0C9276 at 04 Jan 1970
00:49:34
2.5 Logout from telnet:

Xyplex -020- Logged out port 0 on server X0C9276 at 04 Jan 1970
00:49:34
[Ctrl][]] ↵
telnet> quit ↵
Connection closed.
... (root) #
2.6 Perform again step 3.
3. If telnet connection on all ports is refused, except on port 0:
3.1 If the machine you are attempting to connect is not allowed accessing Xyplex ports:
Perform this sheet from another machine.
3.1 If this machine should be allowed to access Xyplex ports: Modify the Internet security
configuration to enable Internet security of this machine.
4. If a command is not executed during the telnet connection: It can happen that a command in an
OMC-R configuration supervised by Xyplex stays non executed. Then, you have to re-execute
it.
FINAL STATUS
The server console is opened on the supervisory workstation and the title window is renamed.

STOPPING OMC-R
SCOPE
This sheet details how to stop the OMC-R application, on OMC-R servers (Integrated or not) 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) %
Note: In case of a dual server configuration, both OMC-R servers will be stopped
simultaneously by carrying out the above command on the preferential active server.
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(s) or the OMC-
R workstation).

LOCAL FILE SYSTEM BACKUP

PRESENTATION
The purpose of this sheet is to backup the local file systems of an OMC-R machine (OMC-R server or
OMC-R workstation). In the case of OMC-R server, the file systems located on disks of disks array
device are not saved.
Required resources:
- 1 blank DAT
- A DAT drive available on the local machine
INPUT PARAMETERS
bkp_type: type of backup ("system" to backup /, /usr, /var, /opt and /home file system
| "application" to backup other local file systems | "all" to backup all local
file systems).
normal_boot: indicates if the system should be booted in multi-user mode after the
backup
(yes | no).
INITIAL STATUS
The operating system is halted under OBP.
The console terminal of the machine is available.
A DAT drive is connected in /dev/rmt/0 and is operational.
ACTIONS
1. Start up the operating system in single user mode on the machine:
On the console terminal:
... ok boot -rs ↵
Resetting ....
.....
INIT: SINGLE USER MODE
Type Ctrl-d to proceed with normal startup,
(or give root password for system maintenance):enter the root password
↵
.....
2. Insert the blank DAT into the drive of the machine.
3. Backup the local file systems:

# /usr/local/oam/bin/ds_backup.sh -Y -Mbkp_type ↵
Do not try to eject DAT before script finishes.
4. Take off the DAT, put a sticker on it, make it write-protect by sliding the tab, and re
insert it in the drive.
5. Check that the DAT is readable by checking if the restore tool exists in the first tar file:


# tar tvf /dev/rmt/0 /tmp/backup/bin/ds_restoreAll.sh ↵
-rwxr-xr-x 0/1 -----------------------
/tmp/backup/bin/ds_restoreAll.sh
6. Take off the DAT.
7. If normal_boot = yes, continue in normal startup:

{
# [Ctrl][d]
INIT: New run level: 3
The system is coming up. Please wait.
.....
}
Else:
{
The operating system remains in single user mode.
}
TROUBLE SHOOTING
1. If the following message appears:
WARNING: ..................
Soft error rate (retries = 7) during writing was too high
Periodic head cleaning required and/or replace tape cartridge
{
The whole backup may be very long. You should better:
- Interrupt it with [Ctrl],[C], and wait (maybe a long time) the current file system dump
ends
- Insert a head cleaning DAT in the drive
- Use a brand new DAT and perform the backup again
}
2. After the backup, if the OMC-R does not restart properly at system reboot, check the
/etc/inittab file:
{
If not already done, open a root or croot session on the backuped machine.
Edit the /etc/inittab file; it should conform to the following:

ap::sysinit:/sbin/autopush -f /etc/iu.ap
ap::sysinit:/sbin/soconfig -f /etc/sock2path
fs::sysinit:/sbin/rcS >/dev/console 2<>/dev/console
</dev/console
is:3:initdefault:
p3:s1234:powerfail:/usr/sbin/shutdown -y -i5 -g0 >/dev/console
2<>/dev/console
s0:0:wait:/sbin/rc0 >/dev/console 2<>/dev/console
</dev/console
s1:1:wait:/usr/sbin/shutdown -y -iS -g0 >/dev/console 2<>/dev/console
</dev/console
</dev/console


</dev/console
</dev/console
</dev/console
</dev/console
fw:0:wait:/sbin/uadmin 2 0 >/dev/console 2<>/dev/console
</dev/console
of:5:wait:/sbin/uadmin 2 6 >/dev/console 2<>/dev/console
</dev/console
rb:6:wait:/sbin/uadmin 2 1 >/dev/console 2<>/dev/console
</dev/console
sc:234:respawn:/usr/lib/saf/sac -t 300
ow:3:wait:/home/omc/boot/start_windows.sh
md:3:once:su - omc -c "cd /CMN/base/exe; ./cf_init.x -ym -d 120 | tee –a
/CMN/diagnostic/diag_restart_omc" >/dev/console 2>&1 </dev/console
If the /etc/inittab file does not conform to the previous lines:

{
Remove any extra line from the /etc/inittab file.
Add any missing line in the /etc/inittab file.
Reboot the machine
}
}
3. If the ds_backup.sh tool interrupts with the following message:

Setting tape device ... Nok
3.1. Remove existing links for DAT device:

# rm /dev/rmt/* ↵
3.2. Reconfigure the DAT device:

# drvconfig ↵
# tapes ↵
3.3. Execute the ds_backup.sh tool again.
4. If the DAT was accidentally ejected during ds_backup.sh work and the script asks
whether to continue or abort operation, you should abort operation and launch the
script again with the same parameters.
5. If during the file system backup a message like the following appears:

DUMP: 90.02% done, finished in 0:06

DUMP: End-of-tape detected
DUMP: Tape rewinding
DUMP: 98.54% done, finished in 0:00
DUMP: Change Volumes: Mount volume `#2' on `server1:/dev/rmt/0'
DUMP: NEEDS ATTENTION: Is the new volume (#2) mounted on
`server1:/dev/rmt/0' and ready to go?: ("yes" or "no")
This means that you have not enough space on the tape to complete the file system
backup. This is an error situation. Please, answer "no" and abort the backup. You can
try to take a bigger tape or to check the size of your /home partition – if it is very big
you might have to delete some unused files.
6. If during the file system backup a message like the following appears:
DUMP: Write error ...

DUMP: NEEDS ATTENTION: Do you want to restart?: ("yes" or "no")
This means that writing on tape failed. You should answer “no”, replace this tape by
another one and launch the tool again.
7. The log file of the tool is /var/local/oam/ds_backup.log.
FINAL STATUS
A file system backup is available for the local machine. The operating system is rebooted or remains
in single user mode, depending on the normal_boot parameter.

DISKS ARRAY DEVICE BACKUP

PRESENTATION
This sheet applies to:
• T3 disks array device on the E4500 server(s)
• T3 disks array device on Sun Fire 880 server
• HDI disks on Sun Fire 890 server
Its purpose is not to backup file-systems built in the disks array device, but to save
the partitioning of disks on the array device, their SVM configuration and the
applicative tree built on their file-systems. It must be completed by issuing OMC-R
environment and daily data backup.
Backup of disks array device has to be performed from the last active server only.
Required resources: 1 blank DAT.
INITIAL STATUS
The OMC-R is not running.
A croot session is available on the last active server.
ACTIONS
1. If not already done, open a shell session under croot user, on the last active server.
2. Insert the blank DAT into the drive on the last active server.
3. Backup the disks array device from the last active server:
Under croot login on the last active server:
...(root) # /usr/local/oam/bin/ds_backup.sh -Y -M d i s ks A rra y
...
#################################################################
# STARTING : ds_backup.sh #
# WITH : -Y -MdisksArray #
# LOG IN : /var/local/oam/ds_backup.log #
#---------------------------------------------------------------#
# DATE | VERSION | UID | MACHINE #
#---------------------------------------------------------------#
# ../../.. ..:..:.. | V.._..... | 0 | ........ #
#################################################################
PRELIMINARY TASKS
=================
...
Disks Array partitions backup

=====================
...
#################################################################
# ds_backup.sh #
#---------------------------------------------------------------#
# END DATE : ../../.. ..:..:.. #
# STATUS : OK #
#################################################################

4. Take off the DAT, put a sticker on it and make it write-protect by sliding the tab.
TROUBLE SHOOTING
1. If the following message appears:
WARNING: ..................
Soft error rate (retries = 7) during writing was too high
Periodic head cleaning required and/or replace tape cartridge
{
The whole backup may be very long. You should better:
- Interrupt it with [Ctrl],[C], and wait (maybe a long time) the current file system dump ends
- Insert a head cleaning DAT in the drive.
- Use a brand new DAT and perform the backup again.
}
2. If the ds_backup.sh tool interrupts with the following message:

Setting tape device ... Nok
2.1. Remove existing links for DAT device:

# rm /dev/rmt/* ↵
2.2. Reconfigure the DAT device:

# drvconfig ↵
# tapes ↵
2.3. Execute the ds_backup.sh tool again.
3. The log file of the tool is /var/local/oam/ds_backup.log
FINAL STATUS
A backup of the disks array device is available on the first section of DAT.

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 )
INITIAL STATUS
The OMC-R application is not running.
A root or croot session is available.
If the servers are used without a graphic display or a keyboard, the deported console is available on
the supervisory workstation.
ACTIONS
For a server or a PCUOAM workstation used with a graphic display and a keyboard, or for a
workstation:
1. If not already done, open a croot or 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 or croot 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

In the deported console on the supervisory workstation:
# init run_level ↵
TROUBLESHOOTING
1. If the init 0 or init 6 command does not result in the operating system shutdown, use the
following workaround:
Type at the command prompt of the root or croot account shell or in the
supervisory workstation deported console:
# sync ↵
# sync ↵
# halt ↵
2. If the init command is issued from a remote connection (telnet or rlogin), the session will be
closed during the action completion:
(root) # init run_level ↵
Connection closed by foreign host
3. For init 6 command only, reboot for operating system restart:

Type at the command prompt of the root or croot account shell or in the
supervisory workstation deported console:
(root) # boot ↵
...
FINAL STATUS
The operating system is halted or rebooted, depending on the run_level parameter.

INSTALLING/REMOVING EXTERNAL DAT DRIVE

SCOPE
This sheet details how to install/remove an external DAT drive on/from an OMC-R workstation.
INITIAL STATUS
The OMC-R workstation is shut down and the Open Boot Prom prompt displays «ok».
An external DAT drive, an SCSI cable and an SCSI terminator are available for installation.
INPUT PARAMETERS
args [boot] indicates that it is necessary to perform a boot operation.
ACTIONS
TO INSTALL:
4. Carry out the following commands:

ok setenv diag-switch? true ↵
ok setenv auto-boot? false ↵
ok reset-all ↵
If the OMC-R workstation is a Sun Blade™ 1500, proceed step 5
ok probe-scsi-all ↵
...
5. Power OFF the OMC-R workstation and then the peripheral devices:
• Turn OFF the computer power switch
• Turn OFF the power switches of the graphic display and other peripherals
6. Connect the SCSI cable:

6.1 If there are external SCSI devices already: Remove the SCSI terminator from the
SCSI connector of the last device and connect the SCSI cable between the DAT drive
IN connector and the device SCSI OUT connector.
6.2 If there are no external SCSI devices: Connect the SCSI cable between the DAT drive
IN connector and the SCSI connector on the back side of the OMC-R workstation.
6.3 Plug the SCSI terminator in the available SCSI DAT drive OUT connector.
6.4 Check that SCSI connectors are correctly locked with screws.
7. Power ON the graphic display and all other peripheral devices, then turn on the OMC-R
workstation.
8. Check the SCSI devices:

8.1 Carry out the following command:
The output will be:

...
Target 4 or 5
Unit0 Removable Tape ...
...
ok
8.2 Make sure that the words Removable DAT appear, as an indication that the DAT drive
is correctly connected.
9. Restore the factory default configuration:
ok set-defaults ↵
Setting NVRAM parameters to default values
ok
10. If (args = boot), carry out the following command, to make the changes valid:
ok boot -r ↵
TO REMOVE:
1. Carry out the following commands:
ok setenv diag-switch? true ↵

ok setenv auto-boot? false ↵
2. Power OFF the OMC-R workstation and then the peripheral devices:
• Turn OFF the computer power switch
• Turn OFF the power switches of the graphic display and other peripherals
3. Disconnect the SCSI cable.
3.1 If there is another SCSI device: Remove the SCSI cable between the DAT drive and
the SCSI device and plug the SCSI terminator in the SCSI device OUT connector.
3.2 If there is no external SCSI device: Remove the SCSI cable between the DAT drive
and the OMC-R workstation. Plug the SCSI terminator in the OMC-R workstation
SCSI connector.
4. Power ON the graphic display and all other peripherals, then turn on the OMC-R workstation.
5. Check the SCSI devices:
5.1 Carry out the following command:
ok reset-all ↵
5.2 Make sure there is no reference to the removable DAT drive in the output, which
means that it has been disconnected correctly.
6. Restore the factory default configuration:

ok set-defaults ↵
Setting NVRAM parameters to default values
ok
7. If (args = boot), to make the changes valid, carry out the following command:
ok boot -r ↵
FINAL STATUS
The external DAT drive is installed or removed from the OMC-R workstation.
The OMC-R workstation is booted if args = boot and halted under OBP if args = none.

XYPLEX DEPORTED CONSOLE CLOSING

PRESENTATION
The purpose of this sheet is to close a deported console previously open on the Xyplex terminal
server.
INPUT PARAMETERS
port_number number of the Xyplex port
INITIAL STATUS
The Ethernet link is connected.
A telnet connection on a port is available.
ACTIONS
) ON ANY EQUIPMENT CONFIGURED AS
A XYPLEX BOOT SERVER
1. Enter the following line to log out from the a Xyplex terminal server port:
If port_number = 0:
{
Xyplex>> set nopriv ↵

Xyplex> quit ↵
Xyplex -020- Logged out port 0 on server X0C9276 at 13 Nov 1997
10:50:45
[Ctrl],[]]
telnet> quit ↵
Connection closed.
...(root)#
}
Else
{
{1} ok [Ctrl],[]]
telnet> quit ↵
Connection closed.
<machine_hostname>...(root)#
}
FINAL STATUS
The deported console is closed on the machine.

HOW TO…
SCOPE
The purpose of this sheet is to help you perform some basic operations that you have to do to
complete the main procedure.
INITIAL STATUS
The OMC-R application is running and the MMI is accessible on every local workstation.
ACTIONS
) ON A SERVER, without a graphic display and keyboard

) ON A PCUOAM WORKSTATION, without a graphic display and keyboard
For a server or PCUOAM workstation without a graphic display and keyboard, the supervisory
workstation displays a console window. This window is called ‘deported console window’. The
deported console is necessary to access the server when the UNIX network layer is not
available (e.g. reboot, stop A…).
Most commands can be carried out remotely from a workstation by means of the remote access
procedure described below. Thus, opening a server or PCUOAM workstation session means
starting a remote access session on an OMC-R workstation (see step D1). No deported console
via the "terminal server" from the supervisory workstation is required.
But each time the console window is required, (such as reboot after "stop A"…), the deported console
via the "terminal server" from the supervisory workstation is mandatory and is precisely
specified before performing a command.
A1. How to update the environment variable to use the "vi" editor on the deported server console:
Type at the command prompt of the deported server console:
... # TERM=sun-cmd ; export TERM ↵
) ON SERVER
B1. Locked mode: How to lock the server
Lock the server by turning the front key to the LOCKED position ( ).
B2. Unlocked mode: How to unlock the server
Unlock the server by turning the front key to the ON position (I).
) ON A SERVER, with a graphic display and keyboard

) ON A WORKSTATION
C1. How to open a shell session window:
On the background menu
SELECT « Access to UNIX »
Then enter the username (omc, root...)
Enter the appropriate password.
) ON A LOCAL OMC-R WORKSTATION

D1. How to remotely log on to the active server from a workstation:
D1.1 Open an omc session window (as explained in step C1)
D1.2 Remotely log on to the active server


GOTO « Xterm »
Type at the command prompt of the omc account shell:
... (omc) % rlogin active_server_name ↵
D2. How to open a session log window:
GOTO « OMC-R browser »
SELECT « View » = Logical
SELECT « Administration »
SELECT « user session log... »
D3. How to open a notification window:
GOTO « OMC-R browser »
SELECT « View » = Logical
SELECT_OBJ « MD-R »
SELECT « Object – Display|Set »
Locate the managerServer parameter.
The value of this parameter is the hostname of the active server
FINAL STATUS
Now you know how to perform all the basic operations described above.

EXIT AND CLEAN

SCOPE
The purpose of this sheet is to help you correctly complete the operations.
INITIAL STATUS
All the operations of requested procedure are completely done.
ACTIONS
) ON SERVER
1. If not already done, lock each server by turning the front key to the LOCKED position ( ).
) ON EACH SITE
1. Gather all backup DATs, make sure each of them is write-protected and has a labelled sticker
on it.
2. Take all backup DATs, CD(or DVD)-ROM(s), all procedures, all documents (and so on…) and
put them in a safe place.
FINAL STATUS
All servers are now locked and all sites are now clean and tidy.

INTER-SERVER SWITCHOVER
PRESENTATION
This sheet describes how to force, in a dual OMC-R servers configuration, an inter-server switchover
for validation.
INITIAL STATUS
The OMC-R application is running on the OMC-R server(s).
An omc session is available on the preferential active server.
The data mirroring is active and the OMC-R/BSS links are available on the OMC-R server(s).
ACTIONS
1. If not already done, open a shell session under omc user, on the preferential active server.
2. Launch the following command:

Under omc login:
... (omc) % /CMN/base/exe/cf_switchover.x -y ↵
3. Check the shutdown message on the preferential active server "Start_OMC-R" window:
<----- Exit sequence - ... ----->
And the start-up message on the preferential passive server "Start_OMC-R" window:
<----- .. - Running sequence - dd/mm/yy hh:mm:ss ----->
FINAL STATUS
The inter-server switchover is complete.

STARTING LOCAL 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
[-BLUEWIN] 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
INITIAL STATUS
The OMC-R application is not running.
An omc session is available on the computer.
ACTIONS
1. Open a new shell session of the omc account, on the computer.
2. Run the starting script on the computer:

Type at the command prompt of the omc account shell on the computer:
... (omc) % /home/omc/bin/ds_start_omc.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 each OMC-R server or on the OMC-R workstation.

UNIX CONSOLE LOGIN

PRESENTATION
The purpose of this sheet is to describe how to perform a login as a specified user to a local OMC-R
machine, using the console login prompt.
INPUT PARAMETERS
user Unix user to login
INITIAL STATUS
A console terminal of the machine is available (for server without screen and keyboard, the deported
console is available on the supervisory workstation).
No graphic environment is launched.
ACTIONS
1. Strike the Enter key and login to the operating system:
on the console terminal:
hostname console login: user ↵
user password: enter the user password ↵
2. If the OMC-R server owns a graphic screen and a keyboard :

{
Depending on the user identification, a graphic environment may be launched.
• For root: no graphic environment is launched
• For croot: answer "CDE" to the question "Which WindowManager?(CDE|none)..."
• For omc: CDE graphic environment is automatically launched
}
Else: Whatever the login, no graphic environment is launched.
TROUBLE SHOOTING
1. If the system console screen shows repetitively the two following lines:
hih0: xmit hung

hih1: xmit hung
It means that no X25 link is connected to HSI ports 0 and 1; it may be normal or may not be,
depending on BSC connection status.
Strike the Enter key to display the login prompt and perform the action # 1.
FINAL STATUS
The user is logged in

DISKS ARRAY DEVICE ASSIGNATION

PRESENTATION
The purpose of this sheet is to restore, in a dual OMC-R servers configuration, the disks array device
assignation to the preferential active server from the preferential passive server after an inter-server
switchover on E4500 server(s).
INPUT PARAMETERS
preferential_active_server: hostname of the preferential active server.
INITIAL STATUS
The OMC-R is stopped on the OMC-R server(s).
A croot session is available on the preferential passive server.
ACTIONS
1. If not already done, open a shell session under omc user on the preferential passive server.
2. Execute the following command on the preferential passive server:

Under omc login on the preferential passive server:
... (omc) % /CMN/shell/cf_majsecours.sh preferential_active_server ↵
3. The following message is displayed:
******************************************************
* cf_majsecours.sh *
* VERSION:... *
******************************************************
...
The script shell is completed.
FINAL STATUS
The disks array device is assigned to the preferential active server.
The OMC-R application can be restarted.

CHECK FILE SYSTEM FULL

PRESENTATION
The purpose of this sheet is to check if file systems are full.
INITIAL STATUS
The OMC-R may be running or not.
A (c)root session is available.
ACTIONS
1. Check the percentage of use of the local file systems:
Under (c)root login on the machine:
# df -kt ↵
Note: An output of this command on your machine will generally differ from the example given
below. The output depends on OMC-R role of machine and file systems condition.
1.1. Pay attention to value of capacity column of each file system (see example below).
# df –kt
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c2t10d0s0 25159 23262 0 100% /
/dev/dsk/c2t10d0s3 241607 193653 23794 90% /usr
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
/dev/dsk/c2t10d0s5 317799 31510 254510 12% /var
/dev/dsk/c2t10d0s4 384871 253555 92829 74% /opt
/dev/dsk/c2t10d0s6 484719 960 435288 1% /home
swap 631176 177464 453712 29% /tmp
/dev/dsk/c2t11d0s0 288855 90439 169531 35% /MD/base
/dev/dsk/c2t11d0s1 1089439 75331 959637 8% /CMN/base
/dev/dsk/c2t11d0s3 605119 605123 0 100% /OMC/base
If a file system is full (capacity is 100%), then clean the file system by deleting useless files.
FINAL STATUS
No one of the file systems must be full.

DISKS ARRAY CHECKING

SCOPE
The purpose of this sheet is to check that the T3 disks array device(s) are correctly recognized by an
E4500 server
INITIAL STATUS
The disks array device(s) are correctly connected to the E4500.
The E4500 is booted, either on CDROM or on OBP.
A root or croot session is available on the machine to check.
ACTIONS
1. If not already done, open a shell session under croot user on the OMC-R server.
2. Check the number of disks:

Under croot login:
... (root) # echo | format ↵
Check that 2 T3 disks disks are found on c1t1d0 and c2t1d0:
Here is an example of the previous command executed from a E4500/T3:
AVAILABLE DISK SELECTIONS:

0. c0t10d0 <SUN2.1G cyl 2733 alt 2 hd 19 sec 80>
/sbus@3,0/SUNW,fas@3,8800000/sd@a,0
1. c0t11d0 <SUN2.1G cyl 2733 alt 2 hd 19 sec 80>
/sbus@3,0/SUNW,fas@3,8800000/sd@b,0
2. c1t1d0 <SUN-T300-0117 cyl 34530 alt 2 hd 112 sec 128>
/sbus@2,0/SUNW,socal@d,10000/sf@1,0/ssd@w50020f2300002d7b,0
/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w50020f2300005963,0
Check that no errors are displayed (for example: c1t1d0 <Drive type unknown>)
3. Check the disks status:
Check that both disks are in “OK” status:

Under croot login:

... (root) # /usr/sbin/luxadm display /dev/rdsk/c1t1d0s2 ↵
DEVICE PROPERTIES for disk: /dev/rdsk/c1t1d0s2
Status(Port A): O.K.
Vendor: SUN
Product ID: T300
WWN(Node): 50020f200000bf19
WWN(Port A): 50020f230000bf19
Revision: 0200
Serial Num: 0004892110
Unformatted capacity: 241724.000 MBytes
Write Cache: Enabled
Read Cache: Enabled
Minimum prefetch: 0x0
Maximum prefetch: 0x0
Device Type: Disk device
Path(s):
/dev/rdsk/c1t1d0s2
/devices/sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w50020f230000bf19,0:c,
raw

Status(Port A): O.K.
Vendor: SUN
Product ID: T300
WWN(Node): 50020f200000ba07
WWN(Port A): 50020f230000ba07
Revision: 0200
Serial Num: 0004762310
Read Cache: Enabled
Path(s):
/dev/rdsk/c2t1d0s2
/devices/sbus@3,0/SUNW,socal@d,10000/sf@1,0/ssd@w50020f230000ba07,0:c,
raw
4. Check that each mirror have 2 sub-mirrors:

Under croot login:
... (root) # /usr/sbin/metastat -s DISKSET1 -p | grep -- "-m" ↵
Check that for each mirror “d(5*p)” two sub mirror are defined “d(5*p+1)” and “d(5*p+2)”
DISKSET1/d(5*p) -m DISKSET1/d(5*p+1) DISKSET1/d(5*p+2) 1
Here is an example of the previous command:

DISKSET1/d5 -m DISKSET1/d6 DISKSET1/d7 1

5. Check that no disks are under maintenance:

... (root) # /usr/sbin/metastat -s DISKSET1 | grep "ainten" ↵
Check that nothing is displayed.
TROUBLESHOOTING
If any check fails there is certainly a hardware failure, please take the appropriate action before
to continue.
FINAL STATUS
The disks array device(s) have been checked.

HOW TO ENABLE AUTOSTART

SCOPE
This sheet details how to modify the system configuration of the OMC-R computer to enable automatic
OMC-R startup. After that the OMC-R computer will be automatically rebooted.
INPUT PARAMETERS
None
INITIAL STATUS
A croot session is available on the computer.
ACTIONS
1. If not done yet, open a croot shell session.
2. Run the following command:

Type at the command prompt of the croot account shell:
... (root) # nohup /usr/local/oam/bin/ds_omcAutoStart_NH.sh ↵
FINAL STATUS
The /etc/inittab file is modified to run the OMC-R software at the system startup. The OMC-R
computer is rebooted.

DDS TAPE AND DRIVE UNIT COMPATIBILITY

SCOPE
The purpose of this sheet is to provide information about compatibility between DDS tapes and drives.
ACTIONS
1. DDS Tape Drives description:
DDS Drives Media Native Capacity Data Rate

DDS Drives First Generation 60 meter MP 1.3 GB 183 KB/sec
(Introduced 1989)
DDS Drives Second Generation 90 meter MP 2 GB 183 - 233 KB/sec
(Introduced 1991)
DDS2 Drives 120 meter MP 4 GB 360 - 750 KB/sec
(Introduced 1993)
DDS3 Drives 125 meter MP++ 12 GB 0.7 - 1.5 MB/sec
(Introduced 1996)
DDS4 Drives 150 meter MP+++ 20 GB 2.4 - 3 MB/sec
(Introduced 1999)
DAT-72 Drives 170 meter MP++++ 36 GB 3.0 - 3.5 MB/sec
2. DDS Tape Drives Read-Write compatibility:
Please follow this table when choose tape to use. Tapes typed in bold are recommended.
Please don’t use tapes that are grayed out.
DDS DDS-2 DDS-3 DDS-4 DAT-72

Tapes Tape Drive Tape Drive Tape Drive Tape Drive Tape
Drive
DDS-1 (60m) R/W R/W R/W
DDS-1 (90m) R/W R/W R/W R
DDS-4 (150m) R/W R/W
DAT-72 (170m) R/W

3. DDS Tape Drive compatibility:
4MM DDS DRIVE COMPATIBILITY

TAPE MEDIA DDS1 DDS1
DDS-2 DDS-3 DDS-4 DAT-72
(60m) (90m)
DG-60M 1.3 GB 1.3 GB 1.3 GB 1.3 GB *Note NC

DG-90M NC 2 GB 2 GB 2 GB *Note NC
DG-120M NC NC 4 GB 4 GB 4 GB NC
DG3-125M NC NC NC 12 GB 12 GB 12 GB
DG4-150M NC NC NC NC 20 GB 20 GB
DG-170M NC NC NC NC NC 32 GB
NC – Not Compatible Native Capacities Shown
*Note: DDS-1 tape compatibility on DDS-4 drives varies with different drive manufacturers.
4. FUJIFILM 4MM DDS Data Cartridge Compatibility Guide:
FUJIFILM P/N DESCRIPTION NATIVE CAPACITY

26047060 DG-60M 1.3 GB on all Drives*
26047190 DG-90M 2.0 GB on 2nd Generation DDS & later Drives*
26047120 DG-120M 4.0 GB on DDS2, DDS3 & DDS4 Drives
26047300 DG3-125M 12.0 GB on DDS3 & DDS4 Drives
26047350 DG4-150M 20.0 GB on DDS4 Drives
26046172 DAT72 36.0 GB on DAT-72 Drives
Use FUJIFILM DG-12CL cleaning cartridge, P/N 26049006, for all 4mm drive cleaning.
* DDS-1 tape compatibility on DDS-4 drives varies with different drive manufacturers.
Note: All capacities and data rates are shown without compression (non-compressed). Two-times (2X) the
native value shown, is typical when indicating compressed values. Data transfer rate is drive dependent; see
drive specifications for exact value, e.g. the data rate of Sony’s DDS4 drive model SDT-10000 is 2.4 MB/sec
without compression. For questions, go to Ask-The-Expert at WWW.FUJIFILMMEDIASOURCE.COM.
FINAL STATUS
The information about compatibility between DDS tapes and drives is introduced.

DISKS ARRAY CHECKING ON SFV880

PRESENTATION
The purpose of this sheet is to check that the T3 disks array devices are correctly recognized by an
SFV880 server
INITIAL STATUS
The T3 disks array device are correctly connected to the SFV880.
The SFV880 is booted, either on CDROM or on OBP.
A root or croot session is available on the machine to check.
ACTIONS
2. Check the number of disks:

Under croot login:
Check that 2 T3 disks disks are found on c2t1d0 and c3t1d0:
Here is an example of the previous command executed from a SFV880/T3:

0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf6b9b2d,0
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf6bb168,0
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf6ba56e,0
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf6ba699,0
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf6ba648,0
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf6bbde9,0
/pci@9,600000/pci@2/SUNW,qlc@4/fp@0,0/ssd@w50020f230000533a,0
/pci@9,600000/pci@1/SUNW,qlc@4/fp@0,0/ssd@w50020f230000534d,0
Check that no errors are displayed (for example: c2t1d0 <Drive type unknown>)

3. Check that both disks are in “OK” status:

Under croot login:
Vendor: SUN
Product ID: T300
Revision: 0201
Serial Num: Unsupported
Read Cache: Enabled
Path(s):
/dev/rdsk/c2t1d0s2
/devices/pci@9,600000/pci@1/SUNW,qlc@4/fp@0,0/ssd@w50020f230000534d,0:
c,raw
LUN path port WWN: 50020f230000534d
Host controller port WWN: 210100e08b2461ed
Path status: O.K.

Vendor: SUN
Product ID: T300
Revision: 0201
Serial Num: Unsupported
Read Cache: Enabled
Path(s):
/dev/rdsk/c3t1d0s2
/devices/pci@9,600000/pci@2/SUNW,qlc@4/fp@0,0/ssd@w50020f230000533a,0:
c,raw
LUN path port WWN: 50020f230000533a
Host controller port WWN: 210100e08b26d097
Path status: O.K.

Under croot login:
... (root) # /usr/sbin/metastat -s DISKSET1 -p | grep -- "-m" ↵
Check that for each mirror “d(5*p)” two sub mirror are defined “d(5*p+2)” and “d(5*p+1)”
DISKSET1/d(5*p) -m DISKSET1/d(5*p+2) DISKSET1/d(5*p+1) 1



... (root) # /usr/sbin/metastat -s DISKSET1 | grep "ainten" ↵
TROUBLE SHOOTING
If any check fails there is certainly a hardware failure, please take the appropriate action before
to continue.
FINAL STATUS
The T3 disks array devices have been checked.

DISKS ARRAY CHECKING ON SFV890

PRESENTATION
The purpose of this sheet is to check that internal disks array is correctly recognized by SFV890
server
INITIAL STATUS
SFV890 server is booted.
A root or croot session on server is available.
ACTIONS
2. Check that 12 internal disks are available:

Under croot login:
Searching for disks...done

0. c1t0d0 <SUN...G cyl ... alt 2 hd .. sec ...>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@.................,0
1. c1t1d0 <SUN72G cyl ... alt 2 hd .. sec ...>

3. Check that all disks are in “O.K.” status:

Under croot login:
... (root) # /usr/sbin/luxadm display /dev/es/ses1 ↵
SUNWGS INT FCBPL
DISK STATUS
SLOT DISKS (Node WWN)
0 On (O.K.) 20000011c61cba47
1 On (O.K.) 20000011c61c7504
2 On (O.K.) 20000011c61cbb98
3 On (O.K.) 20000011c61cba7e
4 On (O.K.) 20000011c61b9ed2
5 On (O.K.) 20000011c61cb338
6 On (O.K.) 500000e010a31a80
7 On (O.K.) 500000e010a3d6d0
8 On (O.K.) 500000e010a3d890
9 On (O.K.) 500000e010a31300
10 On (O.K.) 500000e010a31330
11 On (O.K.) 500000e010a3d6c0
SUBSYSTEM STATUS
FW Revision:922A Box ID:0
Node WWN:50800200001e1a50 Enclosure Name:FCloop
SSC100's - 0=Base Bkpln, 1=Base LoopB, 2=Exp Bkpln, 3=Exp LoopB
SSC100 #0: O.K.(922A/ 8D3C)
SSC100 #1: O.K.(922A/ 8D3C)
SSC100 #2: O.K.(922A/ 8D3C)
SSC100 #3: O.K.(922A/ 8D3C)
Temperature Sensors - 0 Base, 1 Expansion
0:25єC 1:26єC (All temperatures are NORMAL.)
Backplanes - A=Base, B=Expansion
A: O.K.
B: O.K.
Default Language is USA English, ASCII

Under croot login:
... (root) # /usr/sbin/metastat -p | grep -- -m ↵
Check that for each mirror “dXX” two sub mirrors are defined: dYY and dZZ
dXX -m dYY dZZ 1

d30 -m d31 d32 1
d20 -m d21 d22 1
d15 -m d16 d17 1
d10 -m d11 d12 1
d25 -m d26 d27 1
d5 -m d6 d7 1
d100 -m d101 d102 1
d90 -m d91 d92 1
d85 -m d86 d87 1
d75 -m d76 d77 1
d105 -m d106 d107 1
d70 -m d71 d72 1
d65 -m d66 d67 1
d55 -m d56 d57 1
d40 -m d41 d42 1

d35 -m d36 d37 1

d50 -m d51 d52 1

... (root) # /usr/sbin/metastat | grep –i "mainten" ↵
TROUBLE SHOOTING
If any check fails there is certainly a hardware failure, please take the appropriate action before to
continue.
FINAL STATUS
The internal disks array has been checked.

OPERATING SYSTEM BOOT FROM OBP

PRESENTATION
This sheet describes how to boot the operating system of an OMC-R workstation or a server.
INPUT PARAMETERS
args boot argument:
"s" for single user mode
"r" to reconfigure devices
"rs" to reconfigure devices and boot in single user mode
if none argument is specified then normal boot is performed
INITIAL STATUS
The operating system is halted under OBP.
A console terminal on the machine is available (for server without screen and keyboard the deported
console is available on the supervisory workstation).
ACTIONS
1. Boot the system:
on the console terminal of the machine:
<#.> ok boot [-args] ↵
2. If the args argument includes the "s" for single user mode: enter the root password.
Resetting ....
.....
Rebooting with command : -.s
.....
INIT: SINGLE USER MODE
Type Ctrl-d to proceed with normal startup,
(or give root password for system maintenance): enter the root
password ↵
.....
#
FINAL STATUS
The operating system is rebooted.

OMC-R DATA ARCHIVING\RESTORING

SCOPE
The purpose of this sheet is to describe how to:
• archive the OMC-R environment data (BDE, configuration data…) for the current day (today)
• restore the OMC-R environment data for specific day
• archive the OMC-R daily data (observations, alarms...) for the last 3 days before today
Note: The daily data for the current day cannot
be archived
• restore the OMC-R daily data collected for a specific day
• archive PCUOAM configuration
• restore PCUOAM configuration
Required resources, if the backup media is not a backup server: DAT with the previous data archive
for restoration or blank DAT (or DAT used previously to archive OMC-R daily or environment data with
enough space left) without protection for archiving.
For Integrated configuration: USE ONLY DAT OF DDS-4 OR DAT-72 TYPE.
INPUT PARAMETERS
RefDocLabel Reference document
INITIAL STATUS
If you perform daily data archiving/restoration: the OMC-R is running.
If you perform archiving of environment data: the OMC-R is running.
If you perform restoration of environment data: the OMC-R is halted.
If you perform PCUOAM archiving/restoration: the OMC-R must be running on both the active server
and the PCUOAM workstation (in case of single or dual OMC-R configuration) or on the integrated
server (in case of integrated OMC-R configuration).
An omc session is available on the OMC-R server.
ACTIONS
1. If not yet done, open a shell session of the omc account, on the active OMC-R server.
The media should have a label to perform archiving/restoring.

Refer to [RefDocLabel] to for details on working with labels associated with DAT and NFS backup
server.
2. If the backup media is a DAT,

• Insert a DAT in the DAT drive of the active server, if not yet done.
• If you use blank DAT then assign a label
• If the DAT already has a label and you don’t know the label name: get the label name
from DAT
• If you are not sure there is a label then: try to get the label name from DAT
3. If the backup media is NFS backup server, in the OMC-R define the label pointing to NFS
backup server, if not yet done
4. Now the media label is known (labelName below). You will need it to go on for next steps.

5. If you perform restoration, you need to know for which date (specificDay below) the data have to
be restored. Format for this parameter is: YYYYMMDDHHMM for environment data or
YYYYMMDD for others data type.
If you don’t know the value for specificDay, list available values:
Type at the command prompt of the omc account shell on the OMC-R server:
... (omc) % /CMN/base/exe/cf_save_tool.x -o list -l labelName ↵
The data for several days can be stored on the media.
6. Perform appropriate section correspondingly to data type and action type:
If you perform environment data archiving:

{
6.1. Run the archiving utility:

... (omc) % /CMN/base/exe/cf_save_tool.x -o archive
-l labelName -y backup ↵
Note: The number of GSM objects in the OMC-R configuration will be automatically checked by
tool
}
If you perform environment data restoration:

{
6.1. Restore the environment data:
... (omc) % /CMN/base/exe/cf_save_tool.x -o restore
-l labelName -y backup -t specificDay ↵
6.2. Restore the configuration data:

... (omc) % /CMN/base/exe/cf_save_tool.x -o retrieve_cfg
-l labelName -y backup -t specificDay ↵
6.3. Set the ownership:

Type at the command prompt of the root account shell on the OMC-R server:
# /CMN/base/install/shell/cf_set_rights.sh -PNPE_OMC_FULL
-PR/ -f=NOMINAL -FORCE ↵
}
If you perform daily data archiving:

{
6.1. Chose number of days (daysNumber) for which daily data will be archived (the possible
values are: 1, 2 or 3).
6.2. Run the archiving utility for each value of n in the range from 1 to daysNumber :
{
Under omc login:
... (omc) % /CMN/base/exe/cf_save_tool.x -o archive -l labelName
-y daily -p omc –t d-n ↵

Under omc login:

... (omc) % /CMN/base/exe/cf_save_tool.x -o archive -l labelName
-y daily -p md –t d-n ↵
}
}
If you perform daily data restoring:

{
6.1 Run the restoration utility for omc part:
-l labelName -y daily -t specificDay -p omc ↵
6.2. Run the restoration utility for md part:

-l labelName -y daily -t specificDay -p md ↵
}
If you perform PCUOAM configuration archiving:

{
6.1. Run the archiving utility:
... (omc) % /CMN/base/exe/cf_save_tool.x -o archive
-l labelName -y pcuoam -p omc ↵
}
If you perform PCUOAM configuration restoration:

{
6.1. Run the restoration utility:
-l labelName -y pcuoam -t specificDay -p omc ↵
}
7. Wait till the utility execution is complete:
... successfully completed
8. If you perform PCUOAM configuration archiving on DAT, make sure that storage operation
passed well:
8.1. Rewind the tape:

... (omc) % mt -f /dev/rmt/0n rewind ↵
8.2. Type the following command as much time as it is necessary to insure that storage
operation passed well (this command permits to list data contained in the DAT):
... (omc) % tar tvf /dev/rmt/0 ↵

9. If the backup media is a DAT, eject the DAT from the DAT drive.
10. If you have performed archiving on the DAT, make it write-protected by sliding the tab.
TROUBLE SHOOTING
1. See the log file /CMN/base/diagnostic/diag_savetool
2. If you have "Server is not the most recent one" message:
2.1. Execute the following command:

Type at the command prompt of the croot account shell on the OMC-R server:
... (root) # /usr/local/oam/bin/ds_restoreMaj.sh -configSybase
-configure -Y ↵
2.2. Re-launch the OMC-R environment data restoration.
FINAL STATUS
The OMC-R data are now archived or restored.

LX-8020S DEPORTED CONSOLE OPENING

SCOPE
The sheet describes how to get a deported console, by opening a telnet connection on one of the LX-
8020S terminal server ports, on a supervisory workstation or any computer owning a screen and a
keyboard.
INPUT PARAMETERS
terminal_server_hostname : Host name of LX-8020S Terminal Server
port_number : Number of the LX-8020S port connected to the computer
INITIAL STATUS
The supervisory workstation is available and its Ethernet link is connected to the network.
ACTIONS
) ON THE SUPERVISORY WORKSTATION
1. If a shell window is not available: Open a shell session using croot login.
2. Update the appropriate environment variable of the deported console to use the "vi" editor:
Type at the command prompt of the root or croot account shell:
...(root) # setenv TERM sun-cmd ↵
3. Enter the following command to launch the deported console connection, where telnet_port =
2000 + port_number*100:
The following example helps specify accordance between LX-8020S serial port and virtual
port identifier.
Example: port_number = 15: telnet_port = 3500

↵
FINAL STATUS
Connection established

LX-8020S CONSOLE CLOSING

SCOPE
The sheet describes how to close deported console previously open on the LX-8020S terminal server.
And how to close the management console was opened for administrative needs.
INITIAL STATUS
The Ethernet link is connected and telnet connection over it is available
or
A telnet connection over the DIAG/MGMT port is available.
ACTIONS
Enter the following line to log out from a LX-8020S terminal server port:
If telnet connection is available over Ethernet and deported console is opened:
{
{1} ok [Ctrl],[]]
telnet> quit ↵
Connection to <LX-8020S_IP_ADDRESS> closed.
}
Else if telnet connection is available over DIAG/MGT port to the LX-8020S:

{
InReach:0 >>[Ctrl],[d]
Welcome to MRV Communications, In-Reach Product Division.

Port 0 Speed 9600
Login:
}
Else if telnet connection is available over Ethernet to the LX-8020S:
{
InReach:0 >>[Ctrl],[d]
telnet> quit ↵
Connection to <LX-8020S_IP_ADDRESS> closed.
}
FINAL STATUS
Console is closed.

FILE SYSTEM BACKUP ON DVD OPERATIONS

PRESENTATION
The purpose of this sheet is to back up the local file systems of an U45 workstation.
Required resources:
- At least, one DVD disk to back up the U45 workstation without CIUS software installed or two
DVD disks to back up the U45 workstation with the CIUS software installed:
Please use the following types of DVD media:

• DVD+RW / DVD-RW 4x
• 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.
- CIUS DVD-ROM Solaris 10 (labelled "DVD_OAMGSM_SOL10")
INPUT PARAMETERS
step: indicates what backup step is performed:
estimation - backup data size estimation
images_creation - images creation
burning - burning images
installing_boot_image - installing PE_BOOT_DVD image into the
work directory
excl_file: name of the file with the excluded data list
incl_file: name of the file with the included data list
INITIAL STATUS
ACTIONS
Perform appropriate section correspondingly to the value of the step parameter:
If step = installing_boot_image:
{
1. Insert the CIUS DVD-ROM Solaris 10 into the DVD-RW drive of the computer.
Wait until the OS recognizes the disk (a window with the disk contents like as follows will
pop up):

Note: Normally it takes about 20 seconds for the OS to recognize the DVD. If the
CIUS DVD-ROM is not recognized after 1 minute, it may mean that the disk has
mechanical defects. In this case, eject the disk with the DVD-RW drive ‘eject’ button
and try to insert another CIUS DVD-ROM Solaris 10.
2. Install PE_BOOT_DVD image into the work directory:

# /usr/local/oam/bin/tip_backup_dvd.sh -Y –install ↵
3. Take off automatically ejected CIUS DVD-ROM disk.

}
If step = estimation:
{
# /usr/local/oam/bin/tip_backup_dvd.sh -Y –C [-X<excl_file>]
[-I<incl_file>] ↵
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. If the DVD is bootable (that means you will need
to boot from this DVD to make a restoration), it is indicated in parenthesis.
o Then DVD contents are listed. For each backed up partition its name and the
size of dump in kilobytes are specified. If you see “[vol #x]” after the partition
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. If the DVD is
bootable, special set of data “OS&tools” is also put on the DVD so that it is
possible to boot the computer from this DVD and start the restoration.
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 kilobytes)

- 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 (bootable):
------------------
OS&tools 458880 Kb
/ 2325813 Kb
/var 346699 Kb
/OMC 185330 Kb
/OMC/maps 174 Kb
/home [vol #1] 1250021 Kb
Totally filled/DVD capacity: [ 4566917 / 4566917 ] Kb
Remained free space on DVD: 0 Kb
DVD #2:
-------
/home [vol #2] 3165827
Totally filled/DVD capacity: [ 3165827 / 4566917 ] Kb
Remained free space on DVD: 1401090 Kb
****** Excluded data (Kbytes):

/var/sadm/pkg/SUNWcsr/save/pspool/SUNWcsr/reloc/var/adm/wtmpx 199
/var/sadm/pkg/SUNWcsr/save/pspool/SUNWcsr/reloc/var/adm/utmpx 199
/var/adm/utmpx 172
/var/crash/nepo45loghost 171
/home/backup 25521480
/home/lost+found 2999
/home/nedit-5.4-solaris-sparc 4742
/home/tip 3069
/home/users/tools 2987
** Excluded by a user
/home/users/data/tmp_01.dat 100
Total excluded: 25535277
** Included by a user
/var/adm/messages 126
/var/adm/messages.0 134
Total included: 260
Total DVD data size: 7732744 Kb

****** Estimated time to create DVD images: 1 hour(s) 11 min 29 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:
{
# /usr/local/oam/bin/tip_backup_dvd.sh -Y [-X<excl_file>]
[-I<incl_file>] ↵
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”.
2. Switch to multi-user mode by pressing [Ctrl]-[d] combination on the keyboard.

# [Ctrl][d]
svc.startd Returning to milestone all
If step = burning:
{
# /usr/local/oam/bin/tip_backup_dvd.sh -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 is 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 15 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. If you are sure in
good quality of the used disks, you may skip this step to save time.
To start verification, run the following command:

# /usr/local/oam/bin/tip_backup_dvd.sh -Y -verify ↵
For every backup DVD, the tool will ask:

{
type 'ver' to start its verification (or 'exit' to exit from
the tool):
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:
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 : Backup DVD #X verification has failed
ERROR : The disk has bad (non-readable) sectors and
cannot be used for restoration
ERROR : 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 with
the following command (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/oam/bin/tip_backup_dvd.sh -Y -burnX ↵
(where X is a number of the defective backup DVD)
}
4. After all images are successfully burned, it is recommended that you remove images from
the work directory:
# /usr/local/oam/bin/tip_backup_dvd.sh -Y -purge ↵
}
TROUBLE SHOOTING
1. The log files of the tool are in /var/local/oam/tip_backup_dvd (or the log files may be in
/tmp/tip_backup_dvd 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:
# 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:
Type at the command prompt of the root or croot account shell on the
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.
FINAL STATUS
The necessary step is completed.

DEFINING EXCLUDED AND INCLUDED DATA LISTS WHEN

PERFORMING BACKUP ON DVD
PRESENTATION
The purpose of this sheet is to describe how to define excluded and included data lists when
performing a backup on DVD.
INPUT PARAMETERS
excl_file: name of the file with the excluded data list
incl_file: name of the file with the included data list
INITIAL STATUS
ACTIONS
It is possible to exclude or include a number of files (and/or directories) from the whole backup data
set. To do this, you need to create files with exclude and include lists, respectively, basing on the
following rules:
- Excluded elements are specified line by line
- Excluded elements can be either files or directories
- Wildcard characters cannot be used in file names
- You can temporarily comment some files with the “#” symbol
1. If you need to exclude a number of files:
• create file <excl_file> with any text editor and put all excluded files line by line basing on
the rules specified above.
Note:
By default, tip_backup_dvd.sh excludes the following files defined in its internal exclude list:
- All core files present on the disk
- All wtmpx files present on the disk
- All utmpx files present on the disk
- All messages.* files from directory /var/adm
- All gcore files from directory /CMN/base/diagnostic
- Directory /var/crash
- Directory /home except files in directories /home/omc /home/CIUS /home/TT_DB
/home/users/data (hence, work directory /home/backup/DVD is excluded by default)
2. If you need to include certain files, which were excluded as a part of the internal or user excluded
data list, you can use included data list for this purpose:
• create file <incl_file> with any text editor and put all included files line by line basing on
the rules specified above.
Examples of user exclude and include lists:


Exclude list:
/home/CIUS/products
/home/users/data/tmp_01.dat
Include list:
/var/adm/messages
/var/adm/messages.0
TROUBLE SHOOTING
None.
FINAL STATUS
Excluded and/or included data lists are defined.

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

Type at the command prompt of the root or croot account shell on
the computer:
# /bin/cdrw -b fast ↵
}
TROUBLE SHOOTING
None
FINAL STATUS
DVD-RW disks are blanked.

9. ABBREVIATIONS AND DEFINITIONS

9.1. ABBREVIATIONS
BDE OMC-R operations database
CD-ROM Compact Disk Read Only Memory
DAT Digital Audio Tape (magnetic cartridge)
DVD Digital Versatile Disk
E4500 Sun Enterprise™ server family
Gb Gigabyte
HDI High Disk capacity with Internal disks
MD Mediation Device
MDM Multiservice Data Manager
OMC-R Operation and Maintenance Centre - Radio part
OS Operating System
PCU Packet Control Unit
PCUSN PCU Support Node
SB150 Sun Blade™ 150 workstation
SB1500 Sun Blade™ 1500 workstation
SCSI Small Computer Standard Interface
SDO "Serveur de Données de l’OMC-R" (OMC-R Data Server)
SDS Solstice DiskSuit™
SVM Solaris Volume Manager
SF880 Sun Fire™ 880 server
SF890 Sun Fire™ 890 server
T3 Sun StorEdge™ T3 Disk Tray
U45 Sun Ultra™ 45 workstation
U5 Sun™ Ultra-5 workstation
9.2. DEFINITIONS
Data mirroring Process whereby the data is updated on OMC-R server(s)

disks.
Disks array device External storage device (T3)
Integrated OMC-R The OMC-R software that integrates 4 roles: OMC-R server,
PCUOAM, SDO and X-terminal server on one single OMC-R
server.
Master DAT DAT, which contains all the software and the tools to install or
to upgrade an OMC-R server or an OMC-R workstation:
Installation and upgrade tools
OEM software and patches
OEM software Trade software such as Sun™ Solaris™ operating system,
SUNLink®, Sybase, etc.
OMC-R The OMC-R software installed on an OMC-R server or an
OMC-R workstation.

PCUOAM Workstation, which hosts at least OMC-R, NMS, MDP

software.
SDO Application that allows the user to interface in a pre-defined
ASCII format with configuration management, performance
management and fault management.
Sun Fire™ server Sun Fire™ 880 or Sun Fire™ 890 server
Supervisory Dedicated Sun™ workstation on which the system console of
workstation an OMC-R server used without graphic display or keyboard is
monitored. For stability and reliability purposes, OMC-R hosts
(servers or workstations) must not be used as supervisory
workstations.
System at the OBP System under control of processor monitor. The operating
level system is not running, as after a shutdown (init 0).
Z END OF DOCUMENT Y

Dsomcapp000016 1111e

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

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

Dsomcapp000016 1111e

Hochgeladen von

Copyright:

Verfügbare Formate

OMC-R Preventive Maintenance Backup

Document number: DS/OMC/APP/000016

Copyright© 2006-2007 Nortel Networks, All Rights Reserved

Nortel Networks confidential