Spots 10.0 Installation

E200301-01-115-V10.0I-06

SIEMENS S.A.

SPOTS V10 Drop 4

Installation Guide

November/2003

SIEMENS S.A.OG IC, R&D WON NM P3

R. Irmãos Siemens, nº 12720-093 AmadoraPortugal

All rights reserved. No part of this document may be reproduced or transmittedin any form or by any means, electronic or mechanical, including photocopyingand recording, for any purpose other than the purchaser’s personal use withoutthe written permission of Siemens S.A.This document consists of a total of 175 pages (7 Annexes included).The information contained in this document is subject to change.

Installation Guide (SPOTS V10 Drop 4) Siemens S.A.

E200301-01-115-V10.0I-06 i

Table of Contents

1 INTRODUCTION ...........................................................................................................................................51.1 SPOTS documentation .......................................................................................................................................61.2 Target group and structure of this manual..........................................................................................................7

1.2.1 Document Conventions.............................................................................................................................7

2 GENERAL OVERVIEW..................................................................................................................................82.1 Platform Hardware & Standard Software.........................................................................................................10

2.1.1 SPOTS PMS and PMC (Solaris� environment).....................................................................................102.1.2 SPOTS PMC (Windows� environment) ................................................................................................12

2.2 Collecting information .....................................................................................................................................132.3 Hard Disk Partitioning .....................................................................................................................................15

3 INSTALLATION PROCEDURE OVERVIEW....................................................................................................173.1 Initial Installation .............................................................................................................................................183.2 APS upgrade ....................................................................................................................................................19

3.2.1 APS Upgrade without Database re-installation.......................................................................................233.2.2 APS Upgrade with Database re-installation ............................................................................................26

3.3 Data Migration .................................................................................................................................................273.3.1 Data Migration overview ........................................................................................................................273.3.2 Extracting data from an existing SPOTS system.....................................................................................29

3.3.2.1 Extraction using dbArchive........................................................................................................293.3.3 Regenerating extracted data on the newly installed SPOTS system........................................................30

3.3.3.1 Regeneration using dbArchive ...................................................................................................303.3.4 Stopping SPOTS.....................................................................................................................................313.3.5 Installing SPOTS Data Migration package .............................................................................................333.3.6 Dump existing data into tape(s) ..............................................................................................................343.3.7 Recovering regenerated data from tape(s)...............................................................................................353.3.8 Removing the SPOTS Data Migration package ......................................................................................413.3.9 Post Migration configuration files update...............................................................................................413.3.10 Starting SPOTS.....................................................................................................................................42

4 INSTALLING THE OPERATING SYSTEM.......................................................................................................434.1 Getting Started .................................................................................................................................................434.2 Configuring the System....................................................................................................................................464.3 Installing Solaris� ...........................................................................................................................................484.4 Installing Solaris� Patches ..............................................................................................................................52

5 FAULT TOLERANCE WITH DISK MIRRORING..............................................................................................545.1 Setup Tasks ......................................................................................................................................................55

5.1.1 Installing Solstice DiskSuite� Software .................................................................................................555.1.2 Configuring Disk Mirroring....................................................................................................................55

5.1.2.1 Configuring System Disk Mirroring...........................................................................................565.1.2.2 Configuring Full Disk Mirroring................................................................................................57

5.2 Maintenance Procedures ..................................................................................................................................595.2.1 Monitoring Tasks ....................................................................................................................................59

5.2.1.1 DiskSuite� Objects....................................................................................................................595.2.1.2 Disk Failure Notification via Email............................................................................................605.2.1.3 Verifying the Status of State Database Replicas ........................................................................605.2.1.4 Verifying Status of Metadevices ................................................................................................61

5.2.2 Replacing mirroring disks .......................................................................................................................625.2.3 Booting system with insufficient database replicas.................................................................................645.2.4 Creating and Deleting DiskSuite� Objects.............................................................................................65

5.2.4.1 Creating a DiskSuite� State Database Replica ..........................................................................655.2.4.2 Removing a DiskSuite� State Database Replica .......................................................................665.2.4.3 Creating a DiskSuite� submirror...............................................................................................665.2.4.4 Removing a DiskSuite� submirror ............................................................................................665.2.4.5 Removing a DiskSuite� Mirror and Submirrors........................................................................675.2.4.6 Unmirroring a File System That Cannot Be Unmounted ...........................................................69

5.2.5 Formatting Disks.....................................................................................................................................715.2.6 Creating File Systems .............................................................................................................................73

Siemens S.A. Installation Guide (SPOTS V10 Drop 4)

ii E200301-01-115-V10.0I-06

5.2.7 Associating Disk ids to WWNs and Rack Numbers................................................................................735.2.8 Detect and terminate processes that are using a filesystem .....................................................................75

5.3 De-installation Tasks........................................................................................................................................785.3.1 Un-mirroring Disks .................................................................................................................................785.3.2 De-installing Solstice Disksuite� Software ............................................................................................79

6 INSTALLING ORACLE� SOFTWARE ...........................................................................................................806.1 Creating Groups and Users...............................................................................................................................806.2 Installing Oracle� Software.............................................................................................................................836.3 Installing Oracle� Patch Set ............................................................................................................................886.4 De-installing Oracle� Software .......................................................................................................................90

7 INSTALLING SPOTS SOFTWARE (SOLARIS� ENVIRONMENT) ...................................................................917.1 Adding SPOTS SW with admintool.................................................................................................................927.2 Adding SPOTS Software with Package Commands.........................................................................................957.3 Package Installation .........................................................................................................................................97

7.3.1 NIS Users and Groups Requirements......................................................................................................977.3.2 SPOTS Naming Server ...........................................................................................................................977.3.3 SPOTS Application Server .....................................................................................................................997.3.4 SPOTS CLient (Solaris� variant).........................................................................................................1017.3.5 SPOTS Database Server........................................................................................................................1037.3.6 SPOTS Data Migration .........................................................................................................................106

7.4 Post-Installation Procedures...........................................................................................................................1077.4.1 Installing SPOTS Database ...................................................................................................................109

7.5 NMS Configuration........................................................................................................................................1117.5.1 NMS Configuration File .......................................................................................................................1117.5.2 OMC-S Access Specifics ......................................................................................................................1127.5.3 SC Access Specifics..............................................................................................................................1137.5.4 @vantage Commander Access Specifics ..............................................................................................1147.5.5 OMC-B Access Specifics......................................................................................................................1157.5.6 RC Access Specifics .............................................................................................................................1157.5.7 IPM Access Specifics............................................................................................................................1177.5.8 IPM Converter Specifics.......................................................................................................................118

7.6 SPOTS Licensing Software............................................................................................................................1207.6.1 Configuring SPOTS licenses.................................................................................................................1207.6.2 Updating the SPOTS licenses ...............................................................................................................121

8 INSTALLING SPOTS-PMC (WINDOWS� ENVIRONMENT) .......................................................................1228.1 Installation sequence ......................................................................................................................................1228.2 Troubleshooting .............................................................................................................................................1258.3 SPOTS License checking ...............................................................................................................................126

9 UNINSTALLING SPOTS SOFTWARE (SOLARIS� ENVIRONMENT) .............................................................1279.1 Stopping SPOTS applications ........................................................................................................................1279.2 De-installing SPOTS database .......................................................................................................................1279.3 Removing SPOTS Packages...........................................................................................................................128

9.3.1 Removing SPOTS Packages with admintool ........................................................................................1289.3.2 Removing SPOTS Packages with Package Commands ........................................................................129

10 DE-INSTALLING SPOTS-PMC (WINDOWS� ENVIRONMENT) ...............................................................13010.1 Files not removed during de-installation......................................................................................................131

11 ABBREVIATIONS ...................................................................................................................................132

12 REFERENCES.........................................................................................................................................134

ANNEX 1 – DISK PARTITIONING - RAID EXTENSIONS................................................................................135

ANNEX 2 – UNIX ENVIRONMENT VARIABLES ...........................................................................................139

ANNEX 3 – DOMAINS’ CONFIGURATION ....................................................................................................145

ANNEX 4 – SERVER CONFIGURATION FILES...............................................................................................149

ANNEX 5 – CONFIGURATION WORKSHEET ................................................................................................155

ANNEX 6 – INITIAL INSTALLATION TASK FLOW.........................................................................................163

ANNEX 7 – SYSTEM BACKUP & RESTORE .................................................................................................167


E200301-01-115-V10.0I-06 iii


E200301-01-115-V10.0I-06 5

1 Introduction

The SPOTS product belongs to the family of Network Management Systems providedby Siemens (ICM N), for the Operation and Maintenance of Mobile Networks (Core,GERAN and UTRAN sub-networks).

The SPOTS product integrates the platform (consisting of hardware and standardsoftware) and application software that supports the Performance Management activitieson the network.The SPOTS V10 Drop 4 application software includes a mandatory Long-Term part andan optional, additional Real-Time part.

The SPOTS V10 Drop 4 Long Term provides performance management analysiscapabilities, allowing to produce pre-defined and user-defined reports with PerformanceManagement indicators based on data periodically collected from the network.

The SPOTS V10 Drop 4 Real Time part provides near real-time updates of the networkPerformance Management information, allowing to define threshold values forPerformance Management indicators that result in alarms when they are violated. Theoptional module "SNMP Alarm Agent" allows these alarms to be forwarded via SNMPto an external application.

This document describes the installation procedures for the SPOTS V10 Drop 4mandatory part, that is, for the Long-Term part. The description of the SPOTS V10Drop 4 Real-Time installation is provided in [3].


6 E200301-01-115-V10.0I-06

1.1 SPOTS documentation

The SPOTS Long-Term application documentation consists of the following parts:

ManualsDocument the application and provide the necessary information for its operation.

They are available (with the SPOTS Long-Term SW) in the SPOTS distribution media(CD-ROM).

Release NotesSummarizes the authorized versions of the hardware and software products and up-to-date information about user notes, functional limitations and error corrections. TheRelease Notes are applied for a specific release of this SPOTS version (including boththe Long-Term and the Real-Time part).

SPOTS V10.0.x – Release Notes — refer to [2]

On-line helpProvides a complete “on-context “ description of the system functionality.


E200301-01-115-V10.0I-06 7

1.2 Target group and structure of this manual

The Installation Guide is intended for System Administrators and for those who installthe SPOTS product. On the server side, it describes the necessary procedures to performthe initial installation, APS upgrades, configuration and de-installation of the SPOTSsystem 1), specific chapters are dedicated to the installation and de-installation of theWindows� variant (NT / 2000 / XP) of the SPOTS Client.

Chapter 2 describes the functional components of the SPOTS system. It also lists theinformation that must be gathered before starting the initial installation.

Chapter 3 contains an overview of the required procedures for the initial installationand system upgrade. For the installation procedures, refer to Chapter 4 throughChapter 7.

�� Perform the installation procedures as described in this manual. Deviations canresult in malfunctioning.

1.2.1 Document Conventions

The following textual and graphic conventions are used in this document:

Convention Meaning

# The UNIX� super-user default prompt.Boldface Emphasises important word or concept.

<expression>An expression enclosed within angle brackets indicates somevalue to be input that cannot be determined in beforehand and soit should not be taken literally.

� Important notice or warning.� Action that requires user interaction.

� Note or relevant event triggered by some action.� Indicates that a certain procedure is completed.

1) As a prerequisite, please read the corresponding Release Notes.


8 E200301-01-115-V10.0I-06

2 General Overview

The SPOTS system comprises several functional components, grouped into installableSW packages according to a Client/Server approach:

SPOTS Performance Management Client (PMC)• SPOTS Client (SCL)

SPOTS Performance Management Server (PMS)• SPOTS Application Server (SAS)• SPOTS Database Server (SDS)• SPOTS Naming Server (SNS)

Operating System (Solaris 8)

SPOTS-PMS

Network (TCP/IP)

Application Service

Corba

Database Utilities

Task Scheduler

SAS

PM File Converters

Location Service

NamingService

Corba

SNS

Database Service

Oracle8 Corba

SDS

Data Collection

SCL SPOTS-PMC

SPOTS Client

Corba

JRE

Operating System (Solaris 8 or NT/2000)

Figure 1 – SPOTS structure

�� The (SAS) Data Collection gathers the PM data that is produced in the NEs. Thisis done using the collection services provided by the corresponding NMSs. Hence,the configuration procedures, required to allow the interoperability betweenSPOTS and the NMS (refer to Section 7.5), assume critical relevance.

SPOTS PMS components may be installed in two different configuration types: SingleServer and Distributed — details on these configurations are described in [1], Section1.2 (Environment).

SPOTS PMC will be installed on each user’s workstation implementing the SPOTSGraphical User Interface (GUI).The SPOTS PMS components are available on Solaris� 8 (release 2/02).The SPOTS PMC component (SCL) is available in the following operating systems:

• Solaris� 8 (release 2/02)• Windows� NT 4.0 with Service Pack 6a (or higher)• Windows� 2000 with Service Pack 3 (or higher)• Windows� XP


E200301-01-115-V10.0I-06 9

It is possible to install the SPOTS PMC on the same system as the SPOTS PMS.However, due to performance reasons, intensive usage of SCL in this configuration (e.g.for frequent execution of performance reports) is not recommended. In a normal opera-tion environment, this SPOTS PMC configuration is suitable only for sporadic actions(e.g. administrative actions).

Complete information about how to install and de-install SPOTS PMC in a system withWindows� is presented in Chapter 8 and Chapter 10 whilst SPOTS PMC installationand de-installation in Solaris� is presented along with SPOTS PMS installation and de-installation in Chapters 7 and 9.


10 E200301-01-115-V10.0I-06

2.1 Platform Hardware & Standard Software

2.1.1 SPOTS PMS and PMC (Solaris�� environment)

Hardware

For SPOTS PMC, any UltraSPARC-II/III based workstation (with the standard configu-ration) can be used. The only constraint (applied only to UltraSPARC-II workstations) isthat they must support the installation of Solaris� 8 (release 2/02).

For SPOTS PMS, and depending on the managed network size, the following configu-rations are certified for this SPOTS version:

� The used HW should be chosen according to the information provided by yourSiemens representative, who will help you determine which configuration best fitsyour network.

�� The described HW configurations are applied to the Single Server scenario; for theDistributed environment, HW configurations will be provided on request —details on Single Server and Distributed environments are described in [1],Section 1.2 (Environment).

Small ConfigurationUltraSPARC-II based Workstation

Sun Ultra 60 (1x 360 or 450 MHz CPU) with:– 1 GB RAM;– 2 internal disks (minimum disk size: 18 GB).

UltraSPARC-III based WorkstationSun Blade 2000 (1 x 900 MHz CPU) with:

– 1 GB RAM;– 2 internal disks (minimum disk size: 18 GB).

Medium ConfigurationUltraSPARC-II based Workstation

Sun Ultra 60 (2x 360 or 450 MHz CPU) with:– 2 GB RAM;– 2 internal disks (minimum disk size: 18 GB);– StorEdge Multipack (Fibre Channel) with 6 disks (minimum disk size: 18 GB).

UltraSPARC-III based WorkstationSun Blade 2000 (2 x 900 MHz CPU) with:

– 2 GB RAM;– 2 internal disks (minimum disk size: 18 GB);– StorEdge Multipack (Fibre Channel) with 6 disks (minimum disk size: 36 GB).


E200301-01-115-V10.0I-06 11

Large ConfigurationUltraSPARC-III based Server

Sun Fire V880 (4 x 900 MHz CPU) with:– 8 GB RAM (standard configuration);– 6 or 12 (RAID 1 option) internal Fibre Channel disks (minimum size: 36 GB)

UltraSPARC-III based ServerSun Fire V880 (2 x 900 MHz CPU) with:

– 4 GB RAM;– 6 or 12 (RAID 1 option) internal Fibre Channel disks (minimum size: 36 GB)

The following additional items must be included:• (Standard) 21 inch colour Monitor;• CD/DVD-ROM drive;• 4mm or 8mm Tape Driver;• PostScript Printer.

�� The tape driver mentioned above is required only for Small configurations.For Medium and Large configurations, a Legato� based solution is available for“Backup & Restore”. This solution requires the usage of an auto-changer device.

It is recommended to provide the information that is required in [2], Annex 1 (OrderSheet for SPOTS V10 Licensing File). This information shall be used, by your Siemensrepresentative, to calculate the SPOTS configuration that best fits the size of yournetwork.

Standard Software

The following standard software products are used in SPOTS:• Solaris� Operating System (Solaris� 8, 2/02).• Common Desktop Environment (CDE, V1.4.1) — available in the Solaris� CD.• Oracle� RDBMS Server software (V8.1.7, 32 bit).

SPOTS Software

The SPOTS SW consists of several packages, collectively known as APS — seeChapter 7 for a detailed description of the SPOTS software packages.


12 E200301-01-115-V10.0I-06

2.1.2 SPOTS PMC (Windows�� environment)

Hardware

The following minimal configuration is required:

Requirement Value CommentProcessor Pentium or equivalent SuggestedMemory 128 MB SuggestedVirtual memory 256 MB SuggestedHard disk space 55 MB MandatoryVideo resolution 800x600 pixels MandatoryVideo depth 256 colours Mandatory

The available hard-disk space must be located on a local non-removable drive.

Standard Software

The Windows� SPOTS Client uses the following standard software products:• Microsoft Windows� NT 4.0 with Service Pack 6a (or higher), or Microsoft

Windows� 2000 with Service Pack 3 (or higher) or Windows� XP.• TCP/IP protocol.

SPOTS Software

The SPOTS-PMC Windows� variant is installed according to the procedure described inChapter 8.


E200301-01-115-V10.0I-06 13

2.2 Collecting information

During the initial SPOTS installation, you are asked for parameterisation information tobe used in the system. You should therefore understand the topics covered in thisChapter, before starting the software installation; use the Annex 5 to register therelevant information for each host.

Workstation/server configuration parameters

Host name The workstation name, as specified in /etc/hostsExample: “pms01”

Host IP address The network administrator assigns the workstation/serverInternet Protocol address.Example: 129.200.9.1

Netmask for subnets The value you enter depends on the internet address classand whether sub-networks are used (see table below).Example: 255.255.225.0

Default Router Specify a default IP router or let Solaris� installationprogram find one. In the first case provide the “Router IPaddress”.

Geographical region Choose one of the possible values.Example: “Europe”

Time zone Choose one of the possible values.Example: “Middle Europe”

Internet address classes and default netmasks

AddressClass

Byte1 Byte2 Byte3 Byte4 Default Netmask

A 0-127 1-254 1-254 1-254 255.0.0.0B 128-191 1-254 1-254 1-254 255.255.0.0C 192-223 1-254 1-254 1-254 255.255.255.0

SPOTS installation data

SPOTS Naming Server Use this field to record the SPOTS Naming Server IPAddress and TCP/IP Port configured during its installation.This might be useful since SAS, SDS and SCL all need thisinformation.

Database configuration Decide which SPOTS database configuration to use: Tiny(for demonstration purposes only), Small, Medium or Large.

Note:Contact your Siemens representative to know whichconfiguration best fits your network and realize thecorresponding hard disk requirements in the followingsection.


14 E200301-01-115-V10.0I-06

Fault Tolerance configuration dataBefore you begin the OS installation you must fill the Fault Tolerance information inAnnex 5.


E200301-01-115-V10.0I-06 15

2.3 Hard Disk Partitioning

This section describes the disk partitions to be created (during Solaris 8 installation), foreach of the HW configurations presented in Section 2.1. An additional alternative ispresented: the Tiny configuration, for use only for field trial and demo purposes.

On Annex 1, the additional partitions required for HW configurations supportingmirrored disks are described.

�� The described disk partitioning is applied to the Single Server scenario; for Distri-buted configurations, the disk partitioning of each platform will be provided onrequest — details on Single Server and Distributed environments are described in[1], Section 1.2 (Environment).

The following table presents the minimum partitions sizes on each HW configuration.These values guarantee a SPOTS successful installation. For each of the configurations,three columns are presented1: the minimum required partition size, the hard disk whereit must be placed, and the partitions to be extended if more disk space is available.

The installer must extend the partition sizes, increasing them to cover all the availabledisk space.

The rules for extending the partition sizes follow, in order of precedence:

1. Small configuration, disk1: Consider the amount of free disk space afterallocating the minimum partition sizes. Allocate 2/3 of the free disk space toextend the /spots_db5 partition, and the remaining 1/3 to extend the/spots_db6 partition.

2. Small configuration, disk0: analogous to the above, but allocating ½ of thefree space to /spots_db3 and ½ to /spots_db4.

3. Other partitions marked Yes in the Extend column: allocate all of theavailable disk space to extend the partition.

4. For the disks where disk space is still available, extend one of the partitionsin the disk.

In practical terms, the first two rules reduce to: in the Small configuration, split theavailable space in disk 0 among /spots_db3 and /spots_db4 in equal parts, and theavailable space in disk 1 among /spots_db5 and /spots_db6 maintaining their relativessizes. On Medium and Large, as there is one dedicated disk per partition (among thosesupposed to grow), just assign the available space in each disk.

�� ‘/spots_arch’ partition should be created in Spots Medium and Largeconfigurations where the Backup & Restore option will be deployed. Only in thosecases these partitions shall be created.

1 A simpler approach is presented for the Tiny configuration.


16 E200301-01-115-V10.0I-06

Partition Tiny2 Small Medium LargeSize(GB)

Size(GB) Disk Extend



/ 1,5 1,5 0 3,5 0 3,5 0

/var/opt 1 1,5 0 2 0 4 0

swap 1 1 0 4 0 8 0

/export/home 0,5 1 0 1 0 1 0

/opt 1,5 2 1 2 0 2 0

/spots_arch - - - - 10 7 14 0

/spots_db1 2 3 0 5 2 8 1

/spots_db2 - 3 1 5 3 5 2

/spots_db3 - 4 0 Yes 9 4 Yes 9 2

/spots_db4 - 4 0 Yes 9 5 Yes 14 3 Yes

/spots_db5 - 7 1 Yes 9 6 Yes 16 4 Yes

/spots_db6 - 3,5 1 Yes 6 7 Yes 14 5 Yes

�� Use Annex 5 to register the selected configuration.

2 All the partitions to be created on Disk 0 if one disk available, or follow the same disk split as in the Small configuration, if twodisks are available.


E200301-01-115-V10.0I-06 17

3 Installation Procedure Overview

This chapter provides an overview of how to carry out the SPOTS installation.

Two different installation options exist: Initial Installation (Section 3.1) and APSUpgrade (Section 3.2).

The Initial Installation procedure applies for installing SPOTS from scratch.Additionally, the Initial Installation also applies when SPOTS is previously installed butdisk partition sizes need to be changed (see Section 2.3 for disk partitioninginformation).

If SPOTS is already installed and no partition resizing occurs, the APS Upgradeprocedure can be used for the transition to a new APS release of SPOTS software.

Either one of these options (Initial Installation / APS Upgrade) may or may not becoupled with a Data Migration procedure.The Data Migration procedure allows transferring data from an existing SPOTSinstallation (belonging to the current SPOTS version or to a previous SPOTS version)into a new SPOTS installation, for usage in this latter installation.Section 3.3 describes the steps for migrating data from an existing SPOTS version.(These steps are referred by the descriptions of the Initial Installation and APS Upgradeprocedures, as appropriate.)

�� Before executing the installation tasks (Initial Installation or APS Upgrade), andif applicable, assure that the existing SPOTS applications and all the associatedjobs and daemons are stopped — refer to the Section “Stopping SPOTS” in theInstallation Guide of the SPOTS version to be upgraded.

�� After executing the installation tasks (Initial Installation or APS Upgrade), per-form a system shutdown; execute, as root user, the following command:

# /etc/shutdown -y -g0 -i6


18 E200301-01-115-V10.0I-06

3.1 Initial Installation

Before installing SPOTS, one shall collect the necessary information, to serve asreference during the installation — see Annex 5. Refer to Annex 6, for an overview ofthe installation sequence.

The steps listed below have to be carried out for the Initial Installation.

�� Before proceeding, refer to [2] for possible specific recommendations on InitialInstallation.

1. Extracting data from an existing SPOTS system(This step applies only if it is desired to migrate performance data stored on anexisting SPOTS system, in order to use it on the SPOTS system to be installed.)Firstly, consult Section 3.3.1 to get a global overview of the data migrationprocedure.Then, perform the steps in Section 3.3.2 to extract data from the existing SPOTSsystem.

2. Installing Specific HardwareThe procedure to install the required hardware components is out of the scope ofthis manual. Refer to the hardware documentation.

3. Installing Standard SoftwarePerform the steps in Chapters 4, 5 and 6.

4. Installing SPOTS SoftwarePerform the steps in Chapters 7 and 8.

5. Regenerating extracted data onto the newly installed SPOTS system(This step applies only if it is desired to migrate performance data stored on anexisting SPOTS system, in order to use it on the newly installed SPOTS system.)Perform the steps in Section 3.3.3 to regenerate the data extracted in Step 1 ontothe newly installed SPOTS system.

6. Installing Real-Time software (if applicable)If the SPOTS Real-Time functionality is desired, install the respective software asdescribed in the Real-Time Installation Guide ([3]).

7. Setting the Oracle passwordExecute, as root user, the SPOTS command "setdbpwd" with the "-c" parameter(as described in [1]), to change the Oracle password for all SPOTS Databaseconnections.

�� The used password length must be between 6 and 8 characters.


E200301-01-115-V10.0I-06 19

3.2 APS upgrade

Before upgrading SPOTS, collect the necessary information, to serve as reference duringthe installation — see Annex 5.

�� For security reasons, a System Backup shall be performed, before executing APSupgrade procedure; if any unrecoverable error occurs during its execution, the pre-vious environment could be re-established via a System Restore — refer to thedescription of System Backup & Restore procedures of the SPOTS version to bede-installed; for the new SPOTS version, they are described in the Annex 7.

�� During an APS upgrade from a previous SPOTS V10, some user-defined dataexisting in several configuration files is lost. To avoid reconfiguring them again,before de-installing the existing SPOTS packages, all these files need to be savedfor future merge with the newly installed. The following table lists all these files(relative paths are located under the SPOTS base installation directory), orderedby SPOTS package.

File Purpose/etc/spotsenv This file holds the SPOTS run-time

environment. The ‘old’ user-definedenvironment variables must be reconfigured.

SpotsAScustom/reports/virtual_entities.dat This file carries the Siemens pre-defined

virtual entities. The ‘old’ user-defined publicvirtual entities must be added.

domain.cfg Default is only ‘root’ domain defined. Use‘old’ domains configuration file.

nodes_creation.cfg The ‘old’ user-defined automatic nodescreation entries must be added.

sas.cfg The ‘old’ user-defined properties must beadded.

users.cfg No users are defined by default. Use ‘old’users configuration file.

egw.cfg The ‘old’ user-defined properties must beadded.

mail.cfg The ‘old’ user-defined properties must beadded.

SpotsDSsds.cfg The ‘old’ user-defined properties must be

added.

SpotsNSsns.cfg The ‘old’ user-defined properties must be

added.


20 E200301-01-115-V10.0I-06

�� During an APS upgrade from a previous SPOTS V10 Drop 3 or Drop 4 someReal-Time specific user-defined data are lost. To ease the task of reconfiguringthem again, save the following information before de-installing the existingSPOTS packages:

� Threshold definitions:(Only if an Upgrade with Database reinstallation is performed -- see moreinformation on APS Upgrade variants below). Use the "Export ThresholdValues" functionality of SPOTS to export all existing threshold definitionsonto a CSV file. This file must be saved for future import into the newSPOTS installation, using the "Import Threshold Values" functionality.Consult [7], Section 3.6.5.4, for information on the Threshold Export andImport functionality.

� Real-Time Agency default memory:If the value of the maximum memory available for any RT Agency has beenchanged from the default, write down the changes made in the file <%SPOTS-RTAgency%>\James\profiles\service.properties to reuse afterthe upgrade.Refer to Real-Time Installation Guide [3], Sections “4.4.1-ConfiguringSPOTS RT Agency Software (Solaris� environment)” or “5.2.1-RT Agencyconfiguration files” for details.

� Real-Time Agents default granularity:If the value of the supported granularity for any RT Agent has been changedfrom the default, write down the changes made in the affected files:/opt/spots/rt/Server_rt/Agent/<agent_type>/properties/pdc.properties/opt/spots/rt/Server_rt/Agent/<agent_type>/xml/metadataMapFive.xmlto reuse after the upgrade.Refer to Real-Time Installation Guide [3], Section “4.4.3- Modifying the RTAgents default granularity” for details.

� RT Bar Chart reports default granularity:If the value of the granularity for any RT Bar Chart report has been changedfrom the default, write down the changes made in the affected files:/opt/spots/reports/src/*_BC.scto reuse after the upgrade.Refer to Real-Time Installation Guide [3], Section “4.4.4- Modifying the RTBar Chart reports default granularity” for details.

�� In the same way as for the APS upgrade for the Long Term software, for the Real-Time software there are some user-defined data existing in several configurationfiles that must be saved for future merge with the newly installed. The followingtable lists all these files (relative paths are located under the SPOTS baseinstallation directory) depending if the RT Agencies are located in a Solarisenvironment or in a Windows environment (relative paths are located under theSPOTS Agency base installation directory).


E200301-01-115-V10.0I-06 21

File PurposeRT Agencies in Solaris

<data_type>/cfg/real_time.cfg

where <data_type> can be:asciicyclicexpggsnhlrimspq3dcsctcsprupf

This file is created manually by the user whenthe Agency is installed in Solaris (refer toReal-Time Installation Guide [3] in section“4.4.1.1-Configuring real_time.cfg files”).It holds the information for the directorywhere the agency was installed, the name ofthe agency and the filter for the name of thefiles to be processed, e.g.:

/opt/spots_rt/rta Agency_4 ‘sc3’

RT Agencies in Windows\FileTransfer\cfg\AgentDirectories.cfg It holds information about the name of

the files that are processed by eachAgent/Agency.

\FileTransfer\cfg\FileTransfer.cfg It holds information about theparameters for the FileTransferapplication.

\FileTransfer\cfg\PDCData.cfg It holds information about theidentification of the files generated foreach type of data.

�� Upgrading to a new SPOTS Client version results in loss of possibly existing usercustomised data, like for example applications preferences and/or look & feel.After performing an APS upgrade in the SPOTS Client the default settings arereset.

�� Upgrading to a new SPOTS Client version implies that all Unix/Windows Clientshave to be upgraded to the same drop as the server.

Two variants of the APS upgrade are possible:

� APS upgrade without Database re-installation:This APS Upgrade procedure can be applied whenever the origin SPOTS versionis a SPOTS V10 Drop 3 or SPOTS V10 Drop 4.The fact that the Database is not reinstalled allows a faster upgrade process,minimizing the usage of the HW resources.To execute this procedure, follow the steps in section 3.2.1 below.

�� If the origin version is SPOTS V10 Drop 2, it may be justifiable to performa first upgrade from Drop 2 to Drop 3 in order to allow an "APS upgrade


22 E200301-01-115-V10.0I-06

without Database reinstallation" from Drop 3 to Drop 4. Contact your localSiemens representative for advice.

� APS Upgrade with Database re-installation:This APS Upgrade procedure must be applied whenever the origin SPOTS versionis earlier than SPOTS V10.To execute this procedure, follow the steps in section 3.2.2 below.


E200301-01-115-V10.0I-06 23

3.2.1 APS Upgrade without Database re-installation

1. Stopping SPOTS applications and Data

� Execute the steps in Section 9.1 "Stopping SPOTS Applications".

� Login as oracle user and run the following command:$ . /etc/spotsenv$ $SPOTS_DIR/bin/stopDB

2. Deinstalling SPOTS patches

� Logged as root check which SPOTS patches are installed in the system with thefollowing command:

# pkginfo | grep SPOTS

� For each SPOTS patch listed by the previous command do:# pkgrm <patch-id>

� Find all SPOTS files backed up by SPOTS patches and remove them:# . /etc/spotsenv# find $SPOTS_DIR –name *.before_p* -print# find /etc –name *.before_p* -print# rm <backup file># ###(e.g. rm /opt/spots/bin/loader.before_p100906-5.Z)

3. De-installing the existing SPOTS Software

� Remove the SPOTS V10 Drop 3 or Drop 4 SW packages, without de-installingthe Database. This is achieved by following the SPOTS V10 Drop 3 / Drop 4Installation Guide, executing the steps in Section 9.3 "Removing SPOTSPackages".

�� If it is desired to de-install the Real-Time part, refer to [3], Sections “9-De-installing SPOTS Real-Time Software (Solaris� environment)" and “10-De-installing SPOTS RT Agency (Windows� environment)”.

4. Installing Solaris and Oracle patches

� Install the necessary Solaris� patches (perform the steps in Section 4.4).

� Install the Oracle� patches (perform the steps in Section 6.3).

5. Installing the new SPOTS package(s)

� Perform the steps in Chapter 7 and 8.


24 E200301-01-115-V10.0I-06

�� From Chapter 7, execute only the sections 7.1 to 7.3 and make sure that theSpotsDM package is installed in the same host where SPOTS Database isinstalled.

� Shut down the system as root user, entering the shell command:# /etc/shutdown -y -i6 –g0

6. Installing SPOTS patches

� Execute the steps in Section 9.1 "Stopping SPOTS Applications".

� Check which SPOTS patches are released and obtain them.

� Install SPOTS patches following each patch specific instructions.

�� The installation of SPOTS RT patches will be described ahead in step 13.

7. Rebuilding SPOTS Database catalog

� As user oracle execute (assuming that defaults where used during SPOTSInstallation) the following script:

# /opt/spots/tpl/DB_INSTALL/update_catalog/updatecatalog

8. Restoring SPOTS configuration files

� Merge the files saved in the beginning of this procedure with the new filesinstalled by SPOTS packages.

�� The merge of virtual_entities.dat file should be done later in the procedurewhen SPOTS services are running. The method is described ahead in step11.

�� The restore of SPOTS RT configuration files will be described ahead instep 14.

9. Restoring default password of SPOTS Database user

� Restore the SPOTS Database user password to the installation default: ‘o5mc0’.As user spots run the commands:

$ setdbpwd –u omcadm –cEnter current password: [current password]Enter new password : o5mc0Retype new password : o5mc0$ cp /dev/null $SPOTS_DIR/sdb.cfg

10. Converting the SPOTS V10 Database into SPOTS V10 Drop 4 format

� Login as root user and issue one of the following commands:

(if upgrading from a SPOTS V10 Drop 3 installation)# /opt/spots/tpl/DB_INSTALL/upgrade_V10Drop3/upgradeDB


E200301-01-115-V10.0I-06 25

(if upgrading from a previous SPOTS V10 Drop 4 installation)# /opt/spots/tpl/DB_INSTALL/upgrade_V10Drop4md/upgradeDB

� Execute the procedure to start all SPOTS services (see Section 3.3.10).

11. Merging of Virtual Entities

� Start a SPOTS client and login as spots user.

� Expand the “PM entities” leaf in SPOTS tree view area.

� Open the Virtual Counters browsing window.

� Select the ‘Public’ tab.

� Change the window mode to Edit mode.

� From the Task menu select Import…

� Select the saved virtual_entities.dat file.

�� Uncheck the overwrite definitions check-box!.

� Click the OK button.

12. Installing SPOTS Real-Time software (if applicable)

� If the SPOTS Real-Time functionality is desired, install the respective software asdescribed in the Real-Time Installation Guide ([3]).

13. Installing SPOTS Real-Time patches

� Check which SPOTS Real-Time patches are released and obtain them.

� Install SPOTS Real-Time patches following each patch specific instructions.

14. Restoring SPOTS Real-Time configuration files

� Merge the files saved in the beginning of this procedure for Real-Time with thenew files installed by SPOTS Real-Time package.

15. Setting the Oracle password

� Execute the SPOTS command "setdbpwd" with the "-c" parameter (as describedin [1]), to change the Oracle password for all SPOTS Database connections.



26 E200301-01-115-V10.0I-06

3.2.2 APS Upgrade with Database re-installation

To perform an APS upgrade with Database re-installation, the following steps must beexecuted.

�� Before proceeding, refer to [2] for possible specific recommendations on APSUpgrade.

1. Extracting data from an existing SPOTS system(This step applies only if it is desired to migrate performance data stored on anexisting SPOTS system, in order to use it on the SPOTS system to be installed.)Firstly, consult Section 3.3.1 to get a global overview of the data migrationprocedure.Then, perform the steps in Section 3.3.2 to extract data from the existing SPOTSsystem.

2. De-installing the existing SPOTS SoftwarePerform the steps in Section “De-installing SPOTS Software” in the InstallationGuide of the SPOTS version to be upgraded. When performing this task, it mustbe guaranteed that SPOTS is not being used.

3. Installing patchesInstall the necessary Solaris� patches (perform the steps in Section 4.4) andOracle� patches (perform the steps in Section 6.3).

4. Re-installing the new SPOTS package(s)Perform the steps in Chapter 7 and 8.

5. Regenerating extracted data onto the newly installed SPOTS system(This step applies only if it is desired to migrate performance data stored on anexisting SPOTS system, in order to use it on the newly installed SPOTS system.)Perform the steps in Section 3.3.3 to regenerate the data extracted in Step 1 ontothe newly installed SPOTS system.

6. Installing Real-Time software (if applicable)If the SPOTS Real-Time functionality is desired, install the respective software asdescribed in the Real-Time Installation Guide ([3]).

7. Setting the Oracle passwordExecute the SPOTS command "setdbpwd" with the "-c" parameter (as describedin [1]), to change the Oracle password for all SPOTS Database connections.



E200301-01-115-V10.0I-06 27

3.3 Data Migration

3.3.1 Data Migration overview

The Data Migration procedure allows transferring data from an existing SPOTSinstallation (belonging to the current SPOTS version or to a previous SPOTS version)into a new SPOTS installation, for usage in this latter installation.The following data are transferred (migrated):

• Historical and detailed PM data for all NE versions supported by SPOTS V10Drop 4 (for a complete list refer to Table 1 in [1]), that also exist in the previousSPOTS version.

• Historical SR6.0 and SR7.0 data migrated from Databases of previous SPOTSversions.

�� PM data for the time periods of the unsupported versions are not migrated.

�� User defined Calculated Variables, SOOs and SOCs (previously named as SOVs)are not migrated from (any) previous SPOTS version.However, a file with all previously existing user-defined calculated variables isproduced on the new SPOTS installation, with the following path and name:

$SPOTS_DIR/custom/reports/Old_CalcVars.datThe file syntax is similar to the SPOTS V10 Virtual Counters syntax; however,manual modifications to the measurement name, counter name and top objectclass fields are required before using the file contents in the target V10 system.Contact your local Siemens representative for further details.

Data migration is supported from the following SPOTS versions: V8.1, V9.0, V9.2 andV10.

The data migration procedure involves two sets of actions, which must be executed atspecific points of the overall procedures for "Initial Installation" (Section 3.1) or "APSUpgrade" (Section 3.2). These procedures specify when to perform data migrationactions.The 2 sets of data migration actions are:• Data extraction: Save data from the existing SPOTS installation (described in

Section 3.3.2);• Data regeneration: Once the new SPOTS installation is finished, import the data

onto it (described in Section 3.3.3).

�� For security reasons, a System Backup shall be performed, before executing theregeneration steps; if any unrecoverable error occurs during its execution, the pre-vious environment could be re-established via a System Restore — refer to thedescription of System Backup & Restore procedures of the SPOTS version to bemigrated; for the new SPOTS version, they are described in the Annex 7.

�� When migrating more than 15 days of PM detailed data into a new SPOTSdatabase with partitioning option, it is required to configure the newly installedSDS before its first execution. During SPOTS installation, be alert to the warning


28 E200301-01-115-V10.0I-06

instructing you how to configure the “sds.cfg” file. Any non-conformity may resultin loss of PM detailed data.


E200301-01-115-V10.0I-06 29

3.3.2 Extracting data from an existing SPOTS system

�� If the existing SPOTS system belongs to an earlier release of SPOTS V10, then avariant of the extraction procedure must be applied, using the dbArchive SPOTScommand. Refer to Section 3.3.2.1 below.

� Stop the existing SPOTS system, including all scheduled jobs and daemons —refer to the Section “Stopping SPOTS” in the Installation Guide of the SPOTSversion to be upgraded.

� Install SpotsDM package on the existing SPOTS system, on the same host as theSPOTS database — refer to section 3.3.5.

� Dump regenerated data into tape(s) — refer to section 3.3.6.

� Remove SpotsDM package from the system — refer to section 3.3.8.

3.3.2.1 Extraction using dbArchive

� Export the data to file using the dbArchive feature. For example:# $SPOTS_DIR/bin/dbArchive –x –a <archive_dir_name>

�� The disk partition chosen for the archive output file must have enough space tohold the archive contents. In case of space shortage, it is possible to partition thearchive in several files, using the possibilities offered by dbArchive to selectivelyarchive data.

Consult [1], Section "dbArchive" for a precise description of the dbArchive command.


30 E200301-01-115-V10.0I-06

3.3.3 Regenerating extracted data on the newly installed SPOTS system

�� If the extraction step made use of the dbArchive SPOTS command (Section3.3.2.1), then a corresponding variant of the regeneration procedure must beapplied, using also the dbArchive SPOTS command. Refer to Section 3.3.3.1below.

� Stop the newly installed SPOTS system, including all scheduled jobs and daemons— refer to section 3.3.4.

� Install SpotsDM package on the newly installed SPOTS system, on the same hostas the SPOTS database — refer to section 3.3.5.

� Recover and adapt regenerated data from tape(s) — refer to section 3.3.7.

� Remove SpotsDM package from the system — refer to section 3.3.8.

� Update relevant configuration files — refer to section 3.3.9.

� Start SPOTS services and daemons— refer to section 3.3.10.

� Data Migration completed.

3.3.3.1 Regeneration using dbArchive

� For (each of) the saved archive(s) import the data by typing at the commandprompt:

# $SPOTS_DIR/bin/dbArchive –i –a <archive_dir_name>

Consult [1], Section "dbArchive" for a precise description of the dbArchive command.


E200301-01-115-V10.0I-06 31

3.3.4 Stopping SPOTS

Execute the following steps to stop the SPOTS services and the associated jobs:

� Ensure that all SPOTS users have exited from all SPOTS applications includingall SPOTS Client sessions.

The following procedure can be used to stop all applicable services with a singlecommand (see below for a method that uses a specific command for each service):

� Login as root user.

� Issue the following command:# /etc/init.d/initSpotsAll stop

� This command attempts to stop all the above indicated services.It might happen that some of the services/processes do not stop; in such acase, proceed as follows:

� Wait a few seconds and then verify if the PMS processes are stopped, execu-ting the following command:$ ps –ef | grep s[nad]s

� Verify also if RC FTP server is stopped, executing the following command:# ps –ef | grep oltrcftpserver.luc

� If the processes are already stopped, no action is required; otherwise forcethem to stop, with:$ /etc/init.d/initSpotsAll stop -force

The following procedure can be used to stop all the applicable services with a specificcommand per service:

� Login as spots user

� Stop the dc_transfer daemon (applicable only on hosts with SAS installed and ifsupport for OMC-S interworking is activated):$ /etc/init.d/initdctransf stop

� The following step must be performed by root user. To do so, issue the command“su –“ and supply the appropriate password.

� Stop the RC FTP server daemon (applicable only on hosts with SAS installed andif support for interworking with RC is activated):# /etc/init.d/initrcftp stop

� The previous command attempts to stop RC FTP server gracefully.It might happen that the daemon does not stop; in such a case, proceed asfollows:


32 E200301-01-115-V10.0I-06

� Wait a few seconds and then verify if RC FTP server is stopped, executingthe following command:# ps –ef | grep oltrcftpserver.luc

� If it is already stopped (no output or simply a line referent to the grepcommand itself), no action is required; otherwise, force it to stop with:# /etc/init.d/initrcftp stop -force

� Exit from root user role by means of the “exit” command.

� Stop all PMS services:$ /etc/init.d/initSpotsPMS stop

� This command attempts to stop all the PMS servers (SNS, SAS and SDS)that are installed in this host.It might happen that some of the services/processes do not stop; in such acase, proceed as follows:

� Wait a few seconds and then verify if the PMS processes are stopped, execu-ting the following command:$ ps –ef | grep s[nad]s

� If the processes are already stopped, no action is required; otherwise forcethem to stop, with:$ /etc/init.d/initSpotsPMS stop -force

� Stop the License Manager daemon (applicable only on hosts with SAS installed),typing the following command:

$ /etc/init.d/initlmd stop


E200301-01-115-V10.0I-06 33

3.3.5 Installing SPOTS Data Migration package

Install the Data Migration package, from the SPOTS distribution media, in the SPOTSsystem:

Installing SpotsDM package can be accomplished in two ways:

Using admintool

� Follow the procedure referenced in Section 7.1, make sure to:

� Select only the SPOTS Upgrade option comprising SPOTS DataMigration package for installation.

� Do not execute the post-install procedures described in Section 7.4.

� Package SpotsDM installed using admintool command.

Using package commands

� Follow the procedure referenced in Section 7.2, make sure to:

� Select only the SpotsDM package for installation.� Do not execute the post-install procedures described in Section 7.4.

� Package SpotsDM installed using package commands.


34 E200301-01-115-V10.0I-06

3.3.6 Dump existing data into tape(s)

Execute the following steps, to copy the information to be migrated into tape(s):


� Insert a new tape in the device (verify that the tape being used is write enabled).

� Execute the command migrateDB:# /opt/migration/migrateDB <tape_device_name>

� Check in your system for the current <tape_device_name>(e.g. “/dev/rmt/0n”).

� The option “-h” provides help on the usage of this command:# /opt/migration/migrateDB –h

� Enter the Oracle� database SID when required.

� If required, enter the Oracle� Home directory.

� Choose the Save migration option, entering “1”.

� While data is being extracted into tape, information will be logged in the file“/opt/migration/log/migrateDB_SPOTS.log”.

� Insert another new tape in the device when required, for proceeding with theSave migration type procedure.

� After completion, remove the tape from the device.

� For security reasons, put the tape(s) in write-protected mode.

� Regenerated data extracted.


E200301-01-115-V10.0I-06 35

3.3.7 Recovering regenerated data from tape(s)

In the newly installed SPOTS V10 Drop 4 system, execute the following steps, to loadand adapt the information on tape(s):


� Insert the first recorded tape in the device.

� Verify that SPOTS_DIR environment variable is correctly set. It must point to thebase directory where SPOTS is installed. For further information refer to Annex 2.

� Execute the command migrateDB:# $SPOTS_DIR/migration/migrateDB <tape_device_name>

� Check in your system for the current <tape_device_name>(e.g. “/dev/rmt/0n”).

� The option “-h” provides help on the usage of this command:# $SPOTS_DIR/migration/migrateDB –h

� Enter the Oracle� database SID when required.

� If required, enter the Oracle� Home directory.

� Choose the Restore migration option, entering “2” to regenerate Detail andHistorical data, or enter “3” to regenerate only Historical data.

� The next step is applied only if data from Mobile-Core NEs have to bemigrated.

� Modify the SPOTS names for the Mobile-Core NEs.

� NEs names, which previously included the NMS name, no longer useit. Consequently, the NMS name must be removed from all the NEnames in order to be able to import traffic data correctly.

� The list of the Mobile-Core NEs (extracted from the “old” SPOTSDatabase) is displayed in a window, using the Text Editor that is set inthe environment variable EDITOR.

� Only NEs with versions SR6.0 or later are displayed in thewindow. All the others are discarded, i.e. data is not regenerated.If there are no NEs that fulfil the mentioned criteria the windowis not displayed.

In the displayed Text Editor window, a line per NE with the followingsyntax is presented:<old_NE_name> <new_NE_name>

where:<old_NE_name>


36 E200301-01-115-V10.0I-06

is the NE name used in the “old” SPOTS version: the NMSname concatenated, via the character “@”, with the NE nameas configured in the NMS (its symbolic name).

<new_NE_name>is the NE name as configured in the NMS (its symbolic name)— this field is initially set with the value of<old_NE_name>.

Example of the default contents, displayed in the Text Editor window:omc1@lisbon1 omc1@lisbon1omc1@lisbon2 omc1@lisbon2

� For all Mobile-Core NEs, edit the field <new_NE_name>, replacing itby the “new” NE name.

� All NE names must be unique network wide.

Example of the file contents after modification:omc1@lisbon1 lisbonAomc1@lisbon2 lisbonB

� Enter ‘return’ in the last line of the file. Otherwise, that line willnot be considered and an error shall be returned indicating thatline is missing.

� Save the updated file contents.

� The next step is applied only if data from GERAN NEs have to be migrated.

� Modify the SPOTS names for BSCs.

� BSCs names, which previously included the OMC-B name, no longeruse it. Consequently, the OMC-B name must be removed from all theBSC names in order to be able to import traffic data correctly.

� The list of the BSCs (extracted from the “old” SPOTS Database) isdisplayed in a window, using the Text Editor set in the environmentvariable EDITOR.

� Only BSCs with versions BR5.0 or later are displayed in thewindow. All the others are discarded, i.e. data is not regenerated.If there are no BSCs that fulfil the mentioned criteria thewindow is not displayed.

In the displayed Text Editor window, a line with the following syntaxis presented per BSC:<current_BSC_name> <new_BSC_ name>

where:


E200301-01-115-V10.0I-06 37

<current_BSC_name>is the BSC name used in the “old” SPOTS version: the OMC-B name concatenated, via the character “_”, with the BSCname as configured in the BSC database.

<new_BSC_name>is the BSC Symbolic Name as configured in the RC, forBR6.0 BSCs or is the BSC name stripped of its OMC-B namepart, for BR5.0/5.5 BSCs — this field is initially set with<current_BSC_name>.

Example of the default contents, displayed in the Text Editor window:omcb01_BLC01D omcb01_BLC01Domcb01_BLC02D omcb01_BLC02D

� For all BSCs, edit the field <new_BSC _name>, replacing it by the“new” BSC name.

� Symbolic names should be given only to the BSCs that are beingupgraded to BR6.0; the names of BSCs that remain in BR5.0/5.5after the installation of SPOTS V10 Drop 4 should not change.If, later, they are upgraded to BR6.0, a specific procedure mustbe used to change their names at that time — this procedure isdescribed in [1], Section "changeObjNames".

� All NE names must be unique network wide.

Example of the file contents after modification:omcb01_BLC01D Lisbon_1omcb01_BLC02D Lisbon_2

� Enter ‘return’ in the last line of the file. Otherwise, that line willnot be considered and an error shall be returned indicating thatline is missing.



� If required, modify the SPOTS names for BTSMs, giving the correspondingsymbolic names.

� The list of the BTSMs (extracted from the “old” SPOTS Database) isdisplayed in a window, using the Text Editor set in the environmentvariable EDITOR.

� Only BTSMs belonging to BSCs with versions BR5.0 or laterare displayed in the window. All the others are discarded. Ifthere are no BTSMs that fulfil the mentioned criteria thewindow is not displayed.


38 E200301-01-115-V10.0I-06

In the displayed Text Editor window, a line with the following syntaxis presented per BTSM:<current_BSC_name> <current_BTSM_name> <BTSM_symb_name>

where:<current_BSC_name>

is the BTSM corresponding BSC name used in the “old”SPOTS version.

<current_BTSM_name>is the BTSM name used in the “old” SPOTS version.

<BTSM_symb_name>is the BTSM Symbolic Name as configured in the RC — thisfield is initially set with <current_BTSM_name>.

Example of the default contents, displayed in the Text Editor window:omcb01_BLC01D 20 20omcb01_BLC02D 21 21

� For each BTSM whose name has to be changed, edit the field<BTSM_symb_name> field, replacing it by the corresponding symbolicname.

� BTSMs belonging to BSCs that remain in BR5.0/5.5 will keeptheir names unchanged after the installation of SPOTS V10Drop 4. If, later, they are upgraded to BR6.0, a specificprocedure must be used to change their names at that time —this procedure is described in [1], Section "changeObjNames".

Example of the file contents after modification:omcb01_BLC01D 20 Lapaomcb01_BLC02D 21 Benfica



� If BTS identifiers (CGIs) are to be mapped to BTS symbolic names, it isnecessary to prepare a file containing information to perform this mapping.

The file shall be named symbFDN.bts.dat and shall contain one line per BTSto be mapped, according to the following format:

<BTSSymbolicName>{tab}<LAC>{tab}<CI>

� BTSs belonging to BSCs that remain in BR5.0/5.5 will keep theirnames unchanged after the installation of SPOTS V10 Drop 4. If,later, they are upgraded to BR6.0, a specific procedure must be used tochange their names at that time — this procedure is described in [1],Section "changeObjNames".

If the OTS (O&M Toolset) product is installed and the OTS Core Databaseis populated with symbolic naming information for the BTS objects to be


E200301-01-115-V10.0I-06 39

mapped, the above file can be created automatically by the getsymbnameSPOTS application. To achieve this, perform the following sub-steps:


� If a file $SPOTS_DIR/data/gsnl.dat already exists, rename it:$ mv $SPOTS_DIR/data/gsnl.dat $SPOTS_DIR/data/gsnl.bak

� Create a new $SPOTS_DIR/data/gsnl.dat file with the followingcontents:OTS

<Core_DB_user> <Core_DB_pwd>

where:<Core_DB_user>

is the user name for the OTS Core DB service that providesexternal access to the OTS Core DB.

<Core_DB_pwd>is the password for the above-mentioned user.

� Login as root user

� Edit the file tnsnames.ora stored in the subdirectorynetwork/spots_ora_admin of the ORACLE_HOME directory, andappend the following to the contents of the file:rm.cm =

(DESCRIPTION =(ADDRESS_LIST =

(ADDRESS =(PROTOCOL = TCP)(Host = <Core_DB_IP_addr>)(Port = <Core_DB_port_no>)

))(CONNECT_DATA = (SID = <Core_DB_Oracle_SID>))

)

where:<Core_DB_IP_addr>

is the IP address of the host where OTS Core Database is installed.<Core_DB_port_no>

is the port number for the Oracle� Service provided by OTS CoreDB.

<Core_DB_Oracle_SID>

is the “service id” of the Oracle� Service above.


� Execute getsymbname, to retrieve information from the OTS CoreDatabase:


40 E200301-01-115-V10.0I-06

$ cd $SPOTS_DIR/bin$ ./getsymbname

This step shall create a file names symbFDN.bts.dat in directory$SPOTS_DIR/data/BSS.

� If a BTS had several CGIs during its lifetime, the OTS CoreDatabase only provides the symbolic name of the most recentCGI. The file can be edited manually after its creation, in orderto add further CGI / symbolic name mappings. Note that it ispossible to specify only one symbolic name per LAC/CI pair.

� Delete (or move to an ".OTS" extension) the file gsnl.dat that wascreated in one of the above steps (the one with first line "OTS"):$ mv $SPOTS_DIR/data/gsnl.dat $SPOTS_DIR/data/gsnl.OTS

� If, before creating the above file, another gsnl.dat file already existed(in which case it has been renamed gsnl.bak), restore its initial name:

$ mv $SPOTS_DIR/data/gsnl.bak $SPOTS_DIR/data/gsnl.dat

� Enter “y” for mapping BTS identifiers (CGIs) to BTS symbolic names.Otherwise, skip this step entering “n”.

� If “y” was specified, enter the path where the previously prepared filesymbFDN.bts.dat is located.

� If a CGI cannot be mapped to a symbolic name by the migrationprocedure (due to “n” being chosen or due to a processing error), thestring "LAC_XXX_CI_YYY" is saved in SPOTS as the BTSsymbolic name ("XXX" and "YYY" are the LAC and CI values,respectively).

� While data is being extracted from tape(s), information will be logged in thefile “$SPOTS_DIR/migration/log/migrateDB_SPOTS.log”.

� Spots migration Restore option will first regenerate basic configuration data.PM data files should not be imported before this regeneration task iscompleted. To start importing PM data files , wait until the followingmessage is displayed:”Basic Configuration Spots data successfully regenerated!Proceeding with Detailed and Historical data regeneration…”

� When finished, remove the tape from the device.

� Regenerated data restored.


E200301-01-115-V10.0I-06 41

3.3.8 Removing the SPOTS Data Migration package

Carry out the following steps to remove the SpotsDM package:


� Execute the following command:# /usr/sbin/pkgrm SpotsDM

� Confirm all polls with “y”.

� Inspect the output in order to verify that package removal is successful.

� Removal of SpotsDM package completed.

3.3.9 Post Migration configuration files update

� Edit file “$SPOTS_DIR/data/tnsnames.cfg.save” extracted during data regenera-tion from tape and copy the relevant configuration data into the configuration file“$SPOTS_DIR/data/element_managers.cfg”, according to Section 7.5.1.

� Edit file “$SPOTS_DIR/custom/reports/Old_CalcVars.dat” where user Calcvarsdefined in old SPOTS versions are saved as SPOTS V10 Virtual Counters format.Correct saved old calcvars according the new SPOTS V10 Drop 4 measurementsspecification and append it to the SPOTS V10“$SPOTS_DIR/custom/reports/virtual_entities.dat” file.

� File updated.


42 E200301-01-115-V10.0I-06

3.3.10 Starting SPOTS

Execute the following steps to start the SPOTS services and the associated jobs:

� The “start” argument is optional in the commands below i.e. can be omittedwith the same results on behalf of simplicity.

The following procedure can be used to start all applicable services with a singlecommand (see below for a method that uses a specific command for each service):


� Give the following command:# /etc/init.d/initSpotsAll start

The following procedure can be used to start all the applicable services with a specificcommand per service:

� Login as spots user.

� Start the License Manager daemon (applicable only on hosts with SAS installed),typing the following command:# /etc/init.d/initlmd start

� Start all PMS services (SNS, SAS and SDS):# /etc/init.d/initSpotsPMS start

� Start the dc_transfer daemon (applicable only on hosts with SAS installed and ifsupport for OMC-S interworking is activated):# /etc/init.d/initdctransf start

� The following step must be performed by root user. To do so, issue the command“su –“ and supply the appropriate password.

� Start the RC FTP server daemon (applicable only on hosts with SAS installed andif support for interworking with RC is activated):# /etc/init.d/initrcftp start


E200301-01-115-V10.0I-06 43

4 Installing the Operating System

This chapter describes how to install the Solaris� 8 Operating System, which isrequired by all SPOTS PMS components and by the SPOTS Client for Solaris�.SPOTS Client for Windows� NT/2000/XP is also available, however the description ofhow to install Microsoft Windows� NT/2000/XP Operating System shall not beincluded.

� The description on how to install Solaris� 8 Operating System is CD oriented.The installation steps sequence is different if you decide to install Solaris� 8 fromDVD.

4.1 Getting Started

In order to start the installation procedure for Solaris� 8 Operating System, verify thatthe necessary information is gathered, refer to Section 2.2. Then, execute the actionsbelow:

� IMPORTANT NOTE: If you will install Fault Tolerance with diskmirroring do not forget to fill the necessary information, refer to the“Information to fill before OS installation” on Annex 5.

� Switch on your system and verify that all external devices are properly connected.While the Operating System is booting, enter the system monitor prompt, pressingthe keys:“Stop” + “A”

� If you will install Fault Tolerance with disk mirroring or the last systeminstallation included it then execute the following two steps at the ok prompt

� Take note of the booting device, on old boot-device field of Previous OSInstallation Boot Device table at Annex 5, issuing the following command:ok printenv boot-device

� This value can be used to recover from OS installation before any diskchange.

� Change the booting device issuing the following commandok setenv boot-device disk

� Insert the Solaris� 8 2/02 Installation CD and enter the following command:ok boot cdrom

� Select English as the Solaris� Installer language:“1”

� Select the Locale (if applicable), for example:“37”


44 E200301-01-115-V10.0I-06

� Choose the location to place the Solaris� installation software:

� Swap slices are usually erased at each reboot, so it is preferable to place theSolaris� installation software on a disk slice labelled swap.

� If a swap slice exists execute the following steps:

� Reject all swap slices detected by the installation until no more swap slicesexist answering:“n”

� Do not select any slice from swap slices list available in external disksanswering:“none”

� Do not select any slice from general slices list available in external disksanswering:“none”

� Do not go back to re-select a slice answering:“no”

� Do not format the default disk (the default disk will be selected in the next step)answering:“no”

� Disk Selection:

� If your system is a Sun Blade and you will install Fault Management withDisk Mirroring then you must chose one of the machine internal disks. Todo this, from the complete list of disks you can see 2 disks belonging to oneof the disk controllers (the internal disks) and 6 disks belonging to the otherdisk controller (the external disks). It is possible to know to which controllera disk belongs by the number after the letter “c” in the disk id (ex: diskc2t1d0 belongs to controller 2).

� Select the disk to create the swap slice from the complete list of disks.

� Continue if the selected disk contains Solaris� answering:“yes”

� Enter the swap slice size, following the SPOTS recommendations – Section 2.3.

� The swap size cannot be changed afterwards, during file system layout.

� Confirm the swap slice starting at the beginning of the disk answering:“y”

� Verify the information summary. If it is correct, confirm it entering “y”.


E200301-01-115-V10.0I-06 45

� Please wait…After copying Solaris� installation software, the system will automatically rebootand installation will continue with system configuration.

� Getting started section completed.


46 E200301-01-115-V10.0I-06

4.2 Configuring the System

In this section, the installer provides all the information that is required for systemconfiguration.

� After the Welcome screen is displayed, navigate through the Solaris� Installerwindow sequence by means of the Next > and < Back buttons.

� If a XVR-500 graphics accelerator is installed in your system and you are trying toinstall Solaris 8, it is not possible to launch the graphical user interface for theinstallation. That’s why you have to configure (current section) and install(Section 4.3) Solaris via a text based user interface. The dialogs in this text basedinstallation procedure are the same as in the GUI installation. Just follow theinstructions on the screen and enter the required information as described in thecurrent section (for configuration).

� Set Network Connectivity to:“Networked”

� Select Network Interface (if applicable), for example:“eri0”

� Use Dynamic Host Configuration Protocol (DHCP):“No”

� Choose the Host Name that will identify this system on the network, for example:“pms01”

� Enter the Internet Protocol (IP) Address for this system, for example:“129.200.9.1”

� Specify the Netmask of your subnet, or accept the default value, for example:“255.255.255.0”

� Do not accept the default Netmask unless you are sure it is correct for yoursubnet.

� Enable IPv6:“Yes”

� Specify a default IP router (gateway) or let the Solaris� installation program findit:“Specify One/Find One”

� Solaris� installation program default is to find one. If a default router is tobe specified, provide the following information: “Router IP address”

� Enable Kerberos security on this system:“No”

� Select the Name Service that will be used by this system:


E200301-01-115-V10.0I-06 47

“None”

� Specify Time Zone by:“Geographic Region”

� Select the adjusted Geographic Region and Time Zone.

� Enter the correct Date and Time.

� Type the alphanumeric string to be used as Root Password and confirm it.

� Disable Power Management™ (applicable only once for each system):“Turn Power Management Off”“Don’t ask; leave Power Management as set above”

� The previous settings cause this selection to be made only once; thus afterthe installation this question won’t be polled again, after every systemreboot.

� Select the desired Proxy Server Configuration:“Direct Connection to the Internet / Use Proxy ConfigurationBelow”

� The default is a direct connection to the Internet. To specify a proxy server,provide the following information: “Host” and “Port”.

� Verify the information presented in the selection summary. If information iscorrect, confirm it; otherwise, navigate through the Solaris� Installer series ofwindows and correct the information.

� Please wait…The system is being configured with the chosen settings. After this, proceed withthe next section.

� System configuration completed.


48 E200301-01-115-V10.0I-06

4.3 Installing Solaris��

Most of the Solaris� 8 installation is described in this section, including the actions toinstall the Solaris� Software and the Solaris� Documentation.

� The Solaris� Web Start Installation Kiosk is displayed along with the Welcome toSolaris� dialogue box. From this point on, you can click on any link listed in theKiosk menu. Navigate through the sequence of dialogue boxes by means of theNext > and < Back buttons.

� If a XVR-500 graphics accelerator is installed in your system and you are trying toinstall Solaris 8, it is not possible to launch the graphical user interface for theinstallation. That’s why you have to configure (Section 4.2) and install (currentsection) Solaris via a text based user interface. The dialogs in this text basedinstallation procedure are the same as in the GUI installation. Just follow theinstructions on the screen and enter the required information as described in thecurrent section (for installation).

� Enable Automatic reboot and CD ejection after software installation:“Yes”“Yes”

� Specify the installation Media for Solaris� 8 2/02 Software 1 of 2:“CD/DVD”

� The Solaris� 8 2/02 Installation CD is ejected.

� Insert the Solaris� 8 2/02 Software 1 of 2 CD

� Initialising, please wait…

� Select Initial Installation (only applicable, if the Solaris� installation programdetects that the system is upgradeable):“Initial Install”

� Select Type of Install:“Custom Install”

� No additional Software selections are required by SPOTS software, besides thedefault.

� Select the initial System Locale to be used after system installation:“English (POSIX C)(C)”

� De-select all products other than (select only):“Solaris� 8 Documentation European”

� The installation of the Solaris� 8 Documentation is not mandatory so if itisn’t considered necessary de-select all products.

� Install additional third-party or other software products:


E200301-01-115-V10.0I-06 49

“None”

� Applicable on UltraSparc-II platforms only. Select 64-Bit Support (software willbe installed with 64-bit and 32-bit support):“Yes”

� Define the Solaris� software group:“Entire Group”“Default Packages”

� Select all available disks to lay out the file systems on.

� Preserve existing data (only if any of the selected disks has file systems orunnamed slices that you can choose to preserve):“No”

� Define the layout of all existing disks, following the SPOTS recommendations –see Section 2.3. Specify all the corresponding file systems and define their size (inMB).

� Take into consideration the intended SPOTS configuration that will beinstalled in the system. Different SPOTS configurations imply differenthard-disk requirements and different file systems organization.

� If Fault tolerance with disk mirroring will be installed then it is necessary tofill the “Information to fill during OS installation” on Annex 5.

� Verify the information presented in the installation summary. If informationis correct, proceed to installation; otherwise, navigate through the Solaris�Installer series of dialogue boxes and correct the information.

� Installing…Status messages and the name of each added Solaris� Software package aredisplayed in brackets above the top progress bar. The status of the entireinstallation is shown on the bottom progress bar.

� The actual installation time depends on the software you chose to install, thereallocation of any space if needed and the drive performance.

� The Installation Summary dialogue box is presented. For further details aboutimportant events occurred during installation use the Details… button.

� Specify the installation Media for Solaris� 8 2/02 Software 2 of 2:“CD/DVD”

� The Solaris� 8 2/02 Software 1 of 2 CD is ejected.

� Insert the Solaris� 8 2/02 Software 2 of 2 CD and proceed with installation whenready.

� Installing, please wait…


50 E200301-01-115-V10.0I-06


� Specify the installation Media for Solaris� 8 Documentation:“CD/DVD”

� The Solaris� 8 2/02 Software 2 of 2 CD is ejected.

� Installation of the Solaris� 8 Software completed. If previously selected, proceedwith Solaris� 8 Documentation installation otherwise continue after Solaris� 8Documentation installation completion.


E200301-01-115-V10.0I-06 51

� Insert the Solaris� 8 2/02 Documentation CD and start the installation when ready.

� Installing, please wait …


� The Solaris� 8 2/02 Documentation CD is ejected.

� Installation of the Solaris� 8 Documentation completed.

� System reboot is automatically initiated.


� If a XVR-500 graphics accelerator is installed in your system, after the reboot ofthe system you have the console login only, and therefore the next step cannot beperformed at this stage.

� Choose the default desktop:“Common Desktop Environment (CDE)”

� Applicable only to UltraSparc-II platforms, set kernel to 64-bit:

� Execute the following shell commands:# /usr/sbin/eeprom boot-file=”kernel/sparcv9/unix”# /usr/sbin/eeprom diag-file=”kernel/sparcv9/unix”# /etc/shutdown –y –g0 –i6

� If you will install Fault Tolerance with disk mirroring, then fill the “information tofill after OS installation” on Annex 5.

� Installation of the Solaris� 8 completed.


52 E200301-01-115-V10.0I-06

4.4 Installing Solaris�� Patches

The SPOTS SW is distributed along with a Solaris� 8 Recommended Patch Cluster,which must be installed after the Solaris� 8 installation.

SPOTS SW is certified to be used only with the version of the Solaris� 8Recommended Patch Cluster distributed with the SPOTS CD.


� Insert the Patches CD, distributed with SPOTS, on the appropriate device.

� Execute the following shell commands:# cd /cdrom/cdrom0/solaris# ./install_cluster

� Continue with the installation, pressing “y”.

�� A particular patch (provided in this cluster) might not be installed. This does notnecessarily means that an error occurred, refer to the installation log file and checkif you’re under one of the following harmless circumstances:

• The patch applies to a package that has not originally been installed.• The same or newer revision of the patch has already been installed.• The patch was obsolete by another patch that has already been installed.

� Remove the Patches CD from the device, executing:# cd /# eject cdrom

� Restart the system, entering the shell command:# /etc/shutdown -y -i6 –g0

�� Besides the Solaris� 8 Recommended Patch Cluster distributed with SPOTS someadditional software patches, specific to your hardware platform, may be required.For further information, please refer to the Product Notes that accompany yoursystem.

� Installation of the Solaris� 8 patches completed.

� If a XVR-500 graphics accelerator is installed in your system, install the driver forthe XVR-500 graphics accelerator, by executing the steps below.

1. Login as user “root”.2. Insert CD-Rom “Sun XVR-500 Graphics Accelerator”3. Enter the following commands to start the installation of the software:

# cd /cdrom/cdrom0# ./install

4. If prompted for the installation of Sun OpenGL choose the option


E200301-01-115-V10.0I-06 53

“Do not install Sun OpenGL”5. In the next dialog press any key to start the installation.6. Reboot the system with the command:

# shutdown -y –i6 –g0� The next time you perform a login, choose the default desktop:

“Common Desktop Environment (CDE)”

� IMPORTANT NOTE: If you will install Fault Tolerance with disk mirroring,then it must be done before any other change to the system (user add orsoftware installation or configuration).


54 E200301-01-115-V10.0I-06

5 Fault Tolerance with Disk Mirroring

To improve SPOTS availability Fault Tolerance with Disk Mirroring can be used. Thischapter describes how to install, maintain and uninstall Fault Tolerance with DiskMirroring.

If disk mirroring will not be installed, proceed with Oracle� Software Installation onChapter 6.

Fault Tolerance with Disk Mirroring consists on having the contents of one diskreplicated on other disk. Disk mirroring improves data availability. If one of themirrored disks fails, the information can be accessed on the other disk. SolsticeDiskSuite� Software3 is used to manage the mirroring.

Setup TasksTo improve SPOTS availability Fault Tolerance with Disk Mirroring it is necessary toexecute the two following setup tasks.

• The first task is to install DiskSuite� software as described in Section 5.1.1

• The second task is the mirroring configuration as described in Section 5.1.2.

Maintenance TasksAfter the setup tasks have been executed, the mirroring status is checked periodically bythe system. If any mirroring failure is detected, the root user will receive a failurenotification via email. Alternatively, the mirroring status can also be checked on userrequest. After failure detection it is necessary to replace the damaged disks.

The maintenance tasks are:

• The mirror state monitoring as described in Section 5.2.1

• The replacement of damaged disks as described in Section 5.2.2

• The system boot with insufficient database replicas as described in Section 5.2.3

Un-installation TasksWhen Fault Tolerance with Disk Mirroring is no longer needed, it can be removedexecuting the two following un-installation tasks.

• The first task is to remove the mirroring configuration as described in Section5.3.1

• The second task is to uninstall DiskSuite� Software as described in Section5.3.2

3 For more information about Solstice DiskSuite Software refer to http://docs.sun.com


E200301-01-115-V10.0I-06 55

5.1 Setup Tasks

To configure the system for Fault Tolerance with Disk Mirroring it is needed to executethe following tasks:

1st: DiskSuite� Software Installation as described in Section 5.1.1

2nd: Disk Mirroring Configuration as described in Section 5.1.2

5.1.1 Installing Solstice DiskSuite�� Software

This Section describes how to install the Solstice DiskSuite� 4.2.1 packages required tothe mirroring configuration.

The Solstice DiskSuite� 4.2.1 required packages are distributed along with the SPOTSSW distribution media.

� IMPORTANT NOTE: Before installing DiskSuite� Software, all requiredpatches, on Section 4.4, must be installed and the disk partition informationmust be stored in Annex 5.


� Insert the SPOTS Server and Solaris Client distribution media on the appropriatedevice

� Execute the following shell commands:# cd /cdrom/cdrom0/diskman/disksuite# pkgadd -d . SUNWmdx SUNWmdr SUNWmdu SUNWmdg

� The packages installation order is mandatory.


� Verify correct package installation executing the following command# pkginfo -l SUNWmdr SUNWmdu SUNWmdg SUNWmdx

� Restart the system, entering the shell command:# reboot

� Installation of the Solstice DiskSuite� successfully completed

Proceed to Section 5.1.2 to configure the disk mirroring

5.1.2 Configuring Disk Mirroring

This section describes how to configure the disk mirroring.

There are 2 pre-defined mirroring configurations:


56 E200301-01-115-V10.0I-06

1. System disk mirroring for Sun Blade systems with 2 internal disks and 6 externaldisks. The mirroring configuration for this hardware configuration is describedin Section 5.1.2.1.

2. System and Database disks mirroring for Sun Fire systems with 12 internaldisks. The mirroring configuration for this hardware configuration is describedin Section 5.1.2.2.

5.1.2.1 Configuring System Disk Mirroring

This Section describes how to configure the System disk mirroring for Sun Bladesystems with 2 internal disks and 6 external disks.


� This login must be done in the workstation and must be a root login (do notbecome super user with the su command).

� Verify if any remote user is using the system issuing the command:# who

If any user is reported other than root user, logout the user and execute this stepagain to verify than no other user, except root, is using the file system.

� Detect and stop processes, with procedure in Section 5.2.8, that are using thefollowing file systems:

/replica1/replica2/replica3/replica4/var/opt/var_opt_mirror/export/home/home_mirror/opt_mirror/swap_mirror/root_mirror


� Execute the following shell commands:# cd /cdrom/cdrom0/diskman/OSandBRmirror# ./runstep 1# reboot

� Wait for the system to reboot.


� Execute the following shell commands:# cd /cdrom/cdrom0/diskman/OSandBRmirror


E200301-01-115-V10.0I-06 57

# ./runstep 2

� The alternate boot is present in the output of last step. Note it down, filling thecorresponding item of section “Information to fill after disk configuration withDiskSuite�”, in Annex 5. Make sure that all information required in this sectionis completely filled in.

� Verify the configuration as described in Sections 5.2.1.3 and 5.2.1.4.

� Remove the SPOTS Server and Solaris Client distribution media executing thefollowing commands:# cd/eject cdrom

� Disk configuration successfully completed

Proceed with Oracle� Software Installation on Chapter 6

5.1.2.2 Configuring Full Disk Mirroring

This Section describes how to configure the System and Database disks mirroring forSun Fire systems with 12 internal disks.



� Verify if any remote user is using the system issuing the command:# who

If any user is reported other than root user, logout the user and execute this stepagain to verify than no other user, except root, is using the file system.

� Detect and stop processes, with procedure in Section 5.2.8, that are using thefollowing filesystems:

/replica1/replica2/replica3/replica4/replica5/replica6/replica7/replica8/replica9/replica10/replica11/replica12/spots_db1/spots_db1_mirror/spots_db2


58 E200301-01-115-V10.0I-06

/spots_db2_mirror/spots_db3/spots_db3_mirror/spots_db4/spots_db4_mirror/spots_db5/spots_db5_mirror/spots_db6/spots_db6_mirror/var/opt/var_opt_mirror/spots_arch/spots_arch_mirror/export/home/home_mirror/opt_mirror/swap_mirror/root_mirror


� Execute the following shell commands:# cd /cdrom/cdrom0/diskman/OSandBRandDBmirror# ./runstep 1# reboot



� Execute the following shell commands:# cd /cdrom/cdrom0/diskman/OSandBRandDBmirror# ./runstep 2

� The alternate boot is present in the output of last step. Take note of it in Annex 5.

� Refer to Annex 5 and fill the items on “Information to fill after disk configurationwith DiskSuite�”.

� Verify the configuration as described in Sections 5.2.1.3 and 5.2.1.4.

� Remove the SPOTS Server and Solaris Client distribution media executing thefollowing commands:# cd /eject cdrom

� Disk configuration successfully completed

Proceed with Oracle� Software Installation on Chapter 6


E200301-01-115-V10.0I-06 59

5.2 Maintenance Procedures

The maintenance procedures are the following:

• The mirror state monitoring, described in Section 5.2.1

This procedure is to be executed after the reception, by root user, of a FailureNotification via Email, or when it is desired to check the mirroring configurationstatus.

• The replacement of damaged disks, described in Section 5.2.2

This procedure is to be executed after the detection of a mirroring disk failure

• The system boot with insufficient database replicas, described in Section 5.2.3

This procedure is to be executed when the system is unable to boot due to“insufficient database replicas”.

• Section 5.2.8 describes how to detect and stop processes that are using a filesystem.

5.2.1 Monitoring Tasks

The monitoring of mirroring status can be done on user request and on system request.

Section 5.2.1.1 explains the DiskSuite� concepts needed to understand the diskmirroring.

Section 5.2.1.2 describes the system monitoring and how to configure it.

Sections 5.2.1.3 and 5.2.1.4 describe how to monitor the mirroring on user request.

5.2.1.1 DiskSuite�� Objects

The DiskSuite� Objects are metadevices, state database replicas and hot spare pools.

A metadevice is a name for a group of physical slices that appear to the system as asingle, logical device. Metadevices are actually pseudo, or virtual, devices in standardUNIX terms. They are used to increase storage capacity and increase data availability.The metadevices are concatenations, stripes, concatenated stripes, mirrors, RAID5metadevices, and trans metadevices. SPOTS only uses mirrors.

A state database is a database that stores information on disk about the state of yourDiskSuite� configuration (records and tracks changes made to disk configuration). Thedatabase is actually a collection of multiple, replicated database copies. Each copy,referred to as a state database replica, ensures that the data in the database is alwaysvalid.

SPOTS does not use hot spare pools and so they are not described here.

Mirrors (or RAID 1) consist of at least two submirrors. The storage of data isduplicated in all submirrors belonging to the same mirror. Submirrors are physical diskslices. Read performance is improved since either slice can be read at the same time (ifslices are in different disks). Write performance is the same as for single disk storage.


60 E200301-01-115-V10.0I-06

RAID 1 provides the best performance and the best fault-tolerance in a multi-usersystem.

In DiskSuite�, mirrors are made of one until three submirrors.

Mirrors and submirrors are metadevices.

5.2.1.2 Disk Failure Notification via Email

The mirroring status is checked periodically by the system. This check is done by thecrontab job /var/diskman/bin/dscheck.sh every 30 minutes.

If any problem is detected with the mirroring an email is issued to the root user with thestatus of all DiskSuite� Objects.

To change the default monitoring period or to stop the detection, edit the crontab as rootuser issuing the command:# crontab -e

Sections 5.2.1.3 and 5.2.1.4 explains the failure notification contents

The job can also be executed on user request with the following command:# /var/diskman/bin/dscheck.sh

and if a failure occurred then the root user will receive an email

To send failure notification to other users, create and edit the address list file/var/diskman/addresslist.txt and include one email address per line.

Example: To send the email to the local user spots and the remote user smith then theaddress list file contains the following:[email protected]

� Only local users that already exist can receive the email. For example, onlyafter the SPOTS software installation the user spots can be added to theaddress list. Before the installation the user spots does not exist.

� To send mails for remote users it is necessary, first, to configure thesendmail application.

5.2.1.3 Verifying the Status of State Database Replicas


� Execute the following shell command# metadb -i

mailto:[email protected]


E200301-01-115-V10.0I-06 61

� Inspect the output for problems.

The flags in the front of the device name represent the device status. Uppercaseletters indicate a problem status. Lowercase letters indicate an “Okay” status.

Take note of all slices that have replicas with problems (ex: c1t10d0s1).

� IMPORTANT NOTE: If any of the database replicas shows a problem,then the metadevices status must also be checked (if not yet checked). Tocheck the metadevices status use the procedure in Section 5.2.1.4. All thedisks with problems must be replaced with the procedure in Section 5.2.2.

Example of output with problems:flags first blk block count

a m p luo 16 1034 /dev/dsk/c1t0d0s4a p luo 16 1034 /dev/dsk/c1t8d0s4a p luo 16 1034 /dev/dsk/c1t1d0s1a p luo 16 1034 /dev/dsk/c1t9d0s1a p luo 16 1034 /dev/dsk/c1t2d0s1W p l 16 1034 /dev/dsk/c1t10d0s1

a p luo 16 1034 /dev/dsk/c1t3d0s1W p l 16 1034 /dev/dsk/c1t11d0s1W p l 16 1034 /dev/dsk/c1t4d0s1

a p luo 16 1034 /dev/dsk/c1t12d0s1a p luo 16 1034 /dev/dsk/c1t5d0s3a p luo 16 1034 /dev/dsk/c1t13d0s3

In the example, the slices c1t10d0s1, c1t11d0s1 and c1t4d0s1 have problems.

5.2.1.4 Verifying Status of Metadevices


� Execute the following shell command# metastat

� Inspect the output for problems.

If any Mirror Object shows state “Needs maintenance” for one submirror, takenote of device name (ex: c1t11d0s0).

If the two submirrors of one mirror show state “Needs maintenance” then data haspotentially been corrupted. In this case you must substitute the 2 disks and use therespective file system backups.

� IMPORTANT NOTE: If any metadevice shows a problem, then the statusof replicas must also be checked (if not yet checked). To check the status ofstate database replicas use the procedure in Section 5.2.1.3. All the diskswith problems must be replaced with the procedure in Section 5.2.2

Example of output with problems:d60: Mirror

Submirror 0: d61


62 E200301-01-115-V10.0I-06

State: OkaySubmirror 1: d62

State: Needs maintenancePass: 1Read option: roundrobin (default)Write option: parallel (default)Size: 71101179 blocks

d61: Submirror of d60State: OkaySize: 71101179 blocksStripe 0:

Device Start Block Dbase State Hot Sparec1t3d0s0 0 No Okay

d62: Submirror of d60State: Needs maintenanceInvoke: metareplace d60 c1t11d0s0 <new device>Size: 71101179 blocksStripe 0:

Device Start Block Dbase State Hot Sparec1t11d0s0 0 No Maintenance

In the example, the slice c1t11d0s0 has problems.

5.2.2 Replacing mirroring disks

This Section describes how to replace mirrored disks. It must be executed after mirroreddisk failure detection.



� Execute the command below to edit the crontab:# crontab -e

� Stop the email notification, by placing a comment character “#” in the beginningof the line containing the call to the dscheck.sh script, as shown below# 0,30 * * * * /var/diskman/bin/dscheck.sh > /dev/null 2>&1

� Save and exit the crontab file.

� Obtain the disk ids of disks with problems on state database replicas as describedin Section 5.2.1.3.

� Obtain the disk ids of disks with problems on metadevices as described in Section5.2.1.4.

� If this procedure is being executed because the system could not boot(Section 5.2.3), than add the disk ids found on that Section.

� Delete the entire database replicas contained in all the disks with problems indatabase replicas and in all the disks with problems in metadevices.


E200301-01-115-V10.0I-06 63

See Annex 5 to obtain slice ids of database replicas contained in disks withproblems.

To delete a state database replica refer to Section 5.2.4.2.

� Delete all submirrors contained in all disks with problems in database replicas andin all disks with problems in metadevices.

See Annex 5 to obtain mirror and submirror ids of submirror slices contained indisks with problems.

To delete a submirror refer to Section 5.2.4.4

� For Sun Blade host (non hot-plugable), shutdown the machine with command:# reboot

� Sun Fire host is hot-plugable and so disks may be switched without shuttingdown the system.

� Identify the disks to remove using the information filled in Annex 5

� Open the machine and remove the damaged disks

� Take note of the WWN (world wide number) and SN (serial number) numbers ofthe new disks and replace this information on Annex 5.

� Insert the new disks in the slots chosen in last step and close the machine.

� For Sun Fire host (hot-plugable) it is necessary to wait at least 1 minute,after disk removal, to insert the new disks.

� If the server is switched off, press the power button, wait for the login window andlogin as root user

� Format the new disks using the disk partition information on Annex 5 with theprocedure described in Section 5.2.5.

� Create a file system for each slice on the new disks using the information onAnnex 5 with the procedure described in Section 5.2.6.

� Create all database replicas to be contained in the new disks.

See Annex 5 to obtain the slice ids of database replicas contained in new disks.

To create a state database replica refer to Section 5.2.4.1

� The database replicas to be created are the same deleted on the damageddisks

� Create all submirrors to be contained in the new disks.

Refer to Annex 5 to obtain mirror ids, submirror ids and slice ids of the slicescontained in the new disks.

To create a submirror, refer to Section 5.2.4.3.


64 E200301-01-115-V10.0I-06

� The submirrors to be created are the same deleted on the damaged disks


� Activate the exception notification mechanism, by removing the commentcharacter “#” in the beginning of line containing the dscheck.sh script as shownbelow:0,30 * * * * /var/diskman/bin/dscheck.sh > /dev/null 2>&1

� Save and exit the crontab file.

� If the damaged disk contains one submirror of root (/) filesystem then replace therespective boot device by executing the following actions:

� Take note of the boot-device value executing the following shell command:# eeprom | grep boot-device

Example:# eeprom | grep boot-device

boot-device=/pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf8fb7d6,0:g/pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf8fb571,0:g disk

� Set the new boot-device value with the changed disk executing thefollowing shell command:# eeprom boot-device=<value>

Where <value> is the boot-device value obtained in the last step with thedamaged disk WWN substituted by the new disk WWN.

Example: If the disk with WWN 0004cf8fb7d6 was replaced by disk withWWN 0004deadbeef, than the new value is# eeprom boot-device=”/pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w21000004deadbeef,0:g/pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf8fb571,0:g disk”

Note that the 4 digits preceding the disk WWN of the damaged disk must bethe same in the new disk.

� Disk Replacement completed

5.2.3 Booting system with insufficient database replicas.

This section describes how to boot the system when, at booting time, is reported themessage “Insufficient metadevice database replicas located”.

This situation means that one or more disks are damaged and that the system cannotboot without maintenance.

To boot the system execute the following steps:


E200301-01-115-V10.0I-06 65

� Enter maintenance mode, typing the root password.

� Take note of the damaged replicas executing the procedure in Section 5.2.1.3.

� For each damaged database replica, execute the procedure in Section 5.2.4.2ignoring the possible “read-only” messages that can appear during the procedureexecution.

� Verify if there are no more damaged database replicas, by executing the procedurein Section 5.2.1.3 and take note of the damaged disks.

� Reboot system with the following command:# reboot


� Replace the damaged disks executing procedure in Section 5.2.2 adding thedamaged disks ids found with this procedure with the ones obtained with theprocedure 5.2.2.

5.2.4 Creating and Deleting DiskSuite�� Objects

This section describes how to create and delete DiskSuite� objects. The procedures inthis section are to be executed as part of other maintenance tasks.

5.2.4.1 Creating a DiskSuite�� State Database Replica

� IMPORTANT NOTE: Before creating a state database replica, thefilesystem must be created (with newfs command) and the partitions mustbe permanently un-mounted (using the umount command and removing themountpoint from /etc/vfstab file). When creating the replicas using theprocedure for disk substitutions (Section 5.2.2) the partitions are already un-mounted.


� Execute the command below:# metadb -a <slice>

Where <slice> must be replaced by the slice id.

Example:# metadb -a c0t2d0s0

� Verify the database replica creation by examining the output of the command# metadb -i


66 E200301-01-115-V10.0I-06

In the output, the flag “a” (meaning “active”) must be present on the createdreplica as in the example belowflags first blk block count...a u 16 1034 /dev/dsk/c0t2d0s0

5.2.4.2 Removing a DiskSuite�� State Database Replica


� Execute the command below:# metadb -d <slice>

where <slice> must be replaced by the slice id.

Example:# metadb -d c0t2d0s0

� Verify the database replica deletion by examining the output of command# metadb –i

5.2.4.3 Creating a DiskSuite�� submirror


� Execute the commands below:# metainit <submirror> 1 1 <slice># metattach <mirror> <submirror>

where <mirror>, <submirror> and <slice> must be replaced by thecorresponding ids.

Example:# metainit d72 1 1 c1t8d0s7# metattach d70 d72

� After attaching the submirror to the mirror, the newly attached submirrorstarts the synchronization process with the other submirror. Thesynchronization time depends on the slice size and on system hardware andcould take hours. Only when the to submirrors are synchronized, the mirrorcan assure data redundancy.

5.2.4.4 Removing a DiskSuite�� submirror

� IMPORTANT NOTE: The capability for data redundancy is lost while themirror is a one-way mirror.



E200301-01-115-V10.0I-06 67

� Execute the commands below:# metadetach -f <mirror> <submirror># metaclear <submirror>

where <mirror> and <submirror> must be replaced by the correspondingmetadevice ids.

Example:# metadetach -f d70 d72# metaclear d72

5.2.4.5 Removing a DiskSuite�� Mirror and Submirrors

� To remove mirroring from filesystems root (/), swap or /opt (file-systemsthat can not be un-mounted) execute the procedure of Section 5.2.4.6,instead.

� Consult the information on Annex 5 and obtain the mirror id and the sub-mirrors ids and mount-points.

� Verify that a current backup of the metadevice exists. Operation errors maycause data loss.



� Only the root user can be logged to the machine (logout all remote users).

� Stop SPOTS as described in Section 3.3.4.

� Stop all access to the metadevice. Verify and stop metadevice access withprocedure in Section 5.2.8

� Confirm the mirror and submirror ids issuing the command# metastat <metadevice>

Where <metadevice> is the mirror id

Example:# metastat d70

� Unmount the filesystem where resides the mirror to be removed, using umountcommand.

Example: to remove the /export/home filesystem# umount /export/home


68 E200301-01-115-V10.0I-06

� Delete the submirror that does not contain the word “mirror” in the mountpointfield of disk table on Annex 5 (example: /export/home) using the commandsbelow:# metadetach -f <mirror> <submirror># metaclear <submirror># metaclear <mirror>


Example:# metadetach -f d70 d71# metaclear d71# metaclear d70

� Edit the /etc/vfstab file and perform the following actions:

1. Uncomment the line (remove the “#” character from the beginning of the line)containing the mountpoint and the slice.

2. Delete the line containing the metadevice and the mountpoint.

Example: for /export/home mirror, the line:#/dev/dsk/c1t0d0s4 /dev/rdsk/c1t0d0s4 /export/home ufs 2 yes -

Should be changed to:/dev/dsk/c1t0d0s4 /dev/rdsk/c1t0d0s4 /export/home ufs 2 yes –

And the lines below should be deleted:# home mirror

/dev/md/dsk/d70 /dev/md/rdsk/d70 /export/home ufs 2 yes –

� Mount the filesystem with the command mount

Example: for /export/home filesystem use the command:# mount /export/home

� Delete the second submirror, the one containing the word “mirror” in themountpoint field of disk table on Annex 5 (example: /home_mirror), using thecommands below# metaclear <submirror>

Where <submirror> must be replaced by the corresponding metadevice id.

Example:# metaclear d72

� Create the mountpoint directory, for this last submirror, using the command belowand the information on Annex 5.# mkdir <mountpoint>

where <mountpoint> is the mountpoint directory


E200301-01-115-V10.0I-06 69

Example: if the mountpoint is /home_mirror then issue the command:# mkdir /home_mirror

� Edit the /etc/vfstab file and uncomment the line (remove the “#” character fromthe beginning of the line) that contains the mountpoint and the slice.

Example: for /home_mirror partition, the line:#/dev/dsk/c1t1d0s4 /dev/rdsk/c1t1d0s4 /home_mirror ufs 2 yes -

Should be changed to:/dev/dsk/c1t1d0s4 /dev/rdsk/c1t1d0s4 /home_mirror ufs 2 yes -

� Mount the filesystem with the command mount# mount <filesystem>

Where <filesystem> is the filesystem to mount

Example: for /home_mirror filesystem use the command:# mount /home_mirror

5.2.4.6 Unmirroring a File System That Cannot Be Unmounted

� This procedure is only for filesystems that cannot be unmounted, such asroot (/), swap or /opt. For other filesystems execute the procedure ofSection 5.2.4.5, instead.

� Consult the information on Annex 5 and obtain the mirror id and the sub-mirrors ids and mount-points.

� Verify that a current backup of the metadevice exists. Operation errors maycause data loss.



� Confirm the mirror and submirror ids issuing the command# metastat <metadevice>


Example:# metastat d100

� Remove the submirror that does not contain the word “mirror” in the mountpointfield of disk table on Annex 5 (example: /opt) from the mirror using thecommand below:# metadetach -f <mirror> <submirror>


70 E200301-01-115-V10.0I-06


Example:# metadetach -f d100 d101

� For swap or /opt filesystems, edit the /etc/vfstab file and followingperform the following actions:

1. Uncomment the line (remove the “#” character from the beginning of theline) that contains the mountpoint point and the slice.

2. Delete the line containing the metadevice and the mountpoint.

Example: for swap mirror, the lines:#/dev/dsk/c1t0d0s1 - - swap - no –# swap mirror/dev/md/dsk/d90 - - swap - no -

Should be changed to:/dev/dsk/c1t0d0s1 - - swap - no -

� For root (/) filesystem execute the command:# metaroot /dev/dsk/<slice>

where <slice> is slice id of the root filesystem (/) on Annex 5.

Example:# metaroot /dev/dsk/c0t3d0s0

� Reboot the system with command:# reboot


� Remove the mirror executing command:# metaclear <metadevice>


Example:# metaclear d100

� Delete the two submirrors using the commands below# metaclear <submirror1># metaclear <submirror2>

Where <submirror1> and <submirror2> must be replaced by thecorresponding metadevice ids.

Example:


E200301-01-115-V10.0I-06 71

# metaclear d101# metaclear d102

� Create the mountpoint directory, for submirror that has the word “mirror”, usingthe command below and the information on Annex 5.mkdir <mountpoint>

where <mountpoint> must be replaced by the moutpoint name

Example: if the mount point is /root_mirror then issue the command:mkdir /root_mirror

� Edit the /etc/vfstab file and uncomment the line (remove the “#” character fromthe beginning of the line) that contains the mountpoint point and the slice.

Example: for /root_mirror partition, the line:#/dev/dsk/c1t1d0s6 /dev/rdsk/c1t1d0s6 /root_mirror ufs 2 yes -

Should be changed to:/dev/dsk/c1t1d0s6 /dev/rdsk/c1t1d0s6 /root_mirror ufs 2 yes -

� Mount the filesystem with the command mount# mount <mountpoint>

where <mountpoint> must be replaced by the moutpoint name

Example: for /root_mirror filesystem use the command:# mount /root_mirror

5.2.5 Formatting Disks

This procedure is to be executed as part of the disk replacement procedure. Do notexecute it as a generic format procedure.

� To format a disks, the information saved in Annex 5 is needed in order toreproduce the slices of the damaged disk in the new one.

� It is not necessary to add new information to Annex 5 upon a new diskformating.


� Start the format utility# format

� A list of available disks is displayed.

� Compare the disk geometry of the disk to format with the original one (refer toAnnex 5).

� Enter the number of the disk to repartition from the list displayed.


72 E200301-01-115-V10.0I-06

Specify disk (enter its number): <disk-number>

� <disk-number> is the number of the disk to repartition.

� When replacing a disk then the disk id (ex: c1t3d0) of the new disk is thesame of the old disk

� Go into the partition menu (which allows to set up the slices).format> partition

� Start the modification process.partition> modify

� Set the disk to all free hog.Choose base (enter number) [0]? 1

� Create a new partition table by answering y when prompted to continue.Do you wish to continue creating a new partition table basedon above table[yes]? y

� Identify the free hog partition (slice).

� The free hog partition must be one of the slices containing a DiskSuite�state database replica (a slice that contains a /replica mount point).

� Enter the slice sizes when prompted (ignore the slices tag and flag values).

� If the new disk has the same geometry of the original one then the slice sizesmust be entered in cylinders (ex: 1234c). If it is not of the same geometrythen enter the size of each partition in megabytes adding 3 megabytes to thesize of the original partition. To know the new disk geometry, execute theformat command. The damaged disk geometry is stored in Annex 5.

� The new partition table is now displayed.

� Make the displayed partition table the current partition table by answering “y”when asked.Okay to make this the current partition table[yes]? y

To change the current partition table, answer no and go back to start themodification process.

� Name the partition table.Enter table name (remember quotes): "<partition-name>"

<partition-name> is any name you choose for the new partition table. Example:“disk6”.

� Label the disk with the new partition table when you have finished allocatingslices on the new disk.


E200301-01-115-V10.0I-06 73

Ready to label disk, continue? yes

� Quit the partition menu.partition> q

� To partition more disks issue the command bellow, and the return to the “Go intothe partition menu” step.format> disk

� Quit the format menu.format> q

5.2.6 Creating File Systems

This procedure is to be executed as part of the disk replacement procedure. Do notexecute it as a generic procedure to create filesystems.

� To create a new filesystem, the information saved in Annex 5 must be used.


� Create a file system for each slice with the newfs command.# newfs /dev/rdsk/<cwtxdysz>

where <cwtxdysx> is the raw device for the file system to be created.

Answer y when prompted.

� Ignore the unallocated cylinders warning.

Example: To create a filesystem for slice c1t8d0s7 then use the command:# newfs /dev/rdsk/c1t8d0s7newfs: /dev/rdsk/c1t8d0s7 last mounted as /export/homenewfs: construct a new file system /dev/rdsk/c1t8d0s7: (y/n)? y/dev/rdsk/c1t8d0s7: 2088746 sectors in 723 cylinders of 27 tracks, 107 sectors

1019.9MB in 46 cyl groups (16 c/g, 22.57MB/g, 10816 i/g)super-block backups (for fsck -F ufs -o b=#) at:32, 46368, 92704, 139040, 185376, 231712, 278048, 324384, 370720, 417056,463392, 509728, 556064, 602400, 648736, 695072, 741408, 787744, 834080,880416, 926752, 973088, 1019424, 1065760, 1112096, 1158432, 1204768, 1251104,1297440, 1343776, 1390112, 1436448, 1479200, 1525536, 1571872, 1618208,1664544, 1710880, 1757216, 1803552, 1849888, 1896224, 1942560, 1988896,2035232, 2081568,

5.2.7 Associating Disk ids to WWNs and Rack Numbers

This procedure is to be executed as part of the mirroring configuration and diskreplacement procedures. Do not execute it as a generic procedure.

The luxadm command can be used to relate the disk id and the disk World-Wide-Number (WWN) for optical disks.

To obtain the relation do the following:

For Sun Blade Machine


74 E200301-01-115-V10.0I-06

� Execute the following command:# luxadm probe

For each WWN, the disk id that can be found as part of the path.

� Note that the Node WWN is the concatenation of 4 digit Node number with12 digit Disk WWN.

Output example:# luxadm probeNo Network Array enclosures found in /dev/es

Found Fibre Channel device(s):Node WWN:2000002037ef8360 Device Type:Disk deviceLogical Path:/dev/rdsk/c2t1d0s2

Node WWN:2000002037cdab8c Device Type:Disk deviceLogical Path:/dev/rdsk/c2t2d0s2

On the example above, the disk id c2t1d0 belongs to WWN 002037ef8360

For Sun Fire machine

� Execute the following command:# luxadm probe

Output example:# luxadm probeFound Enclosure:SUNWGS INT FCBPL Name:FCloop Node WWN:50800200001a1150Logical Path:/dev/es/ses0

� Execute the following command:# luxadm display <logical-path>

replacing <logical-path> by the logical path obtained in the previous step.

In the output the slot (rack number) can relate with the disk WWN. Note that theNode WWN is the concatenation of 4 digit node number with 12 digit disk WWN.

Output example:# luxadm display /dev/es/ses0

SUNWGS INT FCBPLDISK STATUS

SLOT DISKS (Node WWN)0 On (O.K.) 20000004cf8fb7d61 On (O.K.) 20000004cf8fb5712 On (O.K.) 20000004cf8f2f413 On (O.K.) 20000004cf8fb0764 Not Installed5 On (O.K.) 20000004cf8fb2696 On (O.K.) 20000004cf8fc1577 On (O.K.) 20000004cf8fc0ed8 On (O.K.) 20000004cf8fbd60


E200301-01-115-V10.0I-06 75

9 On (O.K.) 20000004cf8fa9fa10 On (O.K.) 20000004cf8fabd311 On (O.K.) 20000004cf8fa936

SUBSYSTEM STATUSFW Revision:9226 Box ID:0Node WWN:50800200001a1150 Enclosure Name:FCloop

SSC100's - 0=Base Bkpln, 1=Base LoopB, 2=Exp Bkpln, 3=ExpLoopB

SSC100 #0: O.K.(9226/ FD99)SSC100 #1: O.K.(9226/ FD99)SSC100 #2: O.K.(9226/ FD99)SSC100 #3: O.K.(9226/ FD99)

Temperature Sensors - 0 Base, 1 Expansion0:23ºC 1:25ºC (All temperatures are NORMAL.)

Default Language is USA English, ASCII

� Check the output of the previous command with the information on “DiskLocation Table” of on Annex 5, for fields rack number (slot) and disk WWN.

� Note that the Node WWN, of previous step, is the concatenation of 4 digitNode number with 12 digit Disk WWN.

� For all disks execute the following command:# luxadm display <node-wwn>

replacing <node-wwn> by the Node WWN for each disk WWN.

For each output take note of the disk id that can be found as part of the path.

Output example:# luxadm display 20000004cf8fbd60DEVICE PROPERTIES for disk: 20000004cf8fbd60Status(Port B): O.K.Vendor: SEAGATEProduct ID: ST336605FSUN36GWWN(Node): 20000004cf8fbd60WWN(Port B): 21000004cf8fbd60Revision: 0538Serial Num: 3FP1K4ZF0000Unformatted capacity: 34732.891 MBytesRead Cache: EnabledMinimum prefetch: 0x0Maximum prefetch: 0xffff

Location: In the enclosure named: FCloopDevice Type: Disk devicePath(s):/dev/rdsk/c1t10d0s2

/devices/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf8fbd60,0:c,raw

On the example above, the disk id is c1t10d0

5.2.8 Detect and terminate processes that are using a filesystem


76 E200301-01-115-V10.0I-06

This procedure is to be executed as part of the mirroring configuration and diskreplacement procedures. Do not execute it as a generic procedure.

To detect the processes that are using a filesystem do the following:

� Execute the command:below:# cat /etc/vfstab

Output example:# cat /etc/vfstab#device device mount FS fsck mount mount#to mount to fsck point type pass at boot options##/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes -fd - /dev/fd fd - no -/proc - /proc proc - no -/dev/dsk/c1t1d0s1 - - swap - no -/dev/dsk/c1t1d0s3 /dev/rdsk/c1t1d0s3 / ufs 1 no -/dev/dsk/c1t1d0s7 /dev/rdsk/c1t1d0s7 /export/home ufs 2 yes -/dev/dsk/c1t2d0s6 /dev/rdsk/c1t2d0s6 /home_mirror ufs 2 yes -/dev/dsk/c1t1d0s4 /dev/rdsk/c1t1d0s4 /opt ufs 2 yes -/dev/dsk/c1t2d0s4 /dev/rdsk/c1t2d0s4 /opt_mirror ufs 2 yes -/dev/dsk/c1t1d0s0 /dev/rdsk/c1t1d0s0 /replica1 ufs 2 yes -/dev/dsk/c1t1d0s6 /dev/rdsk/c1t1d0s6 /replica2 ufs 2 yes -/dev/dsk/c1t2d0s1 /dev/rdsk/c1t2d0s1 /replica3 ufs 2 yes -/dev/dsk/c1t2d0s7 /dev/rdsk/c1t2d0s7 /replica4 ufs 2 yes -/dev/dsk/c1t2d0s3 /dev/rdsk/c1t2d0s3 /root_mirror ufs 2 yes -/dev/dsk/c1t1d0s5 /dev/rdsk/c1t1d0s5 /var/opt ufs 2 yes -/dev/dsk/c1t2d0s5 /dev/rdsk/c1t2d0s5 /var_opt_mirror ufs 2 yes -/dev/dsk/c1t2d0s0 /dev/rdsk/c1t2d0s0 /swap_mirror ufs 2 yes -swap - /tmp tmpfs - yes -/dev/dsk/c2t1d0s1 /dev/rdsk/c2t1d0s1 /spots_db1 ufs 2 yes -/dev/dsk/c2t4d0s0 /dev/rdsk/c2t4d0s0 /spots_db2 ufs 2 yes -/dev/dsk/c2t2d0s0 /dev/rdsk/c2t2d0s0 /spots_db3 ufs 2 yes -/dev/dsk/c2t5d0s0 /dev/rdsk/c2t5d0s0 /spots_db4 ufs 2 yes -/dev/dsk/c2t3d0s0 /dev/rdsk/c2t3d0s0 /spots_db5 ufs 2 yes -/dev/dsk/c2t6d0s0 /dev/rdsk/c2t6d0s0 /spots_db6 ufs 2 yes -

� The output of the last step contains devices and mountpoints. Take note of thefilesystem device (the value at the first column) of the filesystem mountpoint (thevalue at the third column) that is to be checked.

Example:

To check the usage of filesystem /export/home then, in the output of theexample above, take note of the value /dev/dsk/c1t1d0s7

� Execute the command below:# fuser <device>

Where <device> is the filesystem device to check.

Output example:# fuser /dev/dsk/c1t0d0s7/dev/dsk/c1t0d0s7: 614o

� The output of command last command shows the list of process identifiers (eachone followed by a letter) that are using the filesystem. If no process identifier wasshown, than no process is using the filesystem and your detection is finished. Ifthe list is not empty then continue the detection.

� For each process identifier obtained execute the steps below:

� Execute the following command to know the process name:


E200301-01-115-V10.0I-06 77

# ps -e -o pid,comm | grep <process-id>

Where <process-id> is the process identifier.

Output example:# ps –e –o pid,comm | grep 6141221 grep 614614 rpc.ttdbserverd

� In the output of the last step are the process identifier and the process nameof the service to be stopped. If there is more than one line of output, than thecorrect line is the one that does not have the grep command.

� If you don’t know how to stop the service execute the command# kill <process-id>


Then verify is process was terminated executing the last step. If the outputshows the process than execute the command:# kill -9 <process-id>


� Verify that all processes terminated successfully by executing the commandbelow:# fuser <device>

Where <device> is the filesystem device to check.

If the output does not show an empty list then execute the whole procedure again(procedure 5.2.8).


78 E200301-01-115-V10.0I-06

5.3 De-installation Tasks

The un-installation tasks allow the removal of the mirroring configuration and theDiskSuite� Software.

5.3.1 Un-mirroring Disks

� Verify that a current backup of the metadevices to un-mirroring is available.Operation errors may cause data loss.




� Remove the Failure Notification via Email, deleting the line containing the call todscheck.sh script. The line is:0,30 * * * * /var/diskman/bin/dscheck.sh > /dev/null 2>&1

� Save and exit the crontab file edition.

� Remove all mirrors using the information on Annex 5 with the proceduredescribed in Section 5.2.4.5.

� Verify that no mirrors exist, using the procedure in Section 5.2.1.4. No mirrorsshould be reported by the procedure.

� Remove all state database replicas using the procedure described in Section5.2.4.2� To remove the last state database replica, the “–f” flag must be used as

shown in the example:# metadb -d –f c0t2d0s0

� Verify that no state database replicas exist, using the procedure in Section 5.2.1.3.No state database replicas should be reported by the procedure.

� For each state database replica partition, consult the mountpoint on Annex 5proceed as follows:

� Edit the /etc/vfstab to remove the comment char (#) that is in thebeginning of the line containing the moutpoint.

� Create the mountpoint directory with the command:mkdir /<mountpoint>


E200301-01-115-V10.0I-06 79

replacing <mountpoint> by the partition mountpoint.

� Mount the partition with the command:mount /<mountpoint>

replacing <mountpoin>t by the partition mountpoint.

� Remove the alternate boot device with the following actions:

� Take note of the boot-device value executing the following shell command:# eeprom | grep boot-device

Example:# eeprom | grep boot-device

boot-device=/pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf8fb7d6,0:g/pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf8fb571,0:g disk

� Take note of the alternate boot device on Annex 5

� With following shell command, set the new boot-device value with thevalue obtained in last step without the alternate boot device:# eeprom boot-device=<value>

replacing <value> by the new boot-device value

5.3.2 De-installing Solstice Disksuite�� Software

This procedure de-installs the Solstice DiskSuite� Software

� Before de-installing DiskSuite� it is necessary to remove all DiskSuite�objects as described in to Section 5.3.1.


� Execute the following shell command# pkgrm SUNWmdx SUNWmdg SUNWmdu SUNWmdr


� Restart the system, entering the shell command:# reboot

� Solstice Disksuite� Software successfully de-installed


80 E200301-01-115-V10.0I-06

6 Installing Oracle�� Software

This chapter describes in detail the necessary actions that must be performed to installOracle� software according to SPOTS requirements. Before proceeding read carefullythe following note:

� The actions to be performed in this chapter assume “/opt/oracle“ as the Oracle�installation directory since it is the most commonly used location. Nevertheless, ifdesired, it is possible to install Oracle� in a different base directory. To do so,substitute any reference to the recommended “/opt/oracle” path by the desiredone.

6.1 Creating Groups and Users

This section describes a series of preliminary tasks to be executed before installing theOracle� software.This installation step is applicable only to the hosts where the SPOTS Database ServerSW package and SPOTS Database are installed.It comprises the creation of the user responsible for Oracle� system administration andits execution environment.


� Verify that the DISPLAY environment variable is correctly set

� Execute the following command:# admintool

� Click on the “Browse” menu and select the “Groups” option.

� Click on the “Edit” menu and select the “Add…” option:

� Add groups “dba” and “oinstall” as depicted below:

� The Group ID is not relevant, provided that it is unique.


E200301-01-115-V10.0I-06 81

� Click on the “Browse” menu and select the “Users” option.

� Click on the “Edit” menu and select the “Add” option.

� Add “oracle” user according to the profile depicted in the following picture:

� The User ID is not relevant, provided that it is unique.

� When questioned, set oracle user password and confirm it


82 E200301-01-115-V10.0I-06

� Click on the “File” menu and select the “Exit” option to terminate this task.

� Create the Oracle� installation directory by executing the following commands (ifdesired, modify the installation directory):# mkdir /opt/oracle# chown oracle:oinstall /opt/oracle

� Login as oracle user

� Choose the default desktop:“Common Desktop Environment (CDE)”

� Insert the SPOTS V10 Drop 4 (long-term) CD-ROM

� Create the oracle user profile:

� The profile of the oracle user present in the CD-ROM defines theORACLE_BASE to its most commonly used value “/opt/oracle”.

� Copy the oracle user profile from the CD-ROM and if necessary, edit it tomatch the desired installation directory:$ cp /cdrom/cdrom0/utils/oracle.profile .profile

� Remove the SPOTS V10 Drop 4 CD-ROM from the device:$ eject

� Logout oracle user.

� Creation of the Oracle� Software groups and user completed.


E200301-01-115-V10.0I-06 83

6.2 Installing Oracle�� Software

The present section guides you through the Oracle� Software installation. Be sure toexecute the following steps only if the previous section is successfully completed.

� Insert the Oracle�8i Enterprise Edition Release 3 (8.1.7) 1 of 2 CD.

� Login as oracle user.

� Verify that the DISPLAY environment variable is correctly set.

� Start the Oracle� Universal Installer program, executing the followingcommands:$ cd /cdrom/cdrom0$ runInstaller

� The Welcome window of the Oracle� Universal Installer program is displayed. Tonavigate between windows use the “Previous” and “Next” buttons.

� Enter the File Locations:

� Source…“/cdrom/oracle8i/stage/products.jar”

�� If Oracle� is installed in a non-default directory, assume that “/opt/oracle”path refers to the previously chosen Oracle� installation directory.

� Destination…“/opt/oracle/product/8.1.7”

� Enter the UNIX Group Name:“oinstall”

� Oracle� Installer program presents the window depicted hereafter. Proceed for thenext step and follow the instructions.


84 E200301-01-115-V10.0I-06

� Execute the following commands in the Unix shell where Oracle� UniversalInstaller program was started and then click on the Retry button of the windowto continue:�� If Oracle� is installed in a non-default directory, assume that “/opt/oracle”

path refers to the previously chosen Oracle� installation directory.$ su –# /opt/oracle/product/8.1.7/orainstRoot.sh# exit

� Select the Product to install:“Oracle8i Enterprise Edition 8.1.7.0.0”

� Select the Installation Type:“Custom”

� Select the Product Components to install (unselect all the others):“Oracle8i Server 8.1.7.0.0”“Oracle Product Options 8.1.7.0.0”

Select only the following option:“Oracle Partitioning 8.1.7.0.0”

�� To unselect Oracle Spatial 8.1.7.0.0 it is necessary to unselect, first,Oracle Visual Information Retrieval 8.1.7.0.0 and then OracleinterMedia 8.1.7.0.0.

“Net8 Products 8.1.7.0.0”Select only the following options:

“Net8 Client 8.1.7.0.0”“Net8 Server 8.1.7.0.0”“Oracle Protocol Support 8.1.7.0.0”

“Oracle Utilities 8.1.7.0.0”Select all options.

� Define the Component Location for Java Runtime Environment, by default:


E200301-01-115-V10.0I-06 85

“/opt/oracle/jre/1.1.8”

� Define the Privileged Operating System Groups, as follows:

� Database Administrator (OSDBA) Group:“dba”

� Database Operator (OSOPER) Group“dba”

� Create a new Database, using the Oracle� Database Configuration Assistant:“No”

� Continue to the next window, accepting the pre-selected Oracle� ProtocolSupport.

� Revise the Installation Summary window, if the information is correct,proceed to installation; otherwise, before proceeding with installation, returnto the previous windows in order to correct the problem(s).

� Installing, please wait…

� Exchange to Oracle�8i Enterprise Edition Release 3 (8.1.7) 2 of 2 CD:

� When the Disk Location window appears, in the Unix shell where Oracle�Universal Installer program was started, execute the following shellcommands:$ cd /$ eject cdrom

� Insert Oracle�8i Enterprise Edition Release 3 (8.1.7) 2 of 2 CD.

� Enter the path in the Disk Location window:“/cdrom/cdrom0/”

� Running “root.sh” script:



86 E200301-01-115-V10.0I-06

� When the Setup Privileges window appears, execute the followingcommands in the Unix shell where Oracle� Universal Installer program wasstarted (Note: user interaction is in bold letters):$ suPassword: <root password># cd /opt/oracle/product/8.1.7# ./root.shRunning Oracle8 root.sh script...ORACLE_SID is not set.

The following environment variables are set as:ORACLE_OWNER= oracleORACLE_HOME= /opt/oracle/product/8.1.7ORACLE_SID=

Enter the full pathname of the local bindirectory:[/usr/local/bin]: /usr/bin

Creating /var/opt/oracle/oratab file...Adding entry to /var/opt/oracle/oratab file...Finished running generic part of root.sh script.Now product-specific root actions will be performed.IMPORTANT NOTE:

Please delete any log and trace files previouslycreated by the Oracle Enterprise Manager IntelligentAgent. These files may be found in the directoriesyou use for storing other Net8 log and trace files.If such files exist, the OEM IA may not restart.

# exit

� On the Setup Privileges window, click on the OK button to continue.

� Welcome to the Net8 Configuration Assistant.

�� The required Net8 Configuration is done during the execution of the SPOTSinstallation procedure. Thus, the Oracle� Net8 Configuration is not performednow.

� Click on the Cancel button to continue.

� Confirm the request to cancel the Net8 Configuration, clicking on the Yes buttonof the presented dialogue box.


E200301-01-115-V10.0I-06 87

� Click on the OK button to continue:

� Exit from the Oracle� Universal Installer program, clicking on the Exit

button.

� Confirm Exit from the Oracle� Installer program, clicking on the Yes button.

� Eject the CD-ROM, executing these shell commands in the Unix shell whereOracle� Universal Installer program was started:$ cd /$ eject cdrom

� ORACLE� Software installed.


88 E200301-01-115-V10.0I-06

6.3 Installing Oracle�� Patch Set

The SPOTS SW is distributed along with an Oracle�8i Patch Set, which must beinstalled after the Oracle�8 installation. SPOTS SW is certified to be used only with theversion of the Oracle� Patch Set distributed with the SPOTS CD.

� There is no mechanism provided for de-installing Oracle� patch sets. If you areconcerned about being able to de-install the patch set, it is recommended that youback up your software installation, before applying the patch set.

To proceed with installation complete the following steps:

� Insert the Oracle�8i Enterprise Edition Release 3 (8.1.7) 1 of 2 CD.

� Login as oracle user.

� Verify that the DISPLAY environment variable is correctly set.

� Start the Oracle� Universal Installer program, executing the followingcommands:$ cd /cdrom/cdrom0$ runInstaller

� The Welcome window of the Oracle� Universal Installer program is displayed.

� In the Installer window press the Next button.

� Eject Oracle� CD, executing these shell commands in the Unix shell whereOracle� Universal Installer program was started:$ cd /$ eject cdrom

� Insert the Patches CD-ROM distributed with SPOTS.

� Back in the Installer window, enter File Locations:

� Source…“/cdrom/cdrom0/oracle/stage/products.jar”

�� Verify that the Destination field contains the path to the directory whereOracle� is installed, by default “/opt/oracle/product/8.1.7”.

� Destination…“/opt/oracle/product/8.1.7”

� Press the Next button to load the list of products.

� Press the Install button to install the patch set.

� Installing, please wait…Upon successful installation, the End of Installation message is displayed.


E200301-01-115-V10.0I-06 89

� Press the Exit button and confirm that you want to leave the Installer.

� Eject the Patches CD-ROM, executing the following shell command in the Unixshell where Oracle� Universal Installer program was started:$ eject cdrom

� ORACLE� Software upgraded.


90 E200301-01-115-V10.0I-06

6.4 De-installing Oracle�� Software

A specific Oracle� Product can be de-installed by means of the “orainst” program,which will assist you during the procedure. To de-install all components of the Oracle�Software from your system, run the following steps:

�� If the existing database(s) contents must be preserved, a data migration proceduremust be executed. This procedure must fit the (new) Oracle� Software to beinstalled. Therefore, SPOTS Support Service must be contacted, to provide thespecific migration package.


� De-install Oracle�:


� Execute the following command sequence:# rm –rf /opt/oracle/*# rm –rf /var/opt/oracle/*# userdel -r oracle# groupdel dba# groupdel oinstall

� Oracle� Software de-installed.


E200301-01-115-V10.0I-06 91

7 Installing SPOTS Software (Solaris�� environment)

This chapter deals with the installation of SPOTS PMS and PMC components onSolaris� environments. For the installation of SPOTS PMC on Windows�environments, refer to Chapter 8.

� Before proceeding, make sure you have read Section 2 which provides anoverview of SPOTS PMS and PMC components.

In a Solaris� environment, two different methods for performing software administra-tion are supported:

• Admintool, a graphical front-end to the package commands.For a detailed description about adding or removing SPOTS software usingadmintool, refer to Sections 7.1 or 9.3.1 respectively.

• Package commands (pkgadd, pkgrm and pkginfo).For a detailed description about adding or removing SPOTS software usingpackage commands, refer to Sections 7.2 or 9.3.2 respectively.


92 E200301-01-115-V10.0I-06

7.1 Adding SPOTS SW with admintool

The tool admintool offers ease of use, as it is a graphical interface to the pkgadd andpkgrm commands and it includes online help providing general information on using thetool. The user can also benefit from admintool as it offers detailed information about thespecified product, including approximate disk space requirements. Using the admintoolgraphical browser provides a modular view of the contents of the installation medium.

These reasons make admintool a preferential tool in software administration, unless youdo not meet the requirements described in the following notice:

� The admintool software manager requires a bit-mapped display monitor andthe ability to use the OpenWindows� environment. If these requirements arenot met, all software-related tasks can alternatively be performed using thepackage administration commands.


� Insert the SPOTS V10 Drop 4 (long-term) CD.

� Volume Manager utility will automatically mount it.

� Verify that the DISPLAY environment variable is set and start admintool:# admintool &

� Admintool provides online help with general information on using the tool. Use itwhenever necessary, accessing the “Help” menu or through the context sensitiveHelp button.

� Select “Software” from the Admintool “Browse” menu.

� The Admintool: Software window is displayed, listing all software currentlyinstalled in your system.

� Select “Add...” from the “Edit” menu.

� The Admintool: Set Source Media window will appear.

� Set the Source Media as indicated below:

� Software Location:“CD with Volume Management”

� CD Path:“/cdrom/cdrom0”

� Click on the OK button to acknowledge.

� Back in the Admintool: Add Software window, click on the checkbox on theSoftware field to select “SPOTS 10.0”.

� Press the Customize... button.


E200301-01-115-V10.0I-06 93

� In the Admintool: Customize Installation window, the installer is invited to specifythe SPOTS components to install. To proceed with the installation, execute thefollowing actions:

� Expand SPOTS Performance Management Client (PMC), SPOTSPerformance Management Server (PMS) and SPOTS Upgrade options,pressing the triangle-shapped bullet (refer toFigure 2).

� The packages in PMC, PMS and SPOTS Upgrade are displayed.� Do not select SPOTS Upgrade option unless you’re performing a "Data

Migration" as described in Section 3.3 or an "APS Upgrade withoutDatabase Reinstallation" as described in Section 3.2.1. SPOTS DataMigration package must be installed in the host where SPOTS database isinstalled.

� Select/De-select the components to install, clicking on the inner squarebullets.

� Confirm your choice, clicking on the OK button.

Figure 2 – Fully expanded "Admintool: Customize Installation" window

� Back to the Admintool: Add Software window, click on the Add button.

� The warning message in Figure 3 may appear. If so, ignore it, clicking on the“Continue” button. To disable it permanently, set the “Check here todisable this message” option before pressing “Continue”.


94 E200301-01-115-V10.0I-06

Figure 3 – Desktop Environment warning

� A window will appear, prompting you for information about the installation of theselected packages.

� Install the SPOTS packages, as described in Section 7.3.

� Return to Admintool: Software window, pressing the <Return> key.

� Exit admintool, selecting “Exit” from the “File” menu.

� Complete the SPOTS software installation, executing the post-installationprocedures, as described in Section 7.4.

� Selected SPOTS components are now installed in the local host. Then, proceedaccording to the intended SPOTS environment:Single Server Installation completed, all SPOTS components are now installed

in the local host.Distributed Local installation completed. Log on another platform and repeat

the installation process until all the desired SPOTS componentsare installed in the corresponding platforms.

� Once all SPOTS components are installed, refer to Annex 3 for configuring theSPOTS domains and to Annex 4 for verifying and adjusting the SPOTS serverproperties.


E200301-01-115-V10.0I-06 95

7.2 Adding SPOTS Software with Package Commands

Using the pkgadd and pkgrm commands offers flexibility. For example, you canincorporate these commands into scripts, set up optional files to avoid user interactionor perform special checks, and copy software packages to spool directories.


� Insert the SPOTS V10 Drop 4 (long-term) CD.

� Execute the following command:# /usr/sbin/pkgadd -d /cdrom/cdrom0/spots

� As a result, the pkgadd menu is displayed, prompting for the SPOTS packages toinstall in this host:

The following packages are available:

1 SpotsAS SPOTS Application Server(sparc) 10.0.0

2 SpotsCL SPOTS CLient(sparc) 10.0.0

3 SpotsDM SPOTS Data Migration(sparc) 10.0.0

4 SpotsDS SPOTS Database Server(sparc) 10.0.0

5 SpotsNS SPOTS Naming Server(sparc) 10.0.0

Select package(s) you wish to process (or 'all' to processall packages). (default: all) [?,??,q]:

� Do not install SpotsDM package unless you’re performing a Data Migration asdescribed in Section 3.3 or an "APS Upgrade without Database Reinstallation" asdescribed in Section 3.2.1. SpotsDM package must be installed in the host whereSPOTS database is installed.

� When installing several SPOTS packages in the same host, the order ofinstallation is relevant:• SpotsDS package must be installed last.• SpotsNS package should be installed first in order to ease the installation steps.

� To select the packages use the following method:

• Enter one (or more) package(s) at a time by installation order. Typically, forinstalling a Single Server configuration enter “5 1 2 4”, this would installSpotsNS, SpotsAS, SpotsCL and SpotsDS by this exact order and then reprintthe menu, waiting for new input, which can be to install another package or toquit (q) the pkgadd command.

� Type in the menu item(s) of the SPOTS component(s) you wish to install in thelocal host.


96 E200301-01-115-V10.0I-06

� After installing all the desired packages just quit the pkgadd tool, entering theoption “q”:The following packages are available:

1 SpotsAS Spots Application Server(sparc) 10.0

2 SpotsCL Spots CLient(sparc) 10.0

3 SpotsDM Spots Data Migration(sparc) 10.0

4 SpotsDS Spots Database Server(sparc) 10.0

5 SpotsNS Spots Naming Server(sparc) 10.0

Select package(s) you wish to process (or 'all' to processall packages). (default: all) [?,??,q]: q

� Complete the SPOTS software installation, executing the post-install procedures,as described in Section 7.4.

� Selected SPOTS components are now installed in the local host. Then, proceedaccording to the intended SPOTS environment:Single Server Installation completed, all SPOTS components are now installed

in the local host.Distributed Local installation completed. Log on another platform and repeat

the installation process until all the desired SPOTS componentsare installed in the corresponding platforms.

� Once all SPOTS components are installed, refer to Annex 3 for configuring theSPOTS domains and to Annex 4 for verifying and adjusting the SPOTS serverproperties.


E200301-01-115-V10.0I-06 97

7.3 Package Installation

The events, warnings and actions detailed below are common to both SW administrationmethods admintool (Section 7.1) and package commands (Section 7.2) and should onlybe executed as part of those procedures. The following sub-sections provide answers tothe questions presented during the installation of each package.

� To accept the default values, (just) press the “<Return>” key.

7.3.1 NIS Users and Groups Requirements

If UNIX users and groups are managed with NIS/NIS+, the SPOTS installation processleaves the creation of the necessary users (spots and rc_user) and groups (pmadmin andpmuser) in the hands of the system administrator. However, some requirements must beensured:

Use the following attributes for user “spots”:• Primary group: pmadmin• Secondary group: dba• Login shell: ksh• Home directory: <base_home_dir>/<user_login>. Typical value for

<base_home_dir> is “/export/home”.

User “rc_user” is only necessary in the machine running SPOTS ApplicationServer and if an interface with Radio Commander shall be established. Use thefollowing attributes:

• Primary group: pmadmin• Login shell: ksh• Home directory: <base_home_dir>/<user_login>. Typical value for

<base_home_dir> is “/export/home”.

7.3.2 SPOTS Naming Server

� Specify the installation (absolute) path of the SPOTS SW or accept the defaultpath “/opt/spots”.� This query is applicable only if no SPOTS package is present in the system.

If any SPOTS package is already installed, the base directory used by thatpackage will be assumed and the installation proceeds to the next step.

� The specified directory must exist before installation. Otherwise, you’ll beasked if you want the installation program to create it.

� Enter the SNS TCP/IP port number or accept the default “19980”.

� The installation program checks for the usage of NIS/NIS+ groups. If noNIS/NIS+ groups are detected then no action is required; otherwise the followingmessage is displayed:NIS/NIS+ groups detected.


98 E200301-01-115-V10.0I-06

Please check if groups ‘pmuser’ and ‘pmadmin’ are defined inNIS/NIS+ before proceedingPress <return> key to continue

� The system administrator performing the installation must guarantee thatthose groups exist before proceeding with installation.

� The installation program checks for the usage of NIS/NIS+ users. If no NIS/NIS+users are detected then no action is required; otherwise the following message isdisplayed:NIS/NIS+ users detected.Please check if user ‘spots’ is defined in NIS/NIS+ beforeproceedingPress <return> key to continue

� If UNIX users and groups are managed with NIS/NIS+, make sure the‘spots’ user is created according to Section 7.3.1, before proceeding withinstallation by pressing the “<return>” key.

� Enter the user’s home directory or accept the default (recommended). The defaultvalue is “/export/home”.� This query is applicable only if no SPOTS package is present in the system.

If any SPOTS package is already installed, the home directory specifiedduring its installation will be assumed and the installation proceeds to thenext step.


� Inspect the output in order to verify that no problems occur during the installation.

� Package SpotsNS installed.


E200301-01-115-V10.0I-06 99

7.3.3 SPOTS Application Server

� Specify the installation (absolute) path of the SPOTS SW or accept the defaultpath “/opt/spots”.

� This query is applicable only if no SPOTS package is present in the system.If any SPOTS package is already installed, the base directory used by thatpackage will be assumed and the installation proceeds to the next step.

� The specified directory must exist before installation. Otherwise, you’ll beasked if you want that the installation program creates it.

� Specify the installation (absolute) path of the SPOTS data or accept the defaultpath “/var/opt/spots”.

� The specified directory shall be used as SPOTS base directory for PM datacollection from NMSs.

When defining the connection settings between SAS and SNS, two situations can occur:

A local SNS installation is detected

� Decide if a connection to the local SNS should be established (defaultbehaviour) or not (answer “n”). Answering “n” has the same effect as nolocal SNS being detected; so, proceed executing the steps associated withthe other alternative.

No local SPOTS Naming Server is detected

� Specify the SNS host name or IP Address.

� Specify the SNS TCP/IP port number (or accept the default “19980”), as itwas previously configured during SNS installation.

� Proceed with the definition of the connection settings, entering the SAS TCP/IPport number or accepting the default “19981”.

� Decide if the SPOTS components for Radio Commander (RC) interface should beinstalled (default) or not. Answer “n” only if a connection between SPOTS and aRC is not intended.

� Decide if the SPOTS components for Operation and Maintenance Centre forMobile-Core NEs (OMC-S) interface should be installed (default) or not. Answer“n” only if a connection between SPOTS and an OMC-S is not intended.

� The installation program checks for the usage of NIS/NIS+ groups. If noNIS/NIS+ groups are detected then no action is required; otherwise the followingmessage is displayed:NIS/NIS+ groups detected.Please check if groups ‘pmuser’ and ‘pmadmin’ are defined inNIS/NIS+ before proceedingPress <return> key to continue


100 E200301-01-115-V10.0I-06


� The installation program checks for the usage of NIS/NIS+ users. If no NIS/NIS+users are detected then no action is required; otherwise follow one of theapproaches:

Modules for RC interface selected for installation

� The following message is displayed:NIS/NIS+ users detected.Please check if users ‘spots’ and ‘rc_user’ are defined inNIS/NIS+ before proceedingPress <return> key to continue

� If UNIX users and groups are managed with NIS/NIS+, make sure the‘spots’ and ‘rc_user’ users are created according to Section 7.3.1,before proceeding with installation by pressing the “<return>” key.

Modules for RC interface not selected for installation

� The following message is displayed:

NIS/NIS+ users detected.Please check if user ‘spots’ is defined in NIS/NIS+ beforeproceedingPress <return> key to continue





� Inspect the output in order to verify that no problems occur during packageinstallation.

� Package SpotsAS installed.


E200301-01-115-V10.0I-06 101

7.3.4 SPOTS CLient (Solaris�� variant)




When defining the connection settings between SCL and SNS, two situations can occur:











102 E200301-01-115-V10.0I-06





� Package SpotsCL installed.


E200301-01-115-V10.0I-06 103

7.3.5 SPOTS Database Server




When defining the connection settings between SDS and SNS, two situations can occur:






� Proceed with the definition of the connection settings, entering the SDS TCP/IPport number or accepting the default “19982”.

� Enter the Oracle SID value for the SPOTS database or accept (recommended) thedefault “spot”.

� If a non-default Oracle SID value is required, the following constraints areapplied: valid input must be a string of letters and/or digits with a length lessthan or equal to 4 defined with no internal, leading or trailing white space.

� Specify the (absolute) path of the Oracle Home directory or accept the default path“/opt/oracle/product/8.1.7”.

� If an unquestionable value is automatically found (by looking for the secondfield of the “oratab” file where the value of the first field equals the OracleSID), no user interaction is required and the installation proceeds to the nextstep.

When configuring Oracle� kernel parameters with SPOTS values, two approaches canbe followed:

Configure automatically (default)

� Answer “y”.

� No additional action required, the installation program will automaticallyedit the “/etc/system” file and append it with the required values. This is the


104 E200301-01-115-V10.0I-06

most common approach and it’s suited for systems with standalone SPOTSenvironment.

Configure manually

� Answer “n” no changes will be made.

� This approach is suited for systems with special configurations. Uponpackage installation, you shall be instructed to configure the “/etc/system”file.









� If you have previously chosen to manually configure the kernel parameters, editthe “/etc/system” file according to your particular system needs and SPOTSrequirements; otherwise no action is required.

� The following lines describe the SPOTS default used parameters. Do not usesmaller values:forceload: sys/semsys


E200301-01-115-V10.0I-06 105

forceload: sys/shmsys

set semsys:seminfo_semmap=350set semsys:seminfo_semmni=350set semsys:seminfo_semmns=550set semsys:seminfo_semmnu=350set semsys:seminfo_semmsl=550set semsys:seminfo_semopm=950set semsys:seminfo_semvmx=32767set semsys:seminfo_semume=350set shmsys:shminfo_shmmax=4294967295set shmsys:shminfo_shmmin=1set shmsys:shminfo_shmmni=512set shmsys:shminfo_shmseg=150

� A message will appear informing you that a system reboot must be performed.Proceed with the installation as it is described in this document — the requiredsystem reboot shall be performed in a few steps.

� Package SpotsDS installed.


106 E200301-01-115-V10.0I-06

7.3.6 SPOTS Data Migration

� The installation path differs according to the existing SPOTS version:• For source V8.1, V9.0 or V9.2 machines is “/opt/migration”.• For target V10 Drop 4 machines is “$SPOTS_DIR/migration”.




� The system administrator performing the installation must guarantee that‘spots’ user exists, according to SPOTS requirements (refer to section7.3), before proceeding with installation by pressing the “<return>” key.





� Package SpotsDM installed.


E200301-01-115-V10.0I-06 107

7.4 Post-Installation Procedures

This section describes the final steps required for the installation of SPOTS SW. Theevents, warnings and actions detailed below are common to both software administra-tion methods admintool (Section 7.1) and package commands (Section 7.2) and shouldonly be executed after those procedures.


� Make sure that the DNS is adequately configured to allow that the host name andfully qualified host name for all SPOTS hosts (including the local host and allother PMS or PMC hosts existing in the SPOTS installation) can be correctlyresolved into their respective IP addresses.If the DNS is not configured to allow this, it is necessary at least to create aliasesfor the host names and fully qualified host names of all SPOTS hosts, in file"/etc/hosts". Edit this file and include an alias for each SPOTS host. Each aliasconsists of a line with the following format:<IP Address> <local or remote hostname> <fully qualified hostname>

For example:141.29.139.12 spotshost spotshost.siemens.com

� Edit the file "/usr/dt/config/Xconfig" and set the property "Dtlogin*authorize" to"false".

� The spots user is automatically created during installation. However, it will belocked until a password is assigned to it.

� Assign a password to the spots user, executing the following shell command:# passwd –r files spots

The command will request a new password for the user and its confirmation.

� The rc_user user is automatically created during SAS installation if the modulesfor Radio Commander interface were installed. However, it will be locked until apassword is assigned to it.

� If SAS was just installed with support for RC interface, assign a password to therc_user user, executing the following shell command:# passwd –r files rc_user

The command will request a new password for the user and its confirmation.

� If you have installed Fault Tolerance with Disk Mirroring and wish that the userspots (and/or other users) also receive the Email disk failure notification, you mustinclude the user spots email address (and/or other users addresses) in the addresslist as described in Section 5.2.1.2.

� Remove the SPOTS CD-ROM from drive.

IMPORTANT:


108 E200301-01-115-V10.0I-06

� Read in advance the following steps after the system reboot, about theSPOTS database installation, to find out more information about this matter.

� In the SDS host, if the database you wish to install next uses the partitioningoption and more than 15 days of PM detailed data are required then youmust perform this additional step before continuing:

� Set the desired value for the NumberDaysInDetailPartition property ofthe “sds.cfg” file (see also Annex 4)

� Shut down the system, entering the shell command:# /etc/shutdown -y -i6 –g0


� If SDS was just installed, execute the following actions in order to install SPOTSdatabase; otherwise, the post-installation procedures are completed.


E200301-01-115-V10.0I-06 109

7.4.1 Installing SPOTS Database


� Verify that SPOTS_DIR environment variable is correctly set. It must point to thebase directory where SPOTS SW is installed. For further information refer toAnnex 2.

� The Installation Type (Tiny, Small, Medium or Large) should be chosen accordingto the information provided by your Siemens representative, who will help youdetermine which configuration best fits your network.

� Execute the following instructions:# cd $SPOTS_DIR/bin# ./installSpotsDB

� Choose the Installation Type from the menu (Tiny, Small, Medium orLarge), entering the corresponding number or accepting the default value(Small), (just) pressing the “<Return>” key:Choose an installation type:

1 Tiny2 Small3 Medium4 Large

Enter selection (default: Small) [?,??,q]: 3

� Tiny configurations are applicable only for “demos” or “field trials”.

� The hardware requirements for each installation type are specified inSection 2.1.

� You will be requested if Partitioning option should be used: accept thedefault value (“y”) or reject the usage of this option, typing “n”.

� The database partitioning is used to remove automatically the PMdetailed data. If activated, 15 days of detailed data are stored bydefault. This period can be changed setting the propertyNumberDaysInDetailPartition of the “sds.cfg” file (refer to Annex 4).The partitioning option usage is summarized in the following table:

Configuration Database PartitioningTiny Not availableSmall Not necessary

Medium PreferableLarge Mandatory

� Inspect the output messages displayed by SPOTS database installation andverify if any error has occurred.


110 E200301-01-115-V10.0I-06

� SPOTS database installed.


E200301-01-115-V10.0I-06 111

7.5 NMS Configuration

The SPOTS system collects periodically the PM files from the Network ManagerSystems (NMS) in the network. The SPOTS V10 Drop 4 version is able to inter-workwith the following NMS types 4:

• SC (Switch Commander)Used to collect traffic data from Siemens GSM and UMTS Core networks.

• OMC-SUsed to collect traffic data from Siemens GSM Core networks.

• RC (Radio Commander)Used to collect traffic data from Siemens GSM radio access networks from BR6.0version onwards, and Siemens UMTS radio access networks.

• OMC-BUsed to collect traffic data from Siemens GSM radio access networks up to BR5.5version.

• @vantage CommanderUsed to collect traffic data from Siemens HLRi Core network elements.

• IPM (IP Manager)Used to collect traffic data from Cisco based GGSN network elements and MobileSmart Proxy (MSP) network elements.

For a complete list of all supported NMS and NE types and versions, consult [1],Section "Overview".

Section 7.5.1 describes the common configuration file used by SPOTS to access thevarious NMS instances. Sections 7.5.2 through 7.5.6 describe the specific configurationissues per each NMS type.

� In the distributed configuration, if more than one SAS is installed and not all theNMSs are to be accessed by a single SAS, you must choose the subset of NMSs tobe accessed by each SAS. The chosen subsets must be disjoint.

The configuration actions described in the following sections must then be appliedseparately for each one of the existing SASs, taking into account, for each SAS,only the NMSs which have been assigned to it.

Configuring a given set of NMSs on a given SAS implies that, for all the trafficdata originated in the mentioned NMSs, the SAS host machine shall perform thedata collection and data processing tasks needed for loading the data into SPOTSDatabase, as well as the Real-Time threshold processing tasks on the same data.

7.5.1 NMS Configuration File

The list of NMS instances inter-working with SPOTS must be provided in the file“$SPOTS_DIR/data/element_managers.cfg”

This file shall contain one line per NMS system, with the following syntax:• for SC, @vantage Commander and IPM: 4 Depending on the type of operator network, and its NE versions, you will need to configure only part of the NMS types.


112 E200301-01-115-V10.0I-06

<nms_name> <nms_type> <nms_host> <dir_offset> <spots_domain>

• for all the others:<nms_name> <nms_type> <nms_host> <spots_domain>

where:<nms_name>

is the name to be assigned to the NMS (further references in SPOTS will usethis name).

<nms_type>is the NMS type. The valid values are: OMC-SSS, SC, RC-BSS, RC-UTRAN,OMC-B, AC or IPM.

<nms_host>is the identification of the NMS host where the PM files can be retrieved.It can assume the form of an IP address or a host name defined in the SAS. Toassociate an IP address to a host name, proceed as follows:

� Logged as root user, edit the file “/etc/hosts”, inserting one line with thefollowing syntax:<ip-address> <hostname>

<dir_offset>contains the pathname of the directory (relative to the FTP home) where thecollected PM files are stored by PDC/HLRi.� This field is applied only to SC, AC and IPM entries. Therefore, it should

not be used for the other NMS types.<spots_domain>

is the SPOTS primary domain that comprises the NEs managed by the concer-ned NMS — for the concept of primary domains, refer to [1]), Section 1.3(Domains).For Single Server configurations, the primary domain assumes the value “/”.

Sample of a “element_managers.cfg” file:RcPor RC-BSS hst_prt2 /NorthRcLis RC-BSS hst_lis3 /LisbonRcFar RC-BSS hst_far1 /SouthUtrPilot RC-UTRAN hst_lis5 /LisbonScFaro SC hst_far2 CFS /SouthScPorto SC hst_prt3 CFS /NorthScLisbon SC hst_lis4 CFS /LisbonAcPilot AC hst_lis6 CFS /LisbonOmcsnet OMC-SSS hst_far3 /SouthOmcbnet OMC-B hst_far7 /SouthIPMPor IPM host_prt quarter /NorthIPMLis IPM host_lis quarter /LisbonIPMLis2 IPM host_lis2 daily /Lisbon

7.5.2 OMC-S Access Specifics


E200301-01-115-V10.0I-06 113

The following steps must be performed, to allow the interoperability between theSPOTS PMS system and the OMC-S platform to where the Upload Scheduler transfersthe TM/PM files.

� Configure the hosts table of the OMC-S system to where the Upload Schedulerapplication (an OMC-S component) transfers the TM/PM files. As root user, editthe “/etc/hosts” file and insert the following line:<pms_ip-address> <pms_hostname>

where:<pms_ip-address><pms_hostname>

are, respectively, the IP address and the host name of the platform whereSAS is installed.

� In the OMC-S system, create (or edit) a “.rhosts” file under the omc user homedirectory, with the following line:<pms_id> spots

where:<pms_id>

is the identification of the platform where SAS is installed.It can be its IP address or the hostname. If a hostname is used, it mustcorrespond to the name defined in the previous step, in file “/etc/hosts”.

� The directory path pointed to by AP_TR_OMP_DIR (environment variable that isdefined in the file “/etc/oms/omsenviron”, in the OMC-S system to where theUpload Scheduler transfers the TM/PM files) must be copied to an equivalentenvironment variable in SPOTS PMS.

� Typically the directory path in question is /oms_var/self/ap_tr_omp_dir.

� To check this, launch a command tool from an OMT and issue the followingcommand, which should yield the correct path:# echo $AP_TR_OMP_DIR

� Once you are sure of the directory path pointed to by the AP_TR_OMP_DIRof the OMC-S system, edit the file “/etc/spotsenv” as spots user in the SAShost and insert (or edit) the following lines:AP_TR_OMP_DIR=<AP_TR_OMP_DIR of the OMC-S system>export AP_TR_OMP_DIR

� Add one line per OMC-S in the NMS configuration file, as described in Section7.5.1.

7.5.3 SC Access Specifics


114 E200301-01-115-V10.0I-06

The PDC application (an SC component) is used to transfer PM data from the NEs andprovide those data as PM files located on its repository — refer to the appropriate PDCUser Manual ([5], [6]).

SPOTS retrieves such files from the SC Common File Store (CFS) via anonymousFTP.

To allow the interoperability between SAS and the SC File Server to where PDC trans-fers the PM files, only the generic configuration step in Section 7.5.1 is required (addone line per SC in the NMS configuration file).

� Make sure that the environment variables associated with data collection from theSC are properly configured. Check variables GET_SC_TIME_OUT1 / 2 / 3 andMAX_FNF_FAILURE (refer to Annex 2).

� It should be guaranteed that the FTP access to the CFS is properlyconfigured, enabling the anonymous option for access from the SAS hostmachine(s) (restricting anonymous access to the SAS host(s) is the safestapproach).

It must also be ensured that the specified value for <dir_offset> (in thecorresponding entry of the file “element_managers.cfg”) is equal to the VirtualDirectory that was created in the SC File Server for the FTP access to the CFS(refer to the FTP configuration in the Windows� NT environment: InternetService Manager tool, option Default FTP Site). SPOTS only requires read rightson the SC File Server directories.

7.5.4 @vantage Commander Access Specifics

HLRi Export PM data files shall be collected from the @vantage Commander throughthe "HLRi Export PM Data interface". SPOTS retrieves such files via anonymous FTP.

To allow the interoperability between SAS and @vantage Commander, only the genericconfiguration step in Section 7.5.1 is required (add one line per @Vantage Commanderin the NMS configuration file).

� Make sure that the environment variables associated with data collection from the@Vantage Commander are properly configured. Check variablesGET_AC_TIME_OUT1 / 2 (refer to Annex 2).

� It should be guaranteed that the FTP access is properly configured on the@Vantage Commander, enabling the anonymous option.

It must also be ensured that the specified value for <dir_offset> (in thecorresponding entry of the file “element_managers.cfg”) matches the directorywhere HLRi Export PM data files are placed in the @vantage Commander.


E200301-01-115-V10.0I-06 115

7.5.5 OMC-B Access Specifics

To enable SAS to access the OMC-B host(s), the following steps must be performed:

� On the OMC-B system, create (or edit) a “.rhosts” file under the omc user homedirectory, with the following line:<pms_hostname> spots

where:<pms_hostname>

is the identification of the platform where SAS is installed.It can be its IP address or the hostname. If a hostname is used, it must bedefined in the file “/etc/hosts”.

� Add one line per OMC-B in the NMS configuration file, as described in Section7.5.1.

7.5.6 RC Access Specifics

The RC OLTFtp service is used to transfer the PM files from the GERAN and/orUTRAN NEs.The following steps must be performed to allow the interoperability between the SASand the RCs:

� Enable the FTP access to the RC system, creating an RC (OLT) user (refer to theolt_userManagement command in the RC execution environment) for rcftp accessfrom the platform where SAS is installed.

RCs will transfer PM files into SPOTS using a specific FTP account. Define the FTPincoming account in SAS, executing the following steps:


� Edit the file “$SPOTS_DIR/data/oltaccess.cfg” and update the first line asfollows:rc_user <rc_user_pwd>

where:rc_user

is the fixed name of a SPOTS user that was automatically createdduring SAS installation.

<rc_user_pwd>is the password that was assigned to rc_user, using the passwdcommand, after SAS installation (refer to Section 7.4).


116 E200301-01-115-V10.0I-06

� After the first line, insert one line per RC with the following syntax:<rc_name> <spots_ip-address> <rc_olt_user> <rc_olt_pwd>

where:<rc_name>

is the SPOTS alias for the name of the RC host, inserted in the file“element_managers.cfg” (7.5.1).

<spots_ip-address>is the IP address of the platform where SAS is installed (used by theRC to perform ftp access) 5.

<rc_olt_user>is the ftp username (created in the previous step), used by SAS toaccess the RC host.

<rc_olt_pwd>is the ftp password for the above mentioned user.

� Add one line per RC in the NMS configuration file, as described in Section 7.5.1.

� Make sure that the environment variables associated with data collection from theRC are properly configured. Check variables GET_RC_TIME_OUT andRC_VERSION (refer to Annex 2).

To enable SAS to access the RC Symbolic Names information, the following steps mustbe performed:

� Give access from the RC database: On each interfaced RC, make sure thatthere is a database service available for SQL access, done remotely viaTCP/IP, and that there is a database user with the role TPToolRole granted.It will be used by SAS to perform read-only accesses to the database view“cfg_symbolicnamere_view” and table “cfg_symnameversion”.

On the SAS, configure the access to the RC database:

� As spots user, create the “$SPOTS_DIR/data/gsnl.dat” file and insert a firstline with the following fixed string:RC

� After the first line, insert one line per RC with the following syntax:<rc_name> <rc_oracle_serv_name> <rc_db_User> <rc_db_pwd>

where:<rc_name>

is the SPOTS alias for the name of the RC host, inserted in the file“element_managers.cfg” (7.5.1).

<rc_oracle_serv_name>

5 Note that different RC instances may access SPOTS via different IP addresses. This is the reason why this parameter isconfigured individually per RC.


E200301-01-115-V10.0I-06 117

is the Oracle� Service name (to be defined in the next step) for theSAS access to the RC database.

<rc_db_user>is the RC database user with the role TPToolRole granted to accessthe Symbolic Names information.

<rc_db_pwd>is the password for the above-mentioned user.

� As root user, edit the file “tnsnames.ora”, stored in the subdirectory“network/spots_ora_admin” of the “ORACLE_HOME” directory.Per RC, append the following to the contents of the file:<RC Oracle Serv name> =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS =

(PROTOCOL = TCP)

(Host = <RC_DB_IP_addr>)

(Port = <RC_DB_port_no>)

)

)

(CONNECT_DATA = (SID = <RC_DB_Oracle_SID>)

)

)

where:<RC Oracle Serv name >

is the Oracle� Service name for the SAS access to the RCdatabase.

<RC_DB_IP_addr>is the IP address of the host where the RC database is installed.

<RC_DB_port_no>

is the port number for using the Oracle� service defined above.<RC_DB_Oracle_SID>

is the “service id” of the Oracle� service defined above.

7.5.7 IPM Access Specifics

The following steps must be performed, to allow the interoperability between theSPOTS SAS system and the IP Manager platforms from where the Cisco based GGSNand/or MSP, files will be collected:


118 E200301-01-115-V10.0I-06

Enable the FTP access to the IPM system, creating an user for ftp access from theplatform where SAS is installed.

� As spots user, create the file “$SPOTS_DIR/data/ipmaccess.cfg” and insertone line per <ipm_name> inserted on “element_managers.cfg” file, with thefollowing syntax:

<ipm_name> <spots_ip-address> <user> <pwd>

Where:<ipm_name>

is the SPOTS alias for the name of the IPM host, inserted in the file“element_managers.cfg” (7.5.1).

<spots_ip-address>is the IP address of the IPM machine.

<user>is the ftp username, used by SAS to access the IPM host.

<pwd>is the ftp password for the above mentioned user.

Sample of a “ipmaccess.cfg” file:IPMPor host_prt spots spots01IPMLis host_lis2 spots spots2003IPMLis2 host_lis2 spots spots2003

To associate the file names with file type, the following steps must be performed:

� As spots user, create the “$SPOTS_DIR/data/ipm_NEType.dat”, and insert oneline for each NE name with the following syntax:

<ne_name> <ne_type> where :

<ne_name>is the ipm NE name.

<ne_type>could be GGSN or MSP.

Sample of a “ipm_NEType.dat” file:MSP.NODE0 MSPMSP.NODE1 MSPGGSN.NODE0 GGSNGGSN.NODE1 GGSN

7.5.8 IPM Converter Specifics


E200301-01-115-V10.0I-06 119

The data files collected via the IPManager must be processed by two Spots FileConverters - C_GGSNFileConverter and MSPFileConverter.There is a configuration file per Converter that must be configured manually.

1 - To configure the C_GGSNFileConverter: the following file must be edited:$SPOTS_DIR/converters/c_ggsnConverter/cfg/common/properties.cfg and the entries INPUT_DIR e OUTPUT_DIR must be assigned the following values:

INPUT_DIR=$SPOTS_DATA/traffic_data/ggsn/input OUTPUT_DIR=$SPOTS_DATA/traffic_data/ggsn

2 - To configure the MSPFileConverter: the following file must be edited:$SPOTS_DIR/converters/mspConverter/cfg/common/properties.cfg and the entries INPUT_DIR e OUTPUT_DIR must be assigned the following values:

INPUT_DIR=$SPOTS_DATA/traffic_data/msp/input OUTPUT_DIR=$SPOTS_DATA/traffic_data/msp


120 E200301-01-115-V10.0I-06

7.6 SPOTS Licensing Software

The SPOTS Licensing Software is a mandatory component of the SPOTS system and itcontrols the access to SPOTS and its functionality.

The following functional group must be licensed as part of SPOTS V10 Drop 4:• Spots Login.

The following functional groups are optional, providing the access to the environmentfor defining user specific reports:

• Reports Editor.

• Real-Time (mandatory in case the SNMP Alarm Agent is required).

• SNMP Alarm Agent.

(Note that Real-time and SNMP Alarm Agent installation are covered in [3])

The “license.dat” file, containing the licensed features, will be provided by Siemens andinstalled in the PMS system (SAS), acting as the License Server; all the other SPOTSinstallations must be configured to access it:

LicenseServer

SAS

PMS

SAS

Other PMS(s)

7.6.1 Configuring SPOTS licenses

SPOTS PMS License Server



� Place the “license.dat” file, supplied by Siemens, under the path:“$SPOTS_DIR/data”

� Start the License Manager daemon:$ /etc/init.d/initlmd start

� In the previous command the “start” argument is optional i.e., can beomitted with the same results on behalf of simplicity.

�� The License daemon should never be killed (i.e., stopped via the UNIX command“kill”). However, if for some reason, this process must be stopped, execute thecommand:


E200301-01-115-V10.0I-06 121

$ /etc/init.d/initlmd stop

Other SPOTS PMS(s)

� On each SAS installation (other than the License Server), create a license filenamed “license.dat”, under “$SPOTS_DIR/data”, with the following (2) lines:SERVER <licserver_hostname> <licserver_hostid> <port_number>USE_SERVER

where:<licserver_hostname>

is the name of the PMS acting as License Server.<licserver_hostid>

is the identifier of the host where the License Server is installed (it can beobtained running the UNIX command “hostid”).

<port_number>is the TCP/IP port used by the License Server (it is defined in the file“license.dat”, stored on the License Server).

� You may copy the first line from the file “license.dat” installed on theLicense Server.

7.6.2 Updating the SPOTS licenses

The procedure for updating SPOTS licenses is similar to the procedure for configuringthem, but only for the SPOTS PMS License Server part (refer to Section 7.6.1).

�� Updating SPOTS licenses does not require stopping the License ManagerDaemon.


122 E200301-01-115-V10.0I-06

8 Installing SPOTS-PMC (Windows�� environment)

To install the SCL in a Windows� environment, insert the supplied CD-ROM in thesystem’s CD unit.

� For Windows� 2000 or XP, you must be logged on as an administrator or amember of the Administrators group in order to perform this installation.

� There is no facility to upgrade the SPOTS-PMC product. It is mandatory to de-install the older version and install the current one. To de-install the previousSPOTS-PMC version, refer to Chapter 10.

During the installation process, it is assumed that the CD-ROM drive letter is “D”. Ifthis is not the case, use the corresponding letter instead.

The installation process comprises several steps, which are described in the remainderof this chapter.

8.1 Installation sequence

The SPOTS-PMC software for Windows� does not make use of the auto-run facility.To start the installation process execute the following steps:

� Click on the button, located in the lower left corner of your screen.

� Select Run … option.

� Execute the SPOTS-PMC set-up, typing the following command and then press Ok“D:\Setup”

� The SCL splash screen is displayed for a few seconds. Then, the Welcome windowis presented over the SPOTS blue background.

� Close all other applications before proceeding.

� In the Welcome window, click on the Next > button to proceed, or on theCancel button to abort the installation process.

� The EULA – End-User License Agreement window is presented.

� Read carefully all the supplied information.

� Click on the Yes button if you accept all the terms contained in the EULA.Otherwise, terminate the installation, clicking on the No button.

� The < Back button allows returning to the previous window. It is available inthe following windows.


E200301-01-115-V10.0I-06 123

� If the user performing the installation has administrator’s privileges, it shall bequestioned about the Installation Type. Two types of installation are available:Global all the users have SCL available from the SPOTS-PMC folder in the

Windows� Start menu;

Personal only the user who installed SCL has it available from the SPOTS-PMC folder in the Windows� Start menu.

� For installers without administrator’s privileges (applied only to Windows�NT — note that, for Windows� 2000 and XP, these privileges are required),SCL is installed as Personal.

� Choose the location where SCL shall be installed.If the selected location does not exist, a confirmation window is displayed, letSetup create the specified location.

� It is recommended to install SCL in a directory called “SPOTS-PMC” on theroot of the boot drive. However, a different destination may be defined.Almost every drive/directory is allowed, except installing on either aremovable drive or a network drive.

� Avoid using space characters in directory names

� Select the Program Folder after reading the note below:

� During SCL installation, a folder is added to the Start>>Programs menu,containing an icon to start SCL and another to start SPOTS Reports Editor.The folder suggested name is SPOTS-PMC, but the icons may also beadded to an existing folder, for which the list of existing folders is presented.

� Provide the settings for connecting to SNS:

� Fill in the Hostname, which can be up to 15 characters, or the IP Addressof the platform where the SNS is installed.

� Fill in the Naming Server TCP/IP Port number. To reset the TCP/IP Port toits default value (“19980”) press the Set default port button.

� The Start button is only enabled when all required data fields are correctlyspecified.

� This is the last user selection prior to file copying. Press the Start button.

� SCL SW is copied to your system.


124 E200301-01-115-V10.0I-06

� When Setup is completed, click on the Finish button to terminate SPOTS-PMCinstallation.

� SCL installation is completed. To start using SCL, select SPOTS PerformanceManagement Client from the folder selected before (during Program Folderselection), for instance:


E200301-01-115-V10.0I-06 125

8.2 Troubleshooting

When SCL cannot establish a session with its corresponding SN, a window is presentedwith the following message:

Unable to contact naming server.Fatal.

In such a situation, it is required to execute the tool SpotsPing command from the binsubdirectory of the SCL installation. To do so:

� Open a DOS command prompt window

� Admitting that SPOTS Client was installed on c:\SPOTS-PMC, type the followingcommand:cd /d c:\SPOTS-PMC\bin

� Run the SpotsPing tool, executing the command:SpotsPing NS <address> [<TCP/IP port>]

where:<address>

is the SNS address, its hostname or the TCP/IP address.<TCP/IP port>

is the SNS TCP/IP port number (optional if SNS has been configuredwith the default value “19980”).

If the SNS is detected, the following message is presented:

Server detected!!!

Otherwise (SNS is not detected),

Unable to contact theserver.

� Close the DOS command window with the Exit command.


126 E200301-01-115-V10.0I-06

8.3 SPOTS License checking

During login, SPOTS-PMC establishes a connection to a user-defined SAS, for which avalid license must exist.

If the license does not exist or is invalid, a message is presented:

License not available.

In such cases, it is mandatory to obtain a license for the corresponding SAS.

To obtain further information concerning licensing, refer to Section 7.6.


E200301-01-115-V10.0I-06 127

9 Uninstalling SPOTS software (Solaris�� environment)

This section is valid for un-installing either:i) Only the Long-Term SPOTS part (possible only if Real-Time is not installed);ii) Both Long-Term and Real-Time SPOTS.

� If it is desired to un-install the Real-Time part, refer to [3], Sections “9-De-installing SPOTS Real-Time Software (Solaris� environment)" and “10-De-installing SPOTS RT Agency (Windows� environment)”.

To remove the SPOTS SW, execute the following actions as described in the nextsections:

1. Stop SPOTS applications.2. Uninstall SPOTS database.3. Remove all SPOTS packages.

9.1 Stopping SPOTS applications

In case Real-Time is installed, stop first all the Real-Time applications, jobs anddaemons - refer to [3], Section "Stopping SPOTS RT Applications".

Ensure that SPOTS Long-Term applications and all the associated jobs and daemons arestopped by performing the steps described in Section 3.3.4.

9.2 De-installing SPOTS database

Run this procedure locally in the system(s) where the SDS(s) is (are) installed.



� To uninstall SPOTS database execute the following command:# $SPOTS_DIR/bin/uninstallDB


� SPOTS Database de-installed.


128 E200301-01-115-V10.0I-06

9.3 Removing SPOTS Packages

This action, which consists of removing the SPOTS packages installed in each host, canbe accomplished via admintool command (refer to the following section) or via packagecommands (refer to Section 9.3.2).

� SPOTS SW comprises the following packages: SpotsCL, SpotsNS, SpotsDS andSpotsAS (Long-Term); SpotsRTA, SpotsRTC, SpotsRTS and SpotsSAA (Real-Time). However, in a distributed environment, packages can be spread overmultiple hosts; consequently, the procedure described in the next sections shall berepeated for each system hosting SPOTS components.

9.3.1 Removing SPOTS Packages with admintool


� Start admintool, verify that DISPLAY environment variable is set:# admintool &

� Choose “Software” from the Admintool “Browse” menu.

� The Admintool: Software window appears, listing the software currently installedin the system.

� Select all SPOTS components, pressing “Ctrl” key and clicking with the mousepointer in the corresponding entries. If all SPOTS packages are installed, thefollowing must be selected:“SPOTS CLient (SpotsCL)”“SPOTS Naming Server (SpotsNS)”“SPOTS Database Server (SpotsDS)”“SPOTS Application Server (SpotsAS)”“SPOTS RT Agency (SpotsRTA)”“SPOTS RT Client (SpotsRTC)”“SPOTS RT Server (SpotsRTS)”“SPOTS SNMP Alarm Agent (SpotsSAA)”

� Choose “Delete” from the “Edit” menu.

� Confirm the deletion of every package selected in the previous step, clicking onthe Delete button.

� A warning message like the one depicted in Figure 3 may appear.If so, ignore it pressing the “Continue” button. To disable it permanently, clickon the “Check here to disable this message” checkbox before pressingthe “Continue” button.

� A window appears prompting for information about the de-installation:



E200301-01-115-V10.0I-06 129

� Inspect the output in order to verify that all package removals are successful.

� Return to the Admintool: Software window, pressing the <Return> key.

� Exit admintool selecting “Exit” from the “File” menu.

� If the Spots RT packages are also being removed, please check the SPOTS RTInstall Guide [3].

� SPOTS SW uninstalled.

9.3.2 Removing SPOTS Packages with Package Commands


� Identify the installed SPOTS packages, executing the following shell command:# pkginfo | grep Spots

� According to the installed packages in this host, the output of the command can bemore or less extensive. If all SPOTS packages are installed, then the followingoutput is given:application SpotsAS SPOTS Application Serverapplication SpotsCL SPOTS CLientapplication SpotsDS SPOTS Database Serverapplication SpotsNS SPOTS Naming Serverapplication SpotsRTA SPOTS RT Agencyapplication SpotsRTC SPOTS RT Clientapplication SpotsRTS SPOTS RT Serverapplication SpotsSAA SPOTS SNMP Alarm Agent

� Remove the package(s) identified in the previous step, listing it(them) in thepkgrm command. If all packages are installed, the command will be:# /usr/sbin/pkgrm SpotsRTA SpotsRTC SpotsRTS SpotsSAASpotsCL SpotsNS SpotsAS SpotsDS

� Always remove the Real Time packages before the Long Term packages.


� Inspect the output in order to verify that all package removals are successful.

� If the Spots RT packages are also being removed, please check the SPOTS RTInstall Guide [3].

� SPOTS V10 Drop 4 software de-installed.


130 E200301-01-115-V10.0I-06

10 De-installing SPOTS-PMC (Windows�� environment)

The de-install process is common to almost every product designed for MicrosoftWindows� environment. To de-install SCL, the user must have at least the sameprivileges as the installer. Follow the instructions given below:

� Click on the button, located in the lower left corner of your screen.

� Select Settings>>Control Panel option.

� Double-click on the Add/Remove Programs icon.

� A window is displayed, containing a list of all products installed whom de-installation process has been tailored for the Microsoft Windows� environment.

� Select the SPOTS-PMC V10.0M product and click on the Add/Remove … orChange/Remove button according to the Microsoft Windows� system (NT or2000 / XP) that you’re using.

� A confirmation window is displayed, to avoid an accidental removal of theproduct.

� Confirm SPOTS-PMC removal.

� During the de-installation of SCL, a window may be presented, requesting the userpermission to remove an existing file:

� “Win32Printer.dll” is a shared file installed with that SPOTS-PMC.However it might be used by other applications. In such an event, otherapplications should have registered themselves as users of that file. Some-times this does not occur, thus every time a shared file is about to be remo-ved a similar message is presented.


E200301-01-115-V10.0I-06 131

� In case of doubt, do not remove the file. Its presence is harmless to the sys-tem, just occupying disk space. Otherwise click on the Yes button to allowremoval.

� At the end a final window is presented where it is only necessary to click on theFinish button.

� SPOTS-PMC software removed. Reference to the SPOTS-PMC software is nolonger presented since the list of currently installed products was updated.

10.1 Files not removed during de-installation

Each SCL user may configure the application according to his/her personal preferences,which are stored in several configuration files, in each user profile directory, by default:

“C:\WINNT\Profiles\<User Login Name>” for Windows� NT“C:\Documents and Settings\<User Login Name>” for Windows� 2000 or XP

The following files may exist:• SPOTS_PREF.INI• rephelp.cfg• rephelp.chk• report_editor.ini• spots_key.tmp

These files are not removed during SCL de-installation, thus they shall be manuallyremoved.

If a user wants to restore all his/her original settings, it is only required to delete theseuser-dependent files while SCL remains installed.


132 E200301-01-115-V10.0I-06

11 Abbreviations

APS Application Program System.BSS Base Station Subsystem.BTS Base Transceiver Station.BTSM BTS site Management.CCNC Common Channel Network Control.CDE Common Desktop Environment.CFS Common File Store.CGI Cell Global Identity.CI Cell Identity (CGI’s component).EDGE Enhanced Data rates for GSM Evolution.EM Element Manager (SC, OMC-S, RC, OMC-B or @vantage

Commander).EN Equivalent Node.GERAN GSM and EDGE Radio Access Network.GSM Global System for Mobile communications.HLR Home Location Register.HLRi HLR-Innovation.LAC Location Area Code (CGI’s component).MSC Mobile Services Switching Centre.NE Network Element.NMS Network Management System, also known as “EM”.

O&M Operation and Maintenance.OMC Operation and Maintenance Centre.OMC-B Operation and Maintenance Centre for Siemens SBS NEs.OMC-S Operation and Maintenance Centre for Mobile-Core NEs.OMS Operation and Maintenance System.PDC Performance Data Collector.PM Performance Management.PMC Performance Management – Client Configuration.PMS Performance Management – Server Configuration.RAID Redundant Array of Independent DisksRC Radio Commander.SAS SPOTS Application Server.SBS Siemens Base Station.SC Switch Commander.SCL SPOTS Client application.SDS SPOTS Database Server.SNS SPOTS Naming Server.SOC Set of Counters.SOO Set of Objects.SOV Set of Variables.SPOTS Support for Planning, Operation&Maintenance and Traffic Analysis.SSNC Signalling System Network Control.SW Software.UMTS Universal Mobile Telecommunication System.


E200301-01-115-V10.0I-06 133

UTRAN UMTS Terrestrial Radio Access Network.


134 E200301-01-115-V10.0I-06

12 References

[1] User ManualSPOTS V10 Drop 4(SSA Doc E200301-01-114-V10.0I-*)

[2] Release NotesSPOTS V10.0.x(SSA Doc E200301-01-121-V10.0I-*)

[3] Real-Time Installation GuideSPOTS V10 Drop 4(SSA Doc E200301-01-215-V10.0I-**)

[4] Installation and User ManualSPOTS-BAR V1.0(SSA Doc E200301-01-614-V10.0I-**)

[5] User ManualPerformance Data CollectorUMN:PDC V2.2(Siemens Doc A50016-D522-B100-*-7620)

[6] User ManualPerformance Data Collector for SCR10.2(Siemens Doc A50016-D9102-B100-*-7620)

[7] User Manual - Real TimeSPOTS V10 Drop 4(SSA Doc E200301-01-514-V10.0I-*)


E200301-01-115-V10.0I-06 135

Annex 1 – Disk Partitioning - RAID extensions


136 E200301-01-115-V10.0I-06


E200301-01-115-V10.0I-06 137

Disk Partitioning – RAID Extensions

On any configuration with the Medium DB size (HW configurations with 8 disks), andalso on a Large DB configuration the Sun Fire V880 with 12 disks HW option, it isnecessary to configure the mirroring disk partitions. This Annex describes the requiredadditional partitions, to complement those listed on Section 2.3. None of thesepartitions are to be extended with respect to the sizes indicated below.

�� The Installation Type (Tiny, Small, Medium or Large) should be chosen accordingto the information provided by your Siemens representative, who will help youdetermine which configuration best fits your network.

Partition Medium LargeSize Disk Size Disk

/root_mirror = / 1 = / 6

/swap_mirror = swap 1 = swap 6

/opt_mirror = /opt 1 = /opt 6

/home_mirror = /export/home 1 = /export/home6

/spots_db1_mirror - - = /spots_db1 7/spots_db2_mirror - - = /spots_db2 8/spots_db3_mirror - - = /spots_db3 8/spots_db4_mirror - - = /spots_db4 9/spots_db5_mirror - - = /spots_db5 10/spots_db6_mirror - - = /spots_db6 11/spots_arch_mirror - - = /spots_arch 6

/var_opt_mirror = /var/opt 1 = /var/opt 6

/replica1 1 GB 0 1GB 0/replica2 10 MB 0 1GB 1/replica3 1 GB 1 1GB 2/replica4 10 MB 1 1GB 3/replica5 - - 1GB 4/replica6 - - 1GB 5/replica7 - - 1GB 6/replica8 - - 1GB 7/replica9 - - 1GB 8/replica10 - - 1GB 9/replica11 - - 1GB 10/replica12 - - 1GB 11

IMPORTANT NOTES:


138 E200301-01-115-V10.0I-06

• “=” Means that the partition size must be at least the size of partition mentionedafter the symbol.

• On the Medium configuration, Disk0 and Disk1 correspond to the internaldrives.

• The mount points which contain the word “mirror” must have the same numberof cylinders as the corresponding mount points without the word “mirror”, if thedisks are of same model and geometry. If the disks are not of the same modeland geometry then the mount points which contain the word “mirror” must have2 Megabytes more than the corresponding mount points without the word“mirror”.

• The partitions for DiskSuite� state database replicas (the /replica partitions)must be in the beginning of the disk, i.e. containing track 0. Usually definingthese partitions as slice 0 is sufficient. One exception is for swap partition thatcan contain track 0 due to OS installation requirement. Another exception is forMedium configuration that has 2 replicas per internal disk. In this case choose/replica1 as slice 0 and /replica2 as slice 7, on one disk, and choose /replica3 asslice 0 and /replica4 as slice 7 on the other disk.

• If each pair of disks involved in a mirror is of different geometry, start the diskpartitioning by the one with less space (you can know the space of each disk inthe OS-installation partitioning window). The partitions on the disk with morespace must have 3 MB more than the respective ones in the disk with less space,except for the replica partitions (partitions that contain the word “replica”). If thedisk with more space has just one replica partition, than the replica partitionmust contain the remaining disk space (instead of 1GB). If the disk with morespace has two replica partitions, than the replica partition with 1GB must containthe remaining disk space (instead of 1GB)

• The OS-installer partitioning window can show lack of precision in translationbetween Mega Bytes and Cylinders. For each pair of disks making up a mirror, ifyou notice this inconsistency, be sure that the mirrored partitions have the samenumber of cylinders.


E200301-01-115-V10.0I-06 139

Annex 2 – UNIX environment variables


140 E200301-01-115-V10.0I-06


E200301-01-115-V10.0I-06 141

UNIX environment variables

LD_LIBRARY_PATHPath to ORACLE� and SPOTS libraries.

PATHPath for file search.

SPOTS_DIRSPOTS base installation directory (default value: /opt/spots).

SPOTS_DATASPOTS base directory for PM data collection from NMSs (default value: /var/opt/spots).

TMPSPOTS Directory for temporary files (default value: /tmp).

ORACLE_HOMEOracle� home directory (default value: /opt/oracle/product/8.1.7).

ORACLE_SIDOracle� SID for SPOTS database, valid input must be a string of letters and/or digits with a length lessthan or equal to 4 (default value: spot).

TNS_ADMINPath to Oracle� SQL*Net configuration files (value: $ORACLE_HOME/network/spots_ora_admin).

DC_SC_TRACETrace flag for data collection from SC.

SBS_TRACETrace flag for generating the BSCs’ configuration data.

DC_TR_TRACETrace flag for data collection from OMC-S.

DC_RC_TRACETrace flag for data collection from RC.

DC_AC_TRACETrace flag for data collection from @Vantage Commander.

AP_TR_OMP_DIRDirectory for transferred TM/PM files (OMC-S File Server).

DC_ALTERNATE_DIRDirectory for TM/PM files transferred from the OMC-S (collected from SSS “Classic” NEs), to beaccessed by an external Application (other than SPOTS). By default, no alternate directory path is setany value defined for this variable will be interpreted as a directory path.

DC_TR_BASEBase directory for data collection from the EMs: configuration files and unloadable TM/PM files(cannot be imported into the Database).

GET_SC_TIME_OUT1Limit, in seconds, to wait for a reply from the SC to an ftp mget request for a set of “file name files”.Default value: 120 (also applies if the variable is undefined). If this value is reached the mget isinterrupted and the file name files are retrieved one by one, using ftp get operations (this retrieval iscontrolled by variables “GET_SC_TIME_OUT2” and “MAX_FNF_FAILURE”, see next). If thevalue is 0, no limit exists (i.e. “wait forever”).

GET_SC_TIME_OUT2Limit, in seconds, to wait for a reply from the SC to an ftp get request for a single “file name file”.Default value: 20 (also applies if the variable is undefined). If this value is reached the get isinterrupted and the attempt to retrieve this file name file is abandoned (i.e. “go to the next file namefile”). If the value is 0, no limit exists (i.e. “wait forever”).

GET_SC_TIME_OUT3Limit, in seconds, to wait for a reply from the SC to an ftp “get” request to retrieve a single PM filefrom the SC file store. Default value: 300 (also applies if the variable is undefined). If this value is


142 E200301-01-115-V10.0I-06

reached the get is interrupted and the attempt to retrieve the PM file is abandoned. If the value is “0”,no limit exists (i.e. “wait forever”).

MAX_FNF_FAILUREMaximum number of admissible failures in individual “file name file” retrievals from a SC. If, in agiven execution of the collection procedure, the transfer fails for N “file name files” (whereN>MAX_FNF_FAILURE), the file name file transfer is aborted and there is no ensuing attempt totransfer the PM files indicated by the retrieved “file name files”. Default value: 1 (also applies if thevariable is undefined).Note: transfer of PM files based on an incomplete file name file list may cause duplicate PM fileretrievals in subsequent executions of the collection procedure.

GET_AC_TIME_OUT1Limit, in seconds, to wait for a reply from the @Vantage Commander to an ftp ls request for a set offile names. Default value: 300 (also applies if the variable is undefined). If this value is reached the lsis interrupted and the file retrieval fails. If the value is “0”, no limit exists (i.e. “wait forever”).

GET_AC_TIME_OUT2Limit, in seconds, to wait for a reply from the @Vantage Commander to an ftp get request to retrieve asingle PM file from the @Vantage Commander file store. Default value: 300 (also applies if thevariable is undefined). If this value is reached the get is interrupted and the attempt to retrieve the PMfile is abandoned. If the value is “0”, no limit exists (i.e. “wait forever”).

GET_RC_TIME_OUTLimit, in seconds, to wait for a reply from the RC to an ftp request (either for a set of PM files or a listof file names). Default value: 1800 (also applies if the variable is undefined). If the value is 0, no limitis defined (i.e. “wait forever”).

RC_VERSIONRC’s software version to which SPOTS is connected. As the interface changes between BR6.01 andBR6.02, valid values are: BR_601 or BR_602. If the variable is undefined or is defined with an invalidvalue, the default value is used (default value: BR_602).

USER_OMC_BUser identification for the access to the OMC-B environment.

RC_USER_HOMEHome directory of the user for the access to the RC environment (default value: /export/home/rc_user).

USER_OMC_SUser identification for the access to the OMC-S Communication Server.

All variables are defined, after SPOTS installation, in the file “/etc/spotsenv”. Todisplay the value of any of these environment variables:

� Execute the following commands:$ . /etc/spotsenv$ echo $<environment_variable_name>

� The value of the environment variable is displayed.

�� Users should not change the value of environment variables.This is not applied to the following “modifiable” variables:

• GET_SC_TIME_OUT1/2/3 and MAX_FNF_FAILURE• GET_RC_TIME_OUT• DC_ALTERNATE_DIR• RC_VERSION


E200301-01-115-V10.0I-06 143

To change the value of these environment variables, follow this procedure:

� Before changing these environment variables, the SPOTS application mustbe stopped; the new values are available after re-starting SPOTS.


� Edit the file “/etc/spotsenv”.

� If already defined, locate the variable definition and replace the associatedvalue by the new one. For the DC_ALTERNATE_DIR variable, if not yetdefined, create a new variable definition copying an existing definition forany other variable and then changing the variable name and value.

� Logout, in order to changes in your shell environment to take effect.

� The environment variable’s new value is set.


E200301-01-115-V10.0I-06 145

Annex 3 – Domains’ Configuration


146 E200301-01-115-V10.0I-06


E200301-01-115-V10.0I-06 147

Domains’ Configuration

�� This annex refers to concepts that are explained in the SPOTS User Manual ([1]),Section 1.3 (Domains) — read this section before proceeding.

The configuration of domains is performed on a cluster basis. The cluster’s configu-ration, stored in the file “$SPOTS_DIR/domain.cfg”, is associated with the related SAS.

The syntax of the file “domain.cfg" is the following in EBNF notation:

<domain_def> ::= domain <name> <database_server_id> <subdomains>;<name> ::= string<database_server_id> ::= string | <void><subdomains> ::= {<domain_def> <other_subdomains>} | <void><other_subdomains> ::= <domain_def> | <void><void> ::=

�� The configuration of domains must be done “off-line”, this means that the SASand SDS(s) servers of the cluster must be shut down before any changes are doneto the file “domain.cfg”.SNS does not need to be shut down during this process.

Below, some examples of “domain.cfg” files are presented.

Example 1:

domain Root;

Example 2:

domain Root SDS_1;

Example 3:

domain Root { domain North SDS_1;};


148 E200301-01-115-V10.0I-06

Example 4:

Domain Portugal { domain North SDS_1; domain South { domain Lisbon SDS_2; domain Alfragide SDS_3 { domain Alfragide_North; domain Algragide_South; }; };};

�� It must be noticed that:

• There can only be one top domain per “domain.cfg” file.The following example is wrong:

domain Portugal SDS_1;domain Spain SDS_2;

• If the top domain is called “Root”, the cluster will be associated dynamicallywith the domains of the remaining clusters.

• There can only exist one cluster with a top domain called “Root”.

• The sub-domains of a top domain called “Root” cannot be called “Root”.

• Domains cannot be called “domain”.

• The names of SDSs must be the same as the names given to the property“ServerID” in the SDS’s configuration file “sds.cfg” (refer to Annex 4).

• Whenever a domain (or sub-domain) is associated to a SDS, then none of itssub-domains can be associated to another SDS. The following “domain.cfg”example is wrong:

domain Portugal { domain North SDS_1 { domain Porto SDS_2; };}

• Whenever a domain (or sub-domain) is associated to a SDS, then this domaincan have more than one level of sub-domains. The following “domain.cfg”example is valid:

domain Portugal { domain North SDS_1 { domain Porto { domain Ribeira; }; };}


E200301-01-115-V10.0I-06 149

Annex 4 – Server Configuration Files


150 E200301-01-115-V10.0I-06


E200301-01-115-V10.0I-06 151

Server Configuration Files

The configuration of each SPOTS PMS component is stored in a file located under thedirectory $SPOTS_DIR of server’s file system.

The following configuration files are available:

PMS Component FilenameSPOTS Naming Server (SNS) sns.cfgSPOTS Application Server (SAS) sas.cfgSPOTS Database Server (SDS) sds.cfg

Each file defines values for a set of server "properties". The list of all server propertiesis given in the tables presented further on in this Annex, together with their defaultvalues.

The “*.cfg” file is automatically created upon the installation of the SPOTS PMScomponent, with the property values provided during the installation procedure. For allremaining (i.e. not declared) properties, the default values take effect.

If it is desired to modify the value of a property (i.e. either to change a property valuealready declared, or to set a not yet declared property to a non-default value), edit thefile according to the syntax mentioned below, changing or adding the property inquestion, and restart the corresponding PMS component.

� In order to restart a PMS component, proceed as follows:

Only for SAS:As spots user, issue the SPOTS command “spotsShutdown -r” on the hostwhere the SAS is located.

For any PMS component (SAS included):As spots user, issue the SPOTS commands “/etc/init.d/initSpotsPMS stop”and “/etc/init.d/initSpotsPMS start”, in this order: all the (installed) PMScomponents are restarted.

For the description of the SPOTS commands, refer to [1], Section 5.1.

The structure of the configuration file consists of a line per property with the followingsyntax:

<property>=<value>where <property> is a property name and <value> is a string, a number or a boolean(true/false) value.

All lines starting with the characters “#”,“;”, “[“ or “]” are considered comments, thusnot processed. Additionally, leading line spaces are ignored.

The name and the value of a property are case-insensitive. Example: “ServerId” and


152 E200301-01-115-V10.0I-06

“serVerId” have both the same meaning.

�� All the properties whose values are filenames or directories must be defined withthe full pathname.

�� In order to take full advantage of the system performance, make sure to adjust the“LoaderThreads” property in “sas.cfg” file.

SPOTS Naming Server (file “sns.cfg”)

Property Type Description Default valueLogFile String Name of the Log file $SPOTS_DIR/log/sns.log

LogFileTimeStampGMT Boolean Flag for log-messages withtime stamp in GMT FALSE

LocalHost StringFully qualified domain hostname or IP Address of thelocal host

Fully qualified domain hostname

TcpPort Number TCP IP port to be used bythe SNS 19980

PingPeriod Number Interval in seconds to “ping”other servers 120

SPOTS Application Server (file “sas.cfg”)

Property Type Description Default valueServerID String Server identifier AS@<SAS host name>

LocalHost StringFully qualified domain hostname or IP Address of thelocal host


TcpPort Number TCP IP port to be used by theSAS 19981

LogFile String Name of the Log file $SPOTS_DIR/log/sas.log

LogFileTimeStampGMT Boolean Flag for log-messages withtime stamp in GMT FALSE

NamingServerHost StringFully qualified domain hostname or IP Address of theassociated SNS


NamingServerPort Number TCP IP port of the associatedSNS 19980

PingPeriod Number Interval in seconds to “ping”other servers 120

DataLoadDir String

Root of directory tree used forstoring PM files collectedfrom the network. From thislocation, the collected filesare thereafter read by theloader command for loadinginto DB.

$SPOTS_DATA/traffic_data

PublicDir String Public directory $SPOTS_DIR

LoaderThreads Number Number of files to be loadedsimultaneously. To maximize 2


E200301-01-115-V10.0I-06 153

Property Type Description Default valuethe system performance thisinteger value ranging from 1to 20 should be set accordingto the following principle6:Int (2 * Nº of processors / Nºof loaders)See alsoMaximumSimultaneousInvocationsPerClient property.

MaximumSimultaneousInvocationsPerService Number

Maximum number ofsimultaneous serviceinvocations for all sessions.

50

MaximumSimultaneousInvocationsPerClient Number

Maximum number ofsimultaneous serviceinvocations for a givensession.

10

MinimumPercentageIntegrationData Number

Minimum percentage of data,for the aggregation interval,needed to perform any DataAggregation.Make sure to set the samevalue in ‘sas.cfg’ (used forexample in Ad-Hoc reports)and ‘sds.cfg’ (used forexample in mkhistory).

60

SasMaximumSize Number Specifies in Kb the maximumallowed size for SAS.

90% of machine physicalmemory, and the maximumallowed value is also 90% ofmachine physical memory.

ReportMaximumSize Number Specifies in Kb the maximumsize for each report. 512 * 1024

CSVPrecision Number

Specifies the number ofsignificant digits used byreporter command whenoutputting data to CSV files

4

6 The ‘Nº of loaders’ value stands for the number of loader commands running simultaneously, for instance, when you’re followinga load per file type (trf, spr, exp, ascii…) approach.Example:For a machine with 4 processors running 3 simultaneous loaders (trf, spr and exp) set the ‘LoaderThreads’ property to 2. To bemore precise the ‘LoaderThreads’ property value is equal to the integer part of the value given by ‘(2 * 4 / 3)’.


154 E200301-01-115-V10.0I-06

SPOTS Database Server (file “sds.cfg”)

Property Type Description Default value

ServerID String Server identifier DS@<SDS hostname>

LocalHost String Fully qualified domain host nameor IP Address of the local host

Fully qualified domainhost name

TcpPort Number TCP IP port to be used by theSDS 19982

LogFile String Name of the Log file $SPOTS_DIR/log/sds.log

NamingServerHost StringFully qualified domain host nameor IP Address of the associatedSNS

Fully qualified domainhost name

NamingServerPort Number TCP IP port of the associatedSNS 19980

PingPeriod Number Interval in seconds to “ping” otherservers 120

DatabaseName String

Identifies the database to whichSDS should connect.This designation is defined in file$TNS_ADMIN/tnsnames.ora ofOracle�

lm_spot

ConnectionPoolSize NumberContains the number of Oracle�connections kept in a pool for re-usage

10

Trace BooleanEnables the monitoring of heavydata base operations; the result iswritten in the LOG file

FALSE

LogFileTimeStampGMT Boolean Flag for log-messages with timestamp in GMT FALSE

NumberDaysInDetailPartition Number

Number of days to retain detaileddata when Data Partition has beenset as “Use Partitioning” duringinstallation.Use values multiple of 15.

15

AlarmLogSize Number Number of alarms stored indatabase 1000

MinimumPercentageIntegrationData Number

Minimum percentage of data, forthe aggregation interval, neededto perform any Data Aggregation.Make sure to set the same value in‘sas.cfg’ (used for example in Ad-Hoc reports) and ‘sds.cfg’ (usedfor example in mkhistory).

60


E200301-01-115-V10.0I-06 155

Annex 5 – Configuration Worksheet


156 E200301-01-115-V10.0I-06


E200301-01-115-V10.0I-06 157

Global data

Operating System Data

Host Name

Host Internet Address

Netmask for subnets

Default IP router

Geographical region

Time zone

SPOTS Installation Data

IP Address:SPOTS Naming Server

Port:

Database configuration � Tiny� Small � Partitioning option� Medium � Partitioning option� Large � Partitioning option

Previous OS installation boot deviceold boot-device


158 E200301-01-115-V10.0I-06

Disk Partition Information for Backup and Restore

If you will make system-oriented backups, the information on the tables below is used torecover from abnormal situations.

� IMPORTANT NOTE: You must fill the tables in order to recover fromdisaster situations if you will make system-oriented backups.

Disk: c_t_d_

Slice File SystemName

Tag Flag Cylinders Size(MB)

TapeBlock

(1)

0

1

2 backup

3

4

5

6

7

(1) This information is inserted during System Backup and represents the blockorder number (within a tape) of the saved file system; it is relevant for theSystem Restore mechanism, mainly for the Multiple Tape Backup scenario —seeAnnex 7 (System Backup / Restore).

If a backed up file system spans more than one (consecutive) tape, register whichtapes, and corresponding block order number within them, where it is saved.

E.g.: The first part of the file system ‘/spots_db1’ was saved at the end of tape#1 (starting at block #7) and the remaining at the beginning of tape #2.

The corresponding entry for Tape Block should be: T1/B7, T2/B1


E200301-01-115-V10.0I-06 159

Disk Partition Information for Fault Tolerance

If you will install fault tolerance, the tables below store information vital to disksubstitution in case of disk failure.

� IMPORTANT NOTE: You must fill all information if you will install faulttolerance.

� The information bellow is just needed for mirrored disks.

Information to fill before OS installationOn the Disk Location Table, fill the following fields, one row for each disk:

• Rack Number: This is the number printed in the rack were the disk isconnected. On machines that do not have rack numbers printed, fill “Up”,“Down”, “Left” or “Right” or any other word that can help to identify the disklocation.

• WWN (World Wide Number): This number is written in the optical disks box.Leave the field empty if the disk is not an optical disk. The internal disks of SunBlade and Sun Fire machines are optical disks. The internal disks of Sun Ultramachines are not optical disks.

• SN (Serial Number): This number is written in the disk box

Information to fill during OS installationOn the Disk Partition Tables, fill the following fields:

• Disk id: Name used to identify disks (ex c2t4d0). You can obtain theinformation during disk partitioning.

• Partition name: the mount point directory if the partition is mountable.

• Cylinders: You can obtain the information during disk partitioning.

• Size (MB): You can obtain the information during disk partitioning.

Information to fill after OS installationOn the Boot Device Table, fill the following information:

• boot device: boot device to boot from in the usual case. Obtain it from the firstvalue of parameter boot-device in the output of command eeprom.

On the Disk Partition Tables, fill the following fields:

• Geometry: Disk Geometry (ex :SUN4.2G cyl 3880 alt 2 hd 16 sec 135). Youobtain the information with the command format.


160 E200301-01-115-V10.0I-06

Information to fill during disk configuration with DiskSuite�On the Boot Device Table, fill the following information:

• Alternate boot device: boot device to boot from in case of master boot devicefailure. Note that the boot-device parameter is already set with the alternate bootdevice so the system automatically boot from there in case of disk failure.

Information to fill after disk configuration with DiskSuite�On the Disk Partition Tables, fill the following information:

• Mirror and Submirror: refer to section 5.2.1.4 and use the information to fillthe fields.

• Rack, WWN and SN: if the disks are optical disks use the command luxadm asdescribed in 5.2.7 to associate the disk id with the WWW value on the DiskLocation Table. Fill the Rack Nr., WWN and SN fields with the values of DiskLocation Table. If the Disks are not optical disks, refer to the system ServiceManual to associate the disk ids with the SN.


E200301-01-115-V10.0I-06 161

Boot Device Table

Boot Device

Alternateboot Device

Disk Location Table

Rack Nr. SN WWN


162 E200301-01-115-V10.0I-06

Disk Partition TablesPrint this page as many times as needed (one per mirror) and store them in a safe place.

Disk id: c__t__d__ Rack NR:WWN:SN:Geometry

Slice Partition name Cylinders SizeMB

Mirror

Submirror

0134567

Disk id: c__t__d__ Rack NR:WWN:SN:Geometry

Slice Partition name Cylinders SizeMB

Mirror

Submirror

0134567


E200301-01-115-V10.0I-06 163

Annex 6 – Initial Installation Task Flow


164 E200301-01-115-V10.0I-06


E200301-01-115-V10.0I-06

Initial Installation Task Flow

SPO

TS V

10

Solaris 8 Patches(Section 4.4)

SNS(Chapter 7)

SDS(Chapter 7)

SAS(Chapter 7)

Oracle 8.1.7(Chapter 6)

SCL(Chapters 7 or 8)

END INSTALLATION

BEGIN INSTALLATION

Solaris 8 (2/02)(Chapter 4)

EX

TR

AC

T

F
Optional:
ault Tolerance(Chapter 5)

165

SOFT

WA

RE

DA

TA

MIG

RA

TIO

N(S

pots

DM

)R

EC

OV

ER


E200301-01-115-V10.0I-06 167

Annex 7 – System Backup & Restore


168 E200301-01-115-V10.0I-06


E200301-01-115-V10.0I-06 169

System Backup

�� These System Backup procedures are applied only to small configurations. ALegato� based solution is available to support Backup and Restore for mediumand large configurations. See [4] for more information.

The System Backup script supports a multi-system and/or multi-volume backup; if morethan one tape is necessary, the user will be asked to replace tapes before proceeding.

All running processes will be stopped, before starting the backup.

�� Verify that, for each disk, the table “Disk Partitions” presented in the Annex 5 istotally and correctly filled in.A worst-case recovery process (when, at least, one of the partitions “/”, “/usr”,“/var” need to be recovered, i.e. the Operating System is unavailable) cannot beaccomplished if this table is either incomplete and/or incorrectly filled.

The needed information for the first column can be obtained doing the command:# df –k | grep dev

� The information for the remaining columns can be obtained executing thefollowing sequence of commands:(a) Login as root user.(b) Run the command ‘format’.(c) Choose a disk number (e.g., start with the “lowest”).(d) Choose the ‘Partition’ option (type “p”).(e) Choose the ‘Print’ option (type “p”).(f) Fill in the information in the table “Disk Partitions” (Annex 5).(g) Quit the current menu, typing “q”.(h) Type “disk” to choose the next disk.(i) Go to step (c).

To save the existing environment, the following sequence of commands must be exe-cuted:


� Verify that SPOTS_DIR environment variable is correctly set. It must pointto the base directory where SPOTS is installed. For further information referto Annex 2.

� Insert a new tape into the tape drive; make sure that the tape is ‘write enabled’ (tabat ‘REC’ position).


170 E200301-01-115-V10.0I-06

� Exit from SPOTS application (if it is running).

� Shutdown all running processes:# /etc/shutdown -y -g0 -i0Boot prompt> boot –sType control-d to proceed with normal startup,(or give root password for system maintenance): < root-password># mountall

� Change to the directory “$SPOTS_DIR/bin” and call the System Backup scriptwith a non-rewind tape device:# ./sysBackup <tape_device_name>

� Check in your system for the current <tape device name>

(e.g. “/dev/rmt/0n”).

� Check the log file “$SPOTS_DIR/log/spotsBackup.log” for errors and, foreach backed up file system, fill the column “Tape Block” in the table “DiskPartitions” (Annex 5) with the corresponding tape (T) and block (B) ordernumbers.Information about the successfully dumped file systems can also be found inthe file “/etc/dumpdates”.

� Reboot the system:# /etc/shutdown –y –g0 –i6

� Eject the tape and protect it against accidental erasure (tab at ‘SAVE’ position).

� Label the tape with:• the backup date;• the names of the backed up file systems;• the volume number;• the system name;• the performed ‘dump’ level (0);• the password of the root user (after a System Restore, this password

will be the one that was valid at the time where the correspondingSystem Backup was executed).

� The backup procedure is terminated.


E200301-01-115-V10.0I-06 171

System Restore

�� These System Restore procedures are applied only to small configurations. ALegato� based solution is available to support Backup and Restore for mediumand large configurations. See [4] for more information.

SPOTS provides two different processes for restoring a full System Backup:

Single Tape Backup

The script “sysRestore”, leading the user through the recovery of each file system,automatically performs the restoring activities.

�� The System Restore script assumes that the partition settings in the currentdisk(s) (controller / tray / disk / slice) match, one by one, those that arestored in the tape (and therefore, as it was in the backed-up disk at the back-up time).

Multiple Tape BackupIf more than one tape was used for backup, the restoring activities will be reques-ted by the user, using, as reference, the information that was registered in thecolumn “Tape Block” of the table “Disk Partitions” (Annex 5).

For both, two different recovery mechanisms are used, according to the availability ornot of the Operating System (OS):

• OS Disk RecoveryIf the system is not bootable (at least one of the partitions “/”, “/usr”, “/var” needto be recovered).

• Non-OS Disk RecoveryThe system is bootable.

�� Database file systems (/spots_db*) can’t be restored separately, i.e., restoring oneforces to restore all the Database file systems.


172 E200301-01-115-V10.0I-06

1 Single Tape Backup

1.1 OS Disk Recovery

In this situation the system is not bootable. Therefore, you must boot from the Solaris�installation CD, re-create, if necessary, the partitions on the hard disk (e.g., in the caseyou are using a new and unformatted disk) and recover these file systems:

� Insert the Solaris� 8 2/02 Installation CD and enter the following command:ok boot cdrom –sw

�� The next two steps are applied only if the current disk partitioning differs from theone that is previously registered in the table “Disk Partitions” (Annex 5).

� For each disk, restore the partition table:(a) Run the command ‘format’.(b) Choose a disk number (e.g., start with the “lowest”).(c) Choose the ‘Partition’ option (type “p”).(d) Choose the ‘Print’ option (type “p”).(e) For the all the disk partitions, provide the information as defined in the

table “Disk Partitions” (Annex 5).(f) Label the disk, running the command ‘label’ and quit the current menu,

typing “q”.(g) Type “disk” if there are additional disks to be formatted; otherwise, quit

format utility typing “q”.(h) Go to step (b).

� Create the file system for the swap partition (for the remaining partitions, this willbe done by System Restore script):# newfs /dev/rdsk/<device name>

� For details about the partition’s <device name> (e.g., c0t0d0s0), refer to thetable “Disk Partitions” in the (Annex 5)

� Create tape device entries; make sure that the (backup) tape(s) is(are) ‘write pro-tected’ (tab at ‘SAVE’ position):# tapes

� Insert the backup tape into the tape drive, extract the System Restore script andexecute it:# mt -f <tape_device> rewind# dd bs=8k if=<tape_device> of=/tmp/sysRestore# chmod 755 /tmp/sysRestore# /tmp/sysRestore <tape device name>


E200301-01-115-V10.0I-06 173


(e.g. “/dev/rmt/0n”).�� During the execution of the script, a menu-driven utility will guide the user

for the recovery of each file system.

� Reboot the system:# init 6

� The system disk is recovered and restored.

1.2 Non-OS Disk Recovery

In this situation the system is bootable. Therefore, the restore mechanism is restricted toload and execute the System Restore script:

� Stop SPOTS, including all scheduled jobs and daemons — refer to section 3.3.4.

� Shut down the Oracle� instance, if it exists, executing the following command asroot user:# /etc/init.d/dbora stop

� Insert the backup tape into the tape drive, extract the System Restore script andexecute it:# umount –a# mt -f <tape_device> rewind# dd bs=8k if=<tape_device> of=/tmp/sysRestore# chmod 755 /tmp/sysRestore# /tmp/sysRestore <tape device name>



�� During the execution of the script, a menu-driven utility will guide the userfor the recovery of each file system.


� The (non-system) disk is restored.


174 E200301-01-115-V10.0I-06

2 Multiple Tape Backup

2.1 OS Disk Recovery

� Proceed with the steps 1 through 4 of the similar section of Single Tape Backup(this Annex, Section 1.1).

� Collect the information related with the file systems to be restored — seePlanning File Systems Recovery (this Annex, Section 2.1.1).

� Restore the file systems — see Restoring File Systems (this Annex, Section2.1.2).


� The system disk is recovered and restored.

2.1.1 Planning File Systems Recovery

Before restoring file systems from a full System Backup, check which are available inthe tapes and take in account the further considerations in this section.

� As root user, load the backup tape #1 into the tape drive, extract the file FileSystem Name List (“/tmp/fsnlist”) and read it, executing these commands:# mt -f <tape device name> rewind# dd bs=8k if=< tape device name > of=/dev/null# dd bs=8k if=< tape device name > of=/tmp/fsnlist# cat /tmp/fsnlist



� The lines in the file File System Name List were produced according to thissyntax:<seq_number> <partition> <file_system>

where:<seq_number> is a sequential number for ordering the file systems that were

backed up.<partition> is the device name to which the file system will be restored.<file_system> is the name of the file system to be restored.


E200301-01-115-V10.0I-06 175

Example:1 /dev/rdsk/c2t1d0s0 /2 /dev/rdsk/c2t1d0s5 /var3 /dev/rdsk/c2t1d0s3 /export/home4 /dev/rdsk/c2t1d0s4 /opt5 /dev/rdsk/c1t1d0s0 /spots_db16 /dev/rdsk/c1t2d0s0 /spots_db27 /dev/rdsk/c1t3d0s0 /spots_db38 /dev/rdsk/c1t4d0s0 /spots_db49 /dev/rdsk/c1t5d0s0 /spots_db510 /dev/rdsk/c1t6d0s0 /spots_db6

From the list of file systems, select those to be restored, taking in account that filesystems must be restored in the ascending sequential order number in which they aredescribed in the file File System Name List.

According to the previous selection, identify the tapes that will be used in the restoreprocess, reading the Tape Block information that was registered in the “InstallationConfiguration Worksheet / Disk Partitions” (Annex 5).

2.1.2 Restoring File Systems

For each file system to be restored, execute, as root user, the following steps:

� If the tape’s file system doesn’t exist in the disk at restore time, create it in thetarget disk partition, executing the following command:# newfs /dev/rdsk/<device name>

� Refer to the table in the “Installation Configuration Worksheet / DiskPartitions” (Annex 5) for details about the partition’s device name (e.g.,c0t0d0s0).

� If the tape with the beginning of the file system to be restored is not loaded, load itand execute the following command:# /usr/bin/mt -f <tape device name> rewind

Additionally, and only if tape #1 has been loaded, execute the followingcommand:# /usr/bin/mt -f <tape device name> fsf 2



� Move the tape to the beginning of the desired file system, executing the followingcommand:# /usr/bin/mt –f <tape device name> fsf [(bi – bi-1)-1]

where:bi is the block order number within a tape for the file system to be recovered

— see the Tape Block information in the “Installation ConfigurationWorksheet / Disk Partitions” (Annex 5).


176 E200301-01-115-V10.0I-06

bi-1 is the block order number within the same loaded tape of the previouslyrecovered file system. Assume bi-1 = 0 if, for the same loaded tape, no filesystem had been restored yet.

� Mount the desired file system in the correct ‘controller / tray / disk / slice’:# mount /dev/rdsk/<device name> /mnt

� Change to the directory “/mnt” and restore the file system, executing the followingcommands:# cd /mnt# /usr/bin/ufsrestore rfv <tape device name>

�� If the file system to be restored is spanned in more than one tape, when theend of the first one is reached, a message is prompted, asking for changingthe tape to proceed with the recovery.

� Change to the directory “/” and un-mount the file system “/mnt”, executing thesecommands:# cd /# umount /mnt


E200301-01-115-V10.0I-06 177

2.2 Non-OS Disk Recovery

� Stop SPOTS, including all scheduled jobs and daemons — see Stopping SPOTS,Chapter 3, Section 3.3.4.

� Shut down the Oracle� instance, if it exists, and un-mount all existing filesystems, executing the following commands:# /etc/init.d/dbora stop# cd /# umount -a

� Collect the information related with the file systems to be restored — seePlanning File Systems Recovery (this Annex, Section 2.1.1).

� Restore the file systems — see Restoring File Systems (this Annex, Section2.1.2).


� The (non-system) disk is restored.

Education

Spots 10.0 Installation