Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
SIEMENS S.A. 
SPOTS V10 Drop 4 
Installation Guide 
November/2003 
E200301-01-115-V10.0I-06
 SIEMENS S.A. 
OG IC, R&D WON NM P3 
R. Irmãos Siemens, nº 1 
2720-093 Amadora 
Portugal 
All rights reserved. No part of...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
Table of Contents 
1 INTRODUCTION........................................
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
5.2.7 Associating Disk ids to WWNs and Rack Numbers......................
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
E200301-01-115-V10.0I-06 iii
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
1 Introduction 
The SPOTS product belongs to the family of Network Man...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
1.1 SPOTS documentation 
The SPOTS Long-Term application documentation...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
1.2 Target group and structure of this manual 
The Installation Guide ...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
2 General Overview 
The SPOTS system comprises several functional comp...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
It is possible to install the SPOTS PMC on the same system as the SPOT...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
2.1 Platform Hardware  Standard Software 
2.1.1 SPOTS PMS and PMC (Sol...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
Large Configuration 
UltraSPARC-III based Server 
Sun Fire V880 (4 x 9...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
2.1.2 SPOTS PMC (Windows environment) 
Hardware 
The following minimal...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
2.2 Collecting information 
During the initial SPOTS installation, you...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
Fault Tolerance configuration data 
Before you begin the OS installati...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
2.3 Hard Disk Partitioning 
This section describes the disk partitions...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
Partition Tiny2 Small Medium Large 
Size 
(GB) 
Size 
(GB) Disk Extend...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
3 Installation Procedure Overview 
This chapter provides an overview o...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
3.1 Initial Installation 
Before installing SPOTS, one shall collect t...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
3.2 APS upgrade 
Before upgrading SPOTS, collect the necessary informa...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
 During an APS upgrade from a previous SPOTS V10 Drop 3 or Drop 4 some...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
File Purpose 
RT Agencies in Solaris 
data_type/cfg/real_time.cfg 
whe...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
without Database reinstallation from Drop 3 to Drop 4. Contact your lo...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
3.2.1 APS Upgrade without Database re-installation 
1. Stopping SPOTS ...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
 From Chapter 7, execute only the sections 7.1 to 7.3 and make sure th...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
(if upgrading from a previous SPOTS V10 Drop 4 installation) 
# /opt/s...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
3.2.2 APS Upgrade with Database re-installation 
To perform an APS upg...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
3.3 Data Migration 
3.3.1 Data Migration overview 
The Data Migration ...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
instructing you how to configure the “sds.cfg” file. Any non-conformit...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
3.3.2 Extracting data from an existing SPOTS system 
 If the existing ...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
3.3.3 Regenerating extracted data on the newly installed SPOTS system ...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
3.3.4 Stopping SPOTS 
Execute the following steps to stop the SPOTS se...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
 Wait a few seconds and then verify if RC FTP server is stopped, execu...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
3.3.5 Installing SPOTS Data Migration package 
Install the Data Migrat...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
3.3.6 Dump existing data into tape(s) 
Execute the following steps, to...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
3.3.7 Recovering regenerated data from tape(s) 
In the newly installed...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
is the NE name used in the “old” SPOTS version: the NMS 
name concaten...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
current_BSC_name 
is the BSC name used in the “old” SPOTS version: the...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
In the displayed Text Editor window, a line with the following syntax ...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
mapped, the above file can be created automatically by the getsymbname...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
$ cd $SPOTS_DIR/bin 
$ ./getsymbname 
This step shall create a file na...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
3.3.8 Removing the SPOTS Data Migration package 
Carry out the followi...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
3.3.10 Starting SPOTS 
Execute the following steps to start the SPOTS ...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
4 Installing the Operating System 
This chapter describes how to insta...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
 Choose the location to place the Solaris installation software: 
 Swa...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
 Please wait… 
After copying Solaris installation software, the system...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
4.2 Configuring the System 
In this section, the installer provides al...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
“None” 
 Specify Time Zone by: 
“Geographic Region” 
 Select the adjus...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
4.3 Installing Solaris 
Most of the Solaris 8 installation is describe...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
“None” 
 Applicable on UltraSparc-II platforms only. Select 64-Bit Sup...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
 The Installation Summary dialogue box is presented. For further detai...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
 Insert the Solaris 8 2/02 Documentation CD and start the installation...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
4.4 Installing Solaris Patches 
The SPOTS SW is distributed along with...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
“Do not install Sun OpenGL” 
5. In the next dialog press any key to st...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
5 Fault Tolerance with Disk Mirroring 
To improve SPOTS availability F...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
5.1 Setup Tasks 
To configure the system for Fault Tolerance with Disk...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
1. System disk mirroring for Sun Blade systems with 2 internal disks a...
Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 
# ./runstep 2 
 The alternate boot is present in the output of last st...
Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 
/spots_db2_mirror 
/spots_db3 
/spots_db3_mirror 
/spots_db4 
/spots_d...
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Spots 10.0 Installation
Upcoming SlideShare
Loading in …5
×

Spots 10.0 Installation

414 views

Published on

Spots 10.0 Installation

Published in: Education
  • Be the first to comment

  • Be the first to like this

Spots 10.0 Installation

  1. 1. SIEMENS S.A. SPOTS V10 Drop 4 Installation Guide November/2003 E200301-01-115-V10.0I-06
  2. 2.  SIEMENS S.A. OG IC, R&D WON NM P3 R. Irmãos Siemens, nº 1 2720-093 Amadora Portugal All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose other than the purchaser’s personal use without the 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.
  3. 3. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. Table of Contents 1 INTRODUCTION...........................................................................................................................................5 1.1 SPOTS documentation .......................................................................................................................................6 1.2 Target group and structure of this manual..........................................................................................................7 1.2.1 Document Conventions.............................................................................................................................7 2 GENERAL OVERVIEW..................................................................................................................................8 2.1 Platform Hardware & Standard Software.........................................................................................................10 2.1.1 SPOTS PMS and PMC (Solaris environment).....................................................................................10 2.1.2 SPOTS PMC (Windows environment) ................................................................................................12 2.2 Collecting information .....................................................................................................................................13 2.3 Hard Disk Partitioning .....................................................................................................................................15 3 INSTALLATION PROCEDURE OVERVIEW....................................................................................................17 3.1 Initial Installation .............................................................................................................................................18 3.2 APS upgrade ....................................................................................................................................................19 3.2.1 APS Upgrade without Database re-installation.......................................................................................23 3.2.2 APS Upgrade with Database re-installation ............................................................................................26 3.3 Data Migration .................................................................................................................................................27 3.3.1 Data Migration overview ........................................................................................................................27 3.3.2 Extracting data from an existing SPOTS system.....................................................................................29 3.3.2.1 Extraction using dbArchive........................................................................................................29 3.3.3 Regenerating extracted data on the newly installed SPOTS system........................................................30 3.3.3.1 Regeneration using dbArchive ...................................................................................................30 3.3.4 Stopping SPOTS.....................................................................................................................................31 3.3.5 Installing SPOTS Data Migration package .............................................................................................33 3.3.6 Dump existing data into tape(s) ..............................................................................................................34 3.3.7 Recovering regenerated data from tape(s)...............................................................................................35 3.3.8 Removing the SPOTS Data Migration package ......................................................................................41 3.3.9 Post Migration configuration files update...............................................................................................41 3.3.10 Starting SPOTS.....................................................................................................................................42 4 INSTALLING THE OPERATING SYSTEM.......................................................................................................43 4.1 Getting Started .................................................................................................................................................43 4.2 Configuring the System....................................................................................................................................46 4.3 Installing Solaris ...........................................................................................................................................48 4.4 Installing Solaris Patches ..............................................................................................................................52 5 FAULT TOLERANCE WITH DISK MIRRORING..............................................................................................54 5.1 Setup Tasks ......................................................................................................................................................55 5.1.1 Installing Solstice DiskSuite Software.................................................................................................55 5.1.2 Configuring Disk Mirroring....................................................................................................................55 5.1.2.1 Configuring System Disk Mirroring...........................................................................................56 5.1.2.2 Configuring Full Disk Mirroring................................................................................................57 5.2 Maintenance Procedures ..................................................................................................................................59 5.2.1 Monitoring Tasks ....................................................................................................................................59 5.2.1.1 DiskSuite Objects....................................................................................................................59 5.2.1.2 Disk Failure Notification via Email............................................................................................60 5.2.1.3 Verifying the Status of State Database Replicas ........................................................................60 5.2.1.4 Verifying Status of Metadevices ................................................................................................61 5.2.2 Replacing mirroring disks .......................................................................................................................62 5.2.3 Booting system with insufficient database replicas.................................................................................64 5.2.4 Creating and Deleting DiskSuite Objects.............................................................................................65 5.2.4.1 Creating a DiskSuite State Database Replica ..........................................................................65 5.2.4.2 Removing a DiskSuite State Database Replica .......................................................................66 5.2.4.3 Creating a DiskSuite submirror...............................................................................................66 5.2.4.4 Removing a DiskSuite submirror ............................................................................................66 5.2.4.5 Removing a DiskSuite Mirror and Submirrors........................................................................67 5.2.4.6 Unmirroring a File System That Cannot Be Unmounted ...........................................................69 5.2.5 Formatting Disks.....................................................................................................................................71 5.2.6 Creating File Systems .............................................................................................................................73 E200301-01-115-V10.0I-06 i
  4. 4. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 5.2.7 Associating Disk ids to WWNs and Rack Numbers................................................................................73 5.2.8 Detect and terminate processes that are using a filesystem.....................................................................75 5.3 De-installation Tasks........................................................................................................................................78 5.3.1 Un-mirroring Disks .................................................................................................................................78 5.3.2 De-installing Solstice Disksuite Software............................................................................................79 6 INSTALLING ORACLE SOFTWARE ...........................................................................................................80 6.1 Creating Groups and Users...............................................................................................................................80 6.2 Installing Oracle Software.............................................................................................................................83 6.3 Installing Oracle Patch Set ............................................................................................................................88 6.4 De-installing Oracle Software .......................................................................................................................90 7 INSTALLING SPOTS SOFTWARE (SOLARIS ENVIRONMENT) ...................................................................91 7.1 Adding SPOTS SW with admintool.................................................................................................................92 7.2 Adding SPOTS Software with Package Commands.........................................................................................95 7.3 Package Installation .........................................................................................................................................97 7.3.1 NIS Users and Groups Requirements......................................................................................................97 7.3.2 SPOTS Naming Server ...........................................................................................................................97 7.3.3 SPOTS Application Server .....................................................................................................................99 7.3.4 SPOTS CLient (Solaris variant).........................................................................................................101 7.3.5 SPOTS Database Server........................................................................................................................103 7.3.6 SPOTS Data Migration .........................................................................................................................106 7.4 Post-Installation Procedures...........................................................................................................................107 7.4.1 Installing SPOTS Database...................................................................................................................109 7.5 NMS Configuration........................................................................................................................................111 7.5.1 NMS Configuration File .......................................................................................................................111 7.5.2 OMC-S Access Specifics ......................................................................................................................112 7.5.3 SC Access Specifics..............................................................................................................................113 7.5.4 @vantage Commander Access Specifics ..............................................................................................114 7.5.5 OMC-B Access Specifics......................................................................................................................115 7.5.6 RC Access Specifics .............................................................................................................................115 7.5.7 IPM Access Specifics............................................................................................................................117 7.5.8 IPM Converter Specifics.......................................................................................................................118 7.6 SPOTS Licensing Software............................................................................................................................120 7.6.1 Configuring SPOTS licenses.................................................................................................................120 7.6.2 Updating the SPOTS licenses ...............................................................................................................121 8 INSTALLING SPOTS-PMC (WINDOWS ENVIRONMENT) .......................................................................122 8.1 Installation sequence ......................................................................................................................................122 8.2 Troubleshooting .............................................................................................................................................125 8.3 SPOTS License checking ...............................................................................................................................126 9 UNINSTALLING SPOTS SOFTWARE (SOLARIS ENVIRONMENT) .............................................................127 9.1 Stopping SPOTS applications ........................................................................................................................127 9.2 De-installing SPOTS database .......................................................................................................................127 9.3 Removing SPOTS Packages...........................................................................................................................128 9.3.1 Removing SPOTS Packages with admintool ........................................................................................128 9.3.2 Removing SPOTS Packages with Package Commands ........................................................................129 10 DE-INSTALLING SPOTS-PMC (WINDOWS ENVIRONMENT) ...............................................................130 10.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 ii E200301-01-115-V10.0I-06
  5. 5. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. E200301-01-115-V10.0I-06 iii
  6. 6. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 1 Introduction The SPOTS product belongs to the family of Network Management Systems provided by 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 standard software) and application software that supports the Performance Management activities on the network. The SPOTS V10 Drop 4 application software includes a mandatory Long-Term part and an optional, additional Real-Time part. The SPOTS V10 Drop 4 Long Term provides performance management analysis capabilities, allowing to produce pre-defined and user-defined reports with Performance Management indicators based on data periodically collected from the network. The SPOTS V10 Drop 4 Real Time part provides near real-time updates of the network Performance Management information, allowing to define threshold values for Performance Management indicators that result in alarms when they are violated. The optional module SNMP Alarm Agent allows these alarms to be forwarded via SNMP to an external application. This document describes the installation procedures for the SPOTS V10 Drop 4 mandatory part, that is, for the Long-Term part. The description of the SPOTS V10 Drop 4 Real-Time installation is provided in [3]. E200301-01-115-V10.0I-06 5
  7. 7. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 1.1 SPOTS documentation The SPOTS Long-Term application documentation consists of the following parts: Manuals Document 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 Notes Summarizes the authorized versions of the hardware and software products and up-to-date information about user notes, functional limitations and error corrections. The Release Notes are applied for a specific release of this SPOTS version (including both the Long-Term and the Real-Time part). SPOTS V10.0.x – Release Notes — refer to [2] On-line help Provides a complete “on-context “ description of the system functionality. 6 E200301-01-115-V10.0I-06
  8. 8. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 1.2 Target group and structure of this manual The Installation Guide is intended for System Administrators and for those who install the SPOTS product. On the server side, it describes the necessary procedures to perform the initial installation, APS upgrades, configuration and de-installation of the SPOTS system 1), specific chapters are dedicated to the installation and de-installation of the Windows variant (NT / 2000 / XP) of the SPOTS Client. Chapter 2 describes the functional components of the SPOTS system. It also lists the information that must be gathered before starting the initial installation. Chapter 3 contains an overview of the required procedures for the initial installation and system upgrade. For the installation procedures, refer to Chapter 4 through Chapter 7. Perform the installation procedures as described in this manual. Deviations can result 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 some value to be input that cannot be determined in beforehand and so it 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. E200301-01-115-V10.0I-06 7
  9. 9. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 2 General Overview The SPOTS system comprises several functional components, grouped into installable SW 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) SPOTS-PMS SAS PM File Converters Application Service Corba Task Scheduler Location Service SDS Database Service Oracle8 Corba Operating System (Solaris 8) SNS Naming Service Corba Network (TCP/IP) Database Utilities Data Collection SPOTS-PMC SCL SPOTS Client JRE Corba 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. This is done using the collection services provided by the corresponding NMSs. Hence, the configuration procedures, required to allow the interoperability between SPOTS and the NMS (refer to Section 7.5), assume critical relevance. SPOTS PMS components may be installed in two different configuration types: Single Server and Distributed — details on these configurations are described in [1], Section 1.2 (Environment). SPOTS PMC will be installed on each user’s workstation implementing the SPOTS Graphical 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 8 E200301-01-115-V10.0I-06
  10. 10. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 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 with Windows is presented in Chapter 8 and Chapter 10 whilst SPOTS PMC installation and de-installation in Solaris is presented along with SPOTS PMS installation and de-installation in Chapters 7 and 9. E200301-01-115-V10.0I-06 9
  11. 11. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 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) is that 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 your Siemens representative, who will help you determine which configuration best fits your network. The described HW configurations are applied to the Single Server scenario; for the Distributed environment, HW configurations will be provided on request — details on Single Server and Distributed environments are described in [1], Section 1.2 (Environment). Small Configuration UltraSPARC-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 Workstation Sun Blade 2000 (1 x 900 MHz CPU) with: – 1 GB RAM; – 2 internal disks (minimum disk size: 18 GB). Medium Configuration UltraSPARC-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 Workstation Sun 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). 10 E200301-01-115-V10.0I-06
  12. 12. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. Large Configuration UltraSPARC-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 Server Sun 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 (Order Sheet for SPOTS V10 Licensing File). This information shall be used, by your Siemens representative, to calculate the SPOTS configuration that best fits the size of your network. 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 — see Chapter 7 for a detailed description of the SPOTS software packages. E200301-01-115-V10.0I-06 11
  13. 13. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 2.1.2 SPOTS PMC (Windows environment) Hardware The following minimal configuration is required: Requirement Value Comment Processor Pentium or equivalent Suggested Memory 128 MB Suggested Virtual memory 256 MB Suggested Hard disk space 55 MB Mandatory Video resolution 800x600 pixels Mandatory Video 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 in Chapter 8. 12 E200301-01-115-V10.0I-06
  14. 14. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 2.2 Collecting information During the initial SPOTS installation, you are asked for parameterisation information to be used in the system. You should therefore understand the topics covered in this Chapter, before starting the software installation; use the Annex 5 to register the relevant information for each host. Workstation/server configuration parameters Host name The workstation name, as specified in /etc/hosts Example: “pms01” Host IP address The network administrator assigns the workstation/server Internet Protocol address. Example: 129.200.9.1 Netmask for subnets The value you enter depends on the internet address class and whether sub-networks are used (see table below). Example: 255.255.225.0 Default Router Specify a default IP router or let Solaris installation program find one. In the first case provide the “Router IP address”. 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 Address Class Byte1 Byte2 Byte3 Byte4 Default Netmask A 0-127 1-254 1-254 1-254 255.0.0.0 B 128-191 1-254 1-254 1-254 255.255.0.0 C 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 IP Address and TCP/IP Port configured during its installation. This might be useful since SAS, SDS and SCL all need this information. 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 which configuration best fits your network and realize the corresponding hard disk requirements in the following section. E200301-01-115-V10.0I-06 13
  15. 15. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) Fault Tolerance configuration data Before you begin the OS installation you must fill the Fault Tolerance information in Annex 5. 14 E200301-01-115-V10.0I-06
  16. 16. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 2.3 Hard Disk Partitioning This section describes the disk partitions to be created (during Solaris 8 installation), for each of the HW configurations presented in Section 2.1. An additional alternative is presented: the Tiny configuration, for use only for field trial and demo purposes. On Annex 1, the additional partitions required for HW configurations supporting mirrored 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 on request — 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 where it 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 available disk space. The rules for extending the partition sizes follow, in order of precedence: 1. Small configuration, disk1: Consider the amount of free disk space after allocating the minimum partition sizes. Allocate 2/3 of the free disk space to extend 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 the free space to /spots_db3 and ½ to /spots_db4. 3. Other partitions marked Yes in the Extend column: allocate all of the available disk space to extend the partition. 4. For the disks where disk space is still available, extend one of the partitions in the disk. In practical terms, the first two rules reduce to: in the Small configuration, split the available space in disk 0 among /spots_db3 and /spots_db4 in equal parts, and the available space in disk 1 among /spots_db5 and /spots_db6 maintaining their relatives sizes. On Medium and Large, as there is one dedicated disk per partition (among those supposed to grow), just assign the available space in each disk. ‘/spots_arch’ partition should be created in Spots Medium and Large configurations where the Backup Restore option will be deployed. Only in those cases these partitions shall be created. 1 A simpler approach is presented for the Tiny configuration. E200301-01-115-V10.0I-06 15
  17. 17. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) Partition Tiny2 Small Medium Large Size (GB) Size (GB) Disk Extend Size (GB) Disk Extend 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 two disks are available. 16 E200301-01-115-V10.0I-06
  18. 18. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 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 APS Upgrade (Section 3.2). The Initial Installation procedure applies for installing SPOTS from scratch. Additionally, the Initial Installation also applies when SPOTS is previously installed but disk partition sizes need to be changed (see Section 2.3 for disk partitioning information). If SPOTS is already installed and no partition resizing occurs, the APS Upgrade procedure 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 be coupled with a Data Migration procedure. The Data Migration procedure allows transferring data from an existing SPOTS installation (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 Upgrade procedures, as appropriate.) Before executing the installation tasks (Initial Installation or APS Upgrade), and if applicable, assure that the existing SPOTS applications and all the associated jobs and daemons are stopped — refer to the Section “Stopping SPOTS” in the Installation 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 E200301-01-115-V10.0I-06 17
  19. 19. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 3.1 Initial Installation Before installing SPOTS, one shall collect the necessary information, to serve as reference during the installation — see Annex 5. Refer to Annex 6, for an overview of the 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 Initial Installation. 1. Extracting data from an existing SPOTS system (This step applies only if it is desired to migrate performance data stored on an existing 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 migration procedure. Then, perform the steps in Section 3.3.2 to extract data from the existing SPOTS system. 2. Installing Specific Hardware The procedure to install the required hardware components is out of the scope of this manual. Refer to the hardware documentation. 3. Installing Standard Software Perform the steps in Chapters 4, 5 and 6. 4. Installing SPOTS Software Perform 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 an existing 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 onto the newly installed SPOTS system. 6. Installing Real-Time software (if applicable) If the SPOTS Real-Time functionality is desired, install the respective software as described in the Real-Time Installation Guide ([3]). 7. Setting the Oracle password Execute, as root user, the SPOTS command setdbpwd with the -c parameter (as described in [1]), to change the Oracle password for all SPOTS Database connections. The used password length must be between 6 and 8 characters. 18 E200301-01-115-V10.0I-06
  20. 20. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 3.2 APS upgrade Before upgrading SPOTS, collect the necessary information, to serve as reference during the installation — see Annex 5. For security reasons, a System Backup shall be performed, before executing APS upgrade procedure; if any unrecoverable error occurs during its execution, the pre-vious environment could be re-established via a System Restore — refer to the description of System Backup Restore procedures of the SPOTS version to be de-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 data existing in several configuration files is lost. To avoid reconfiguring them again, before de-installing the existing SPOTS packages, all these files need to be saved for future merge with the newly installed. The following table lists all these files (relative paths are located under the SPOTS base installation directory), ordered by SPOTS package. File Purpose /etc/spotsenv This file holds the SPOTS run-time environment. The ‘old’ user-defined environment variables must be reconfigured. SpotsAS custom/reports/virtual_entities.dat This file carries the Siemens pre-defined virtual entities. The ‘old’ user-defined public virtual 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 nodes creation entries must be added. sas.cfg The ‘old’ user-defined properties must be added. users.cfg No users are defined by default. Use ‘old’ users configuration file. egw.cfg The ‘old’ user-defined properties must be added. mail.cfg The ‘old’ user-defined properties must be added. SpotsDS sds.cfg The ‘old’ user-defined properties must be added. SpotsNS sns.cfg The ‘old’ user-defined properties must be added. E200301-01-115-V10.0I-06 19
  21. 21. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) During an APS upgrade from a previous SPOTS V10 Drop 3 or Drop 4 some Real-Time specific user-defined data are lost. To ease the task of reconfiguring them again, save the following information before de-installing the existing SPOTS packages: Threshold definitions: (Only if an Upgrade with Database reinstallation is performed -- see more information on APS Upgrade variants below). Use the Export Threshold Values functionality of SPOTS to export all existing threshold definitions onto a CSV file. This file must be saved for future import into the new SPOTS installation, using the Import Threshold Values functionality. Consult [7], Section 3.6.5.4, for information on the Threshold Export and Import functionality. Real-Time Agency default memory: If the value of the maximum memory available for any RT Agency has been changed from the default, write down the changes made in the file %SPOTS-RTAgency%Jamesprofilesservice.properties to reuse after the upgrade. Refer to Real-Time Installation Guide [3], Sections “4.4.1-Configuring SPOTS RT Agency Software (Solaris environment)” or “5.2.1-RT Agency configuration files” for details. Real-Time Agents default granularity: If the value of the supported granularity for any RT Agent has been changed from 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.xml to reuse after the upgrade. Refer to Real-Time Installation Guide [3], Section “4.4.3- Modifying the RT Agents default granularity” for details. RT Bar Chart reports default granularity: If the value of the granularity for any RT Bar Chart report has been changed from the default, write down the changes made in the affected files: /opt/spots/reports/src/*_BC.sc to reuse after the upgrade. Refer to Real-Time Installation Guide [3], Section “4.4.4- Modifying the RT Bar 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 configuration files that must be saved for future merge with the newly installed. The following table lists all these files (relative paths are located under the SPOTS base installation directory) depending if the RT Agencies are located in a Solaris environment or in a Windows environment (relative paths are located under the SPOTS Agency base installation directory). 20 E200301-01-115-V10.0I-06
  22. 22. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. File Purpose RT Agencies in Solaris data_type/cfg/real_time.cfg where data_type can be: ascii cyclic exp ggsn hlri msp q3dc sctc spr upf This file is created manually by the user when the Agency is installed in Solaris (refer to Real-Time Installation Guide [3] in section “4.4.1.1-Configuring real_time.cfg files”). It holds the information for the directory where the agency was installed, the name of the agency and the filter for the name of the files to be processed, e.g.: /opt/spots_rt/rta Agency_4 ‘sc3’ RT Agencies in Windows FileTransfercfgAgentDirectories.cfg It holds information about the name of the files that are processed by each Agent/Agency. FileTransfercfgFileTransfer.cfg It holds information about the parameters for the FileTransfer application. FileTransfercfgPDCData.cfg It holds information about the identification of the files generated for each type of data. Upgrading to a new SPOTS Client version results in loss of possibly existing user customised data, like for example applications preferences and/or look feel. After performing an APS upgrade in the SPOTS Client the default settings are reset. Upgrading to a new SPOTS Client version implies that all Unix/Windows Clients have 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 version is 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 perform a first upgrade from Drop 2 to Drop 3 in order to allow an APS upgrade E200301-01-115-V10.0I-06 21
  23. 23. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) without Database reinstallation from Drop 3 to Drop 4. Contact your local Siemens representative for advice. APS Upgrade with Database re-installation: This APS Upgrade procedure must be applied whenever the origin SPOTS version is earlier than SPOTS V10. To execute this procedure, follow the steps in section 3.2.2 below. 22 E200301-01-115-V10.0I-06
  24. 24. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 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 the following 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-installing the Database. This is achieved by following the SPOTS V10 Drop 3 / Drop 4 Installation Guide, executing the steps in Section 9.3 Removing SPOTS Packages. 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. E200301-01-115-V10.0I-06 23
  25. 25. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) From Chapter 7, execute only the sections 7.1 to 7.3 and make sure that the SpotsDM package is installed in the same host where SPOTS Database is installed. 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 SPOTS Installation) 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 files installed by SPOTS packages. The merge of virtual_entities.dat file should be done later in the procedure when SPOTS services are running. The method is described ahead in step 11. The restore of SPOTS RT configuration files will be described ahead in step 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 –c Enter current password: [current password] Enter new password : o5mc0 Retype 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 24 E200301-01-115-V10.0I-06
  26. 26. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. (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 as described 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 the new files installed by SPOTS Real-Time package. 15. Setting the Oracle password Execute the SPOTS command setdbpwd with the -c parameter (as described in [1]), to change the Oracle password for all SPOTS Database connections. The used password length must be between 6 and 8 characters. E200301-01-115-V10.0I-06 25
  27. 27. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 3.2.2 APS Upgrade with Database re-installation To perform an APS upgrade with Database re-installation, the following steps must be executed. Before proceeding, refer to [2] for possible specific recommendations on APS Upgrade. 1. Extracting data from an existing SPOTS system (This step applies only if it is desired to migrate performance data stored on an existing 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 migration procedure. Then, perform the steps in Section 3.3.2 to extract data from the existing SPOTS system. 2. De-installing the existing SPOTS Software Perform the steps in Section “De-installing SPOTS Software” in the Installation Guide of the SPOTS version to be upgraded. When performing this task, it must be guaranteed that SPOTS is not being used. 3. Installing patches Install the necessary Solaris patches (perform the steps in Section 4.4) and Oracle 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 an existing 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 onto the newly installed SPOTS system. 6. Installing Real-Time software (if applicable) If the SPOTS Real-Time functionality is desired, install the respective software as described in the Real-Time Installation Guide ([3]). 7. Setting the Oracle password Execute the SPOTS command setdbpwd with the -c parameter (as described in [1]), to change the Oracle password for all SPOTS Database connections. The used password length must be between 6 and 8 characters. 26 E200301-01-115-V10.0I-06
  28. 28. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 3.3 Data Migration 3.3.1 Data Migration overview The Data Migration procedure allows transferring data from an existing SPOTS installation (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 V10 Drop 4 (for a complete list refer to Table 1 in [1]), that also exist in the previous SPOTS version. • Historical SR6.0 and SR7.0 data migrated from Databases of previous SPOTS versions. 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 is produced on the new SPOTS installation, with the following path and name: $SPOTS_DIR/custom/reports/Old_CalcVars.dat The file syntax is similar to the SPOTS V10 Virtual Counters syntax; however, manual modifications to the measurement name, counter name and top object class 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 and V10. The data migration procedure involves two sets of actions, which must be executed at specific points of the overall procedures for Initial Installation (Section 3.1) or APS Upgrade (Section 3.2). These procedures specify when to perform data migration actions. 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 the regeneration steps; if any unrecoverable error occurs during its execution, the pre-vious environment could be re-established via a System Restore — refer to the description of System Backup Restore procedures of the SPOTS version to be migrated; 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 SPOTS database with partitioning option, it is required to configure the newly installed SDS before its first execution. During SPOTS installation, be alert to the warning E200301-01-115-V10.0I-06 27
  29. 29. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) instructing you how to configure the “sds.cfg” file. Any non-conformity may result in loss of PM detailed data. 28 E200301-01-115-V10.0I-06
  30. 30. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 3.3.2 Extracting data from an existing SPOTS system If the existing SPOTS system belongs to an earlier release of SPOTS V10, then a variant of the extraction procedure must be applied, using the dbArchive SPOTS command. 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 SPOTS version to be upgraded. Install SpotsDM package on the existing SPOTS system, on the same host as the SPOTS 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 to hold the archive contents. In case of space shortage, it is possible to partition the archive in several files, using the possibilities offered by dbArchive to selectively archive data. Consult [1], Section dbArchive for a precise description of the dbArchive command. E200301-01-115-V10.0I-06 29
  31. 31. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 3.3.3 Regenerating extracted data on the newly installed SPOTS system If the extraction step made use of the dbArchive SPOTS command (Section 3.3.2.1), then a corresponding variant of the regeneration procedure must be applied, using also the dbArchive SPOTS command. Refer to Section 3.3.3.1 below. 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 host as 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 command prompt: # $SPOTS_DIR/bin/dbArchive –i –a archive_dir_name Consult [1], Section dbArchive for a precise description of the dbArchive command. 30 E200301-01-115-V10.0I-06
  32. 32. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 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 including all SPOTS Client sessions. The following procedure can be used to stop all applicable services with a single command (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 a case, 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 force them to stop, with: $ /etc/init.d/initSpotsAll stop -force The following procedure can be used to stop all the applicable services with a specific command per service: Login as spots user Stop the dc_transfer daemon (applicable only on hosts with SAS installed and if support 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 and if 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 as follows: E200301-01-115-V10.0I-06 31
  33. 33. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) Wait a few seconds and then verify if RC FTP server is stopped, executing the following command: # ps –ef | grep oltrcftpserver.luc If it is already stopped (no output or simply a line referent to the grep command 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 a case, 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 force them 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 32 E200301-01-115-V10.0I-06
  34. 34. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 3.3.5 Installing SPOTS Data Migration package Install the Data Migration package, from the SPOTS distribution media, in the SPOTS system: 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 Data Migration 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. E200301-01-115-V10.0I-06 33
  35. 35. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 3.3.6 Dump existing data into tape(s) Execute the following steps, to copy the information to be migrated into tape(s): Login as root user. 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 the Save 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. 34 E200301-01-115-V10.0I-06
  36. 36. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 3.3.7 Recovering regenerated data from tape(s) In the newly installed SPOTS V10 Drop 4 system, execute the following steps, to load and adapt the information on tape(s): Login as root user. Insert the first recorded tape in the device. Verify that SPOTS_DIR environment variable is correctly set. It must point to the base 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 and Historical data, or enter “3” to regenerate only Historical data. The next step is applied only if data from Mobile-Core NEs have to be migrated. Modify the SPOTS names for the Mobile-Core NEs. NEs names, which previously included the NMS name, no longer use it. Consequently, the NMS name must be removed from all the NE names in order to be able to import traffic data correctly. The list of the Mobile-Core NEs (extracted from the “old” SPOTS Database) is displayed in a window, using the Text Editor that is set in the environment variable EDITOR. Only NEs with versions SR6.0 or later are displayed in the window. All the others are discarded, i.e. data is not regenerated. If there are no NEs that fulfil the mentioned criteria the window is not displayed. In the displayed Text Editor window, a line per NE with the following syntax is presented: old_NE_name new_NE_name where: old_NE_name E200301-01-115-V10.0I-06 35
  37. 37. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) is the NE name used in the “old” SPOTS version: the NMS name concatenated, via the character “@”, with the NE name as 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@lisbon1 omc1@lisbon2 omc1@lisbon2 For all Mobile-Core NEs, edit the field new_NE_name, replacing it by the “new” NE name. All NE names must be unique network wide. Example of the file contents after modification: omc1@lisbon1 lisbonA omc1@lisbon2 lisbonB Enter ‘return’ in the last line of the file. Otherwise, that line will not be considered and an error shall be returned indicating that line 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 longer use it. Consequently, the OMC-B name must be removed from all the BSC names in order to be able to import traffic data correctly. The list of the BSCs (extracted from the “old” SPOTS Database) is displayed in a window, using the Text Editor set in the environment variable EDITOR. Only BSCs with versions BR5.0 or later are displayed in the window. All the others are discarded, i.e. data is not regenerated. If there are no BSCs that fulfil the mentioned criteria the window is not displayed. In the displayed Text Editor window, a line with the following syntax is presented per BSC: current_BSC_name new_BSC_ name where: 36 E200301-01-115-V10.0I-06
  38. 38. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. current_BSC_name is the BSC name used in the “old” SPOTS version: the OMC-B name concatenated, via the character “_”, with the BSC name as configured in the BSC database. new_BSC_name is the BSC Symbolic Name as configured in the RC, for BR6.0 BSCs or is the BSC name stripped of its OMC-B name part, 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_BLC01D omcb01_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 being upgraded to BR6.0; the names of BSCs that remain in BR5.0/5.5 after the installation of SPOTS V10 Drop 4 should not change. If, later, they are upgraded to BR6.0, a specific procedure must be used to change their names at that time — this procedure is described in [1], Section changeObjNames. All NE names must be unique network wide. Example of the file contents after modification: omcb01_BLC01D Lisbon_1 omcb01_BLC02D Lisbon_2 Enter ‘return’ in the last line of the file. Otherwise, that line will not be considered and an error shall be returned indicating that line is missing. Save the updated file contents. The next step is applied only if data from GERAN NEs have to be migrated. If required, modify the SPOTS names for BTSMs, giving the corresponding symbolic names. The list of the BTSMs (extracted from the “old” SPOTS Database) is displayed in a window, using the Text Editor set in the environment variable EDITOR. Only BTSMs belonging to BSCs with versions BR5.0 or later are displayed in the window. All the others are discarded. If there are no BTSMs that fulfil the mentioned criteria the window is not displayed. E200301-01-115-V10.0I-06 37
  39. 39. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) In the displayed Text Editor window, a line with the following syntax is 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 — this field is initially set with current_BTSM_name. Example of the default contents, displayed in the Text Editor window: omcb01_BLC01D 20 20 omcb01_BLC02D 21 21 For each BTSM whose name has to be changed, edit the field BTSM_symb_name field, replacing it by the corresponding symbolic name. BTSMs belonging to BSCs that remain in BR5.0/5.5 will keep their names unchanged after the installation of SPOTS V10 Drop 4. If, later, they are upgraded to BR6.0, a specific procedure 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 Lapa omcb01_BLC02D 21 Benfica Save the updated file contents. The next step is applied only if data from GERAN NEs have to be migrated. If BTS identifiers (CGIs) are to be mapped to BTS symbolic names, it is necessary to prepare a file containing information to perform this mapping. The file shall be named symbFDN.bts.dat and shall contain one line per BTS to 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 their names unchanged after the installation of SPOTS V10 Drop 4. If, later, they are upgraded to BR6.0, a specific procedure must be used to change their names at that time — this procedure is described in [1], Section changeObjNames. If the OTS (OM Toolset) product is installed and the OTS Core Database is populated with symbolic naming information for the BTS objects to be 38 E200301-01-115-V10.0I-06
  40. 40. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. mapped, the above file can be created automatically by the getsymbname SPOTS application. To achieve this, perform the following sub-steps: Login as spots user 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 following contents: OTS Core_DB_user Core_DB_pwd where: Core_DB_user is the user name for the OTS Core DB service that provides external 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 subdirectory network/spots_ora_admin of the ORACLE_HOME directory, and append 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 Core DB. Core_DB_Oracle_SID is the “service id” of the Oracle Service above. Login as spots user Execute getsymbname, to retrieve information from the OTS Core Database: E200301-01-115-V10.0I-06 39
  41. 41. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) $ 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 Core Database only provides the symbolic name of the most recent CGI. The file can be edited manually after its creation, in order to add further CGI / symbolic name mappings. Note that it is possible to specify only one symbolic name per LAC/CI pair. Delete (or move to an .OTS extension) the file gsnl.dat that was created 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 file symbFDN.bts.dat is located. If a CGI cannot be mapped to a symbolic name by the migration procedure (due to “n” being chosen or due to a processing error), the string LAC_XXX_CI_YYY is saved in SPOTS as the BTS symbolic name (XXX and YYY are the LAC and CI values, respectively). While data is being extracted from tape(s), information will be logged in the file “$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 is completed. To start importing PM data files , wait until the following message 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. 40 E200301-01-115-V10.0I-06
  42. 42. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 3.3.8 Removing the SPOTS Data Migration package Carry out the following steps to remove the SpotsDM package: Login as root user. 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 Calcvars defined in old SPOTS versions are saved as SPOTS V10 Virtual Counters format. Correct saved old calcvars according the new SPOTS V10 Drop 4 measurements specification and append it to the SPOTS V10 “$SPOTS_DIR/custom/reports/virtual_entities.dat” file. File updated. E200301-01-115-V10.0I-06 41
  43. 43. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 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 omitted with the same results on behalf of simplicity. The following procedure can be used to start all applicable services with a single command (see below for a method that uses a specific command for each service): Login as root user. Give the following command: # /etc/init.d/initSpotsAll start The following procedure can be used to start all the applicable services with a specific command 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 if support 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 and if support for interworking with RC is activated): # /etc/init.d/initrcftp start 42 E200301-01-115-V10.0I-06
  44. 44. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 4 Installing the Operating System This chapter describes how to install the Solaris 8 Operating System, which is required 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 of how to install Microsoft Windows NT/2000/XP Operating System shall not be included. 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 from DVD. 4.1 Getting Started In order to start the installation procedure for Solaris 8 Operating System, verify that the necessary information is gathered, refer to Section 2.2. Then, execute the actions below: IMPORTANT NOTE: If you will install Fault Tolerance with disk mirroring 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, pressing the keys: “Stop” + “A” If you will install Fault Tolerance with disk mirroring or the last system installation 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 OS Installation 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 disk change. Change the booting device issuing the following command ok 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” E200301-01-115-V10.0I-06 43
  45. 45. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) Choose the location to place the Solaris installation software: Swap slices are usually erased at each reboot, so it is preferable to place the Solaris 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 slices exist answering: “n” Do not select any slice from swap slices list available in external disks answering: “none” Do not select any slice from general slices list available in external disks answering: “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 with Disk Mirroring then you must chose one of the machine internal disks. To do this, from the complete list of disks you can see 2 disks belonging to one of the disk controllers (the internal disks) and 6 disks belonging to the other disk controller (the external disks). It is possible to know to which controller a disk belongs by the number after the letter “c” in the disk id (ex: disk c2t1d0 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”. 44 E200301-01-115-V10.0I-06
  46. 46. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. Please wait… After copying Solaris installation software, the system will automatically reboot and installation will continue with system configuration. Getting started section completed. E200301-01-115-V10.0I-06 45
  47. 47. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 4.2 Configuring the System In this section, the installer provides all the information that is required for system configuration. After the Welcome screen is displayed, navigate through the Solaris Installer window sequence by means of the Next and Back buttons. If a XVR-500 graphics accelerator is installed in your system and you are trying to install Solaris 8, it is not possible to launch the graphical user interface for the installation. 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 based installation procedure are the same as in the GUI installation. Just follow the instructions on the screen and enter the required information as described in the current 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 your subnet. Enable IPv6: “Yes” Specify a default IP router (gateway) or let the Solaris installation program find it: “Specify One/Find One” Solaris installation program default is to find one. If a default router is to be 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: 46 E200301-01-115-V10.0I-06
  48. 48. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. “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 after the installation this question won’t be polled again, after every system reboot. Select the desired Proxy Server Configuration: “Direct Connection to the Internet / Use Proxy Configuration Below” 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 is correct, confirm it; otherwise, navigate through the Solaris Installer series of windows and correct the information. Please wait… The system is being configured with the chosen settings. After this, proceed with the next section. System configuration completed. E200301-01-115-V10.0I-06 47
  49. 49. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 4.3 Installing Solaris Most of the Solaris 8 installation is described in this section, including the actions to install the Solaris Software and the Solaris Documentation. The Solaris Web Start Installation Kiosk is displayed along with the Welcome to Solaris dialogue box. From this point on, you can click on any link listed in the Kiosk menu. Navigate through the sequence of dialogue boxes by means of the Next and Back buttons. If a XVR-500 graphics accelerator is installed in your system and you are trying to install Solaris 8, it is not possible to launch the graphical user interface for the installation. That’s why you have to configure (Section 4.2) and install (current section) Solaris via a text based user interface. The dialogs in this text based installation procedure are the same as in the GUI installation. Just follow the instructions on the screen and enter the required information as described in the current 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 program detects that the system is upgradeable): “Initial Install” Select Type of Install: “Custom Install” No additional Software selections are required by SPOTS software, besides the default. 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 it isn’t considered necessary de-select all products. Install additional third-party or other software products: 48 E200301-01-115-V10.0I-06
  50. 50. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. “None” Applicable on UltraSparc-II platforms only. Select 64-Bit Support (software will be 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 or unnamed 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 (in MB). Take into consideration the intended SPOTS configuration that will be installed in the system. Different SPOTS configurations imply different hard-disk requirements and different file systems organization. If Fault tolerance with disk mirroring will be installed then it is necessary to fill the “Information to fill during OS installation” on Annex 5. Verify the information presented in the installation summary. If information is 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 are displayed in brackets above the top progress bar. The status of the entire installation is shown on the bottom progress bar. The actual installation time depends on the software you chose to install, the reallocation of any space if needed and the drive performance. The Installation Summary dialogue box is presented. For further details about important 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 when ready. Installing, please wait… E200301-01-115-V10.0I-06 49
  51. 51. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) The Installation Summary dialogue box is presented. For further details about important events occurred during installation use the Details… button. 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, proceed with Solaris 8 Documentation installation otherwise continue after Solaris 8 Documentation installation completion. 50 E200301-01-115-V10.0I-06
  52. 52. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. Insert the Solaris 8 2/02 Documentation CD and start the installation when ready. Installing, please wait … The Installation Summary dialogue box is presented. For further details about important events occurred during installation use the Details… button. The Solaris 8 2/02 Documentation CD is ejected. Installation of the Solaris 8 Documentation completed. System reboot is automatically initiated. Login as root user. If a XVR-500 graphics accelerator is installed in your system, after the reboot of the system you have the console login only, and therefore the next step cannot be performed 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 to fill after OS installation” on Annex 5. Installation of the Solaris 8 completed. E200301-01-115-V10.0I-06 51
  53. 53. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 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 8 Recommended Patch Cluster distributed with the SPOTS CD. Login as root user. 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 not necessarily means that an error occurred, refer to the installation log file and check if 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 some additional software patches, specific to your hardware platform, may be required. For further information, please refer to the Product Notes that accompany your system. Installation of the Solaris 8 patches completed. If a XVR-500 graphics accelerator is installed in your system, install the driver for the 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 52 E200301-01-115-V10.0I-06
  54. 54. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. “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 or software installation or configuration). E200301-01-115-V10.0I-06 53
  55. 55. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 5 Fault Tolerance with Disk Mirroring To improve SPOTS availability Fault Tolerance with Disk Mirroring can be used. This chapter describes how to install, maintain and uninstall Fault Tolerance with Disk Mirroring. If disk mirroring will not be installed, proceed with Oracle Software Installation on Chapter 6. Fault Tolerance with Disk Mirroring consists on having the contents of one disk replicated on other disk. Disk mirroring improves data availability. If one of the mirrored disks fails, the information can be accessed on the other disk. Solstice DiskSuite Software3 is used to manage the mirroring. Setup Tasks To improve SPOTS availability Fault Tolerance with Disk Mirroring it is necessary to execute 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 Tasks After the setup tasks have been executed, the mirroring status is checked periodically by the system. If any mirroring failure is detected, the root user will receive a failure notification via email. Alternatively, the mirroring status can also be checked on user request. 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 Tasks When Fault Tolerance with Disk Mirroring is no longer needed, it can be removed executing the two following un-installation tasks. • The first task is to remove the mirroring configuration as described in Section 5.3.1 • The second task is to uninstall DiskSuite Software as described in Section 5.3.2 3 For more information about Solstice DiskSuite Software refer to http://docs.sun.com 54 E200301-01-115-V10.0I-06
  56. 56. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. 5.1 Setup Tasks To configure the system for Fault Tolerance with Disk Mirroring it is needed to execute the 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 to the mirroring configuration. The Solstice DiskSuite 4.2.1 required packages are distributed along with the SPOTS SW distribution media. IMPORTANT NOTE: Before installing DiskSuite Software, all required patches, on Section 4.4, must be installed and the disk partition information must be stored in Annex 5. Login as root user Insert the SPOTS Server and Solaris Client distribution media on the appropriate device Execute the following shell commands: # cd /cdrom/cdrom0/diskman/disksuite # pkgadd -d . SUNWmdx SUNWmdr SUNWmdu SUNWmdg The packages installation order is mandatory. Confirm all polls with “y”. 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: E200301-01-115-V10.0I-06 55
  57. 57. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) 1. System disk mirroring for Sun Blade systems with 2 internal disks and 6 external disks. The mirroring configuration for this hardware configuration is described in Section 5.1.2.1. 2. System and Database disks mirroring for Sun Fire systems with 12 internal disks. The mirroring configuration for this hardware configuration is described in 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 Blade systems with 2 internal disks and 6 external disks. Login as root user This login must be done in the workstation and must be a root login (do not become 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 step again 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 the following file systems: /replica1 /replica2 /replica3 /replica4 /var/opt /var_opt_mirror /export/home /home_mirror /opt_mirror /swap_mirror /root_mirror Insert the SPOTS Server and Solaris Client distribution media on the appropriate device Execute the following shell commands: # cd /cdrom/cdrom0/diskman/OSandBRmirror # ./runstep 1 # reboot Wait for the system to reboot. Login as root user Execute the following shell commands: # cd /cdrom/cdrom0/diskman/OSandBRmirror 56 E200301-01-115-V10.0I-06
  58. 58. Installation Guide (SPOTS V10 Drop 4) Siemens S.A. # ./runstep 2 The alternate boot is present in the output of last step. Note it down, filling the corresponding item of section “Information to fill after disk configuration with DiskSuite”, in Annex 5. Make sure that all information required in this section is 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 the following 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 for Sun Fire systems with 12 internal disks. Login as root user This login must be done in the workstation and must be a root login (do not become 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 step again 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 the following filesystems: /replica1 /replica2 /replica3 /replica4 /replica5 /replica6 /replica7 /replica8 /replica9 /replica10 /replica11 /replica12 /spots_db1 /spots_db1_mirror /spots_db2 E200301-01-115-V10.0I-06 57
  59. 59. Siemens S.A. Installation Guide (SPOTS V10 Drop 4) /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 Insert the SPOTS Server and Solaris Client distribution media on the appropriate device Execute the following shell commands: # cd /cdrom/cdrom0/diskman/OSandBRandDBmirror # ./runstep 1 # reboot Wait for the system to reboot. Login as root user 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 configuration with 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 the following commands: # cd / eject cdrom Disk configuration successfully completed Proceed with Oracle Software Installation on Chapter 6 58 E200301-01-115-V10.0I-06

×