Copie de Nr81pl2 1350 Mig Ed06

All rights reserved.
Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel
1350 Management Suite Migration Guide NR8.1PL2
Supprim : 9
6 ED
15.09.2009 DATE
RELEASED
CHANGE NOTE
F.Casasole M.Ierace
APPRAISAL AUTHORITY
E.Biscuola N.Ajani
ORIGINATOR
ED Optics
RELEASED
8DG 31466 AAAA TCZZA
1/15715715 7157
SUMMARY
1 INTRODUCTION ....................................................................................................................... 8 1.1 GENERAL INFORMATION....................................................................................................................... 8 1.2 HANDBOOK APPLICABILITY ................................................................................................................... 8 1.3 PRODUCTRELEASE HANDBOOKS ......................................................................................................... 9 1.3.1 Handbooks related to the specific software application ........................................................... 9 1.3.2 NR 8.1 Related Handbooks ..................................................................................................... 9 1.4 REGISTERED TRADEMARKS................................................................................................................ 10 1.5 CONVENTIONS................................................................................................................................... 10 1.6 OVERVIEW ........................................................................................................................................ 11 1.7 DOCUMENT OVERVIEW ...................................................................................................................... 11 1.8 WHATS IN THIS DOCUMENT ................................................................................................................ 12 2 MIGRATION PROJECT AND PRODUCT INFORMATION.................................................... 13
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4
2.1 RESTRICTIONS AND PRECONDITIONS .................................................................................................. 13 2.1.1 Mandatory Patches ................................................................................................................ 13 2.1.2 RM and BM-ETH DB schema check on the starting NR........................................................ 13 3 3.1.1 3.1.2 3.1.3 3.1.4 4 MIGRATION IN A COMPLEX NETWORK ............................................................................. 16 One Shot ISE Migration.......................................................................................................... 16 Stepped ISE Migration ........................................................................................................... 16 One Shot Migration with Spare .............................................................................................. 17 Stepped Migration with Spare ................................................................................................ 17 IN SYSTEM EVOLUTION (ISE).............................................................................................. 20
4.1 PREPARATION GUIDE LINES ............................................................................................................... 21 4.1.1 Evaluate the ISE prerequisites............................................................................................... 21 4.1.2 Perform the System Backup .................................................................................................. 21 4.1.3 NMS SWPDESC, OS-Conf and Install Wizard Upgrade ....................................................... 21 4.1.4 Predispose a temporary file system for Data Export.............................................................. 21 4.1.5 Predispose the system for the NR8.1PL2 software. .............................................................. 22 4.1.6 Install NR8.1PL2 software...................................................................................................... 24 4.1.7 Customize OS-Kernel............................................................................................................. 27 4.1.8 Customize Instances Subjected to ISE .................................................................................. 28 4.1.9 Preparing for 1354RM Instance Configuration....................................................................... 31 4.1.10 Export and Import of System Configuration ........................................................................... 31 4.1.11 Configure Instances Subjected to ISE ................................................................................... 33 4.1.12 Create DB schema reference files ......................................................................................... 33 4.1.13 Perform the Application Backup............................................................................................. 34 4.1.14 Export, Import, and Conversion of Instances Subjected to ISE Migration ............................. 34 4.1.15 Shutdown the database of the new NMS subjected to ISE Migration ................................... 35 4.1.16 Restoring 1354RM DB Initialization file.................................................................................. 35 4.2 ONE SHOT ISE GUIDE LINES ............................................................................................................. 37 4.2.1 Shutdown running application subjected to ISE Migration..................................................... 37 4.2.2 De-Activate previous OS-Kernel ............................................................................................ 37 4.2.3 Activate NR8.1PL2 OS-Kernel ............................................................................................... 37 4.2.4 Resume Predispose. .............................................................................................................. 38 4.2.5 Update Poseidon License ...................................................................................................... 39 4.2.6 Upgrade Software Platform .................................................................................................... 39 4.2.7 Customize GoGlobal-UX ........................................................................................................ 39 4.2.8 NMS Integration ..................................................................................................................... 40 4.2.9 Startup NMS applications & verify behaviour......................................................................... 40 4.2.10 1354RM NE and alarm synchronization................................................................................. 40
ED
RELEASED
Optics
2/157
4.2.11 1354RM audit......................................................................................................................... 41 4.2.12 1354BMETH align up ............................................................................................................. 41 4.2.13 Alarm Federation configuration.............................................................................................. 42 4.2.14 1354RM pre-OTN to OTN migration ...................................................................................... 42 4.2.15 Remove Obsolete Data and Software ................................................................................... 42 4.3 STEPPED ISE GUIDE LINES ............................................................................................................... 45 4.3.1 Shutdown running application subjected to ISE Migration..................................................... 45 4.3.2 De-integration......................................................................................................................... 45 4.3.3 De-Activate previous OS-Kernel ............................................................................................ 45 4.3.4 Activate NR8.1PL2 OS-Kernel ............................................................................................... 46 4.3.5 Resume Predispose............................................................................................................... 47 4.3.6 Update Poseidon License ...................................................................................................... 47 4.3.7 Upgrade Software Platform.................................................................................................... 47 4.3.8 Customize GoGlobal-UX........................................................................................................ 48 4.3.9 Customize old client instances............................................................................................... 48 4.3.10 Remote client instances upgrade........................................................................................... 50 4.3.11 NMS Integration ..................................................................................................................... 50 4.3.12 Startup NMS applications & Verify Behaviour........................................................................ 51 4.3.13 1354RM NE and alarm synchronization ................................................................................ 51 4.3.14 1354RM Audit ........................................................................................................................ 51 4.3.15 1354BMETH align up ............................................................................................................. 52 4.3.16 Alarm Federation configuration.............................................................................................. 52 4.3.17 1354RM pre-OTN to OTN migration ...................................................................................... 53 4.3.18 Remove Obsolete Data and Software ................................................................................... 53 5 MIGRATION WITH SPARE SYSTEM .................................................................................... 56
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel
5.1 ONE SHOT MIGRATION WITH SPARE SYSTEM...................................................................................... 57 5.1.1 Obtain source system variables............................................................................................. 57 5.1.2 Install hp-ux on target system ................................................................................................ 57 5.1.3 Install & Predispose the system for the NR8.1PL2 software. ................................................ 58 5.1.4 Install the application software on target system ................................................................... 59 5.1.5 Customize the application software on target system ........................................................... 62 5.2 STEPPED MIGRATION WITH SPARE SYSTEM ........................................................................................ 66 5.2.1 Obtain source system variables............................................................................................. 66 5.2.2 Install hp-ux on target system ................................................................................................ 66 5.2.3 Install & predispose for old client instances ........................................................................... 67 5.2.4 Install & predispose the system for the NR8.1PL2 software.................................................. 70 5.2.5 Install the application software on target system ................................................................... 71 5.2.6 Customize the application software on target system ........................................................... 75 5.3 MIGRATION WITH SPARE SYSTEM COMMON PROCEDURE .................................................................... 78 5.3.1 NMS Master System Configuration........................................................................................ 78 5.3.2 Create DB schema reference files ......................................................................................... 78 5.3.3 Install migration tools ............................................................................................................. 79 5.3.4 Data Export from Source and Import to Target System......................................................... 79 5.3.5 Data Conversion .................................................................................................................... 80 5.3.6 System Swap ......................................................................................................................... 80 6 VERIFY PRE-CONDITIONS ................................................................................................... 85
6.1 CHECK SOFTWARE REQUIREMENTS .................................................................................................... 85 6.1.1 Identify the current software................................................................................................... 86 6.1.2 Identify the target software..................................................................................................... 89 6.2 CHECK HARDWARE REQUIREMENTS ................................................................................................... 90 6.3 CHECK SOFTWARE REQUIREMENTS.................................................................................................... 92 7
1AA 00014 0004 (9711) A4
PLATFORM UPGRADE ......................................................................................................... 93
7.1 UPGRADE PLATFORM TO THE LATEST OS-CONF PATCH ...................................................................... 93
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
3/157
8 9 10 11 12 13 14 15 16 17 18 19 20 21
APPENDIX A: SUMMARY TABLES ...................................................................................... 95

APPENDIX B: SW PACKAGES ............................................................................................. 99 APPENDIX C: REQUIRED DISK SPACE .......................................................................... 102 APPENDIX D: NMS SWPDESC, OS-CONF AND INSTALL WIZARD UPGRADE .......... 104 APPENDIX E: DATA EXPORT/IMPORT............................................................................ 106 APPENDIX F: 1353NM DATA CONVERSION................................................................... 113 APPENDIX G: 1354RM DATA CONVERSION .................................................................. 114 APPENDIX H: 1354BM-ETH DATA CONVERSION.......................................................... 138 APPENDIX I: 1354RM SEC (SECURITY) DATABASE ADAPTATION ............................ 143 APPENDIX J: CUSTOM WARNING AND ERROR............................................................ 146 APPENDIX K: NEW DISK REQUEST................................................................................ 148 APPENDIX L: RETRIEVE HP-UX SYSTEM INFORMATION ............................................ 150 APPENDIX M: 1354RM PRE-OTN TO OTN MIGRATION................................................. 151 APPENDIX N: TROUBLESHOOTING................................................................................ 154
ED
RELEASED
Optics
4/157
1. TABLE
Table 1. Table 2. Table 3. Table 4. Table 5. Table 6. Table 7. Table 8. Table 9. Table 10. Table 11. Table 12. Table 13. Table 14. Table 15. Table 16. Table 17.
Processes for 1354RM Database...................................................................................................36 Upgrade/ISE - Software Packages and Data Instances.................................................................95 Upgrade/ISE - NMS Instance Information ......................................................................................96 NR7.4 NMS version for Install_Wizard ...........................................................................................97 1354RM Process Configuration......................................................................................................97 1353NM Process Configuration......................................................................................................98 Upgradeable NMS software............................................................................................................99 NMS Versions from NR7.1 to NR 7.4 ...........................................................................................100 NMS Version from NR 7.1D/7.2 to NR 7.4 ..................................................................................100 NMS Version from NR7.3 to NR7.4 ............................................................................................100 NMC keys ...................................................................................................................................101 NMS Specific Administration Users ............................................................................................101 Disk requirements for NMS Software for NR8.1 PL2 .................................................................102 Disk requirements for NMS Software for NR8.1 PL2 .................................................................103 Oracle Not Relevant Errors In Database Conversion.................................................................140 1353NM Useless Custom Error and Warning messages ...........................................................146 1354RM Useless Custom Error and Warning messages ...........................................................147
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
5/157
A. FIGURES
Figure 1 - Migration Starting configuration...................................................................................................... 19 Figure 2 - Migration Target configuration........................................................................................................ 19 Figure 3 - Upgrade System, Instance, List window ........................................................................................ 29 Figure 4 - ISE Customize Parameter Definition window................................................................................. 30 Figure 5 - Upgrade Custom log window. ........................................................................................................ 31 Figure 6 - Upgrade System, Instance, List window ........................................................................................ 49 Figure 7 - Upgrade System, Instance, List window ........................................................................................ 63 Figure 8 - Customize Parameter Definition window........................................................................................ 64 Figure 9 - Upgrade Custom log window. ........................................................................................................ 65 Figure 10 - Upgrade System, Instance, List window ...................................................................................... 76 Figure 11 - Customize Parameter Definition window...................................................................................... 76 Figure 12 - Upgrade Custom log window. ...................................................................................................... 77 Figure 13 - Prerequisite System Instances List Window ................................................................................ 87 Figure 14 - Export GUI window..................................................................................................................... 107 Figure 15 - Import GUI window ..................................................................................................................... 108 Figure 16 - Operator in SEC graphical interface ........................................................................................ 143 Figure 17 - Remove of the profile with the same name of Operator .......................................................... 144 Figure 18 - Operator profile list................................................................................................................... 144 Figure 19 - Disks configuration Example ...................................................................................................... 149
ED
RELEASED
Optics
6/157
HISTORY
Edition Ed02 It05 = Ed03 Internal Ed04 Ed04 = Internal Ed05 Ed05 = internal ed09
Date Oct 2008 Nov 2008 Nov 2008
Notes Third Edition internal use only (R&D) Forth Edition
March 2009
Fifth Edition Inclusion Patch 5 BM ETH and new conversion scripts for BM.
Ed06 = internal ed10
September 2009
Sixth edition
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
7/157
1 1.1
INTRODUCTION General Information

WARNING
ALCATEL makes no warranty of any kind with regards to this manual, and specifically disclaims the implied warranties of merchantability and fitness for a particular purpose. ALCATEL will not be liable for errors contained herein or for damages, whether direct, indirect, consequential, incidental, or special, in connection with the furnishing, performance, or use of this material NOTICE The product specification and/or performance levels contained in this document are for information purposes only and are subject to change without notice. They do not represent any obligation on the part of ALCATEL. COPYRIGHT NOTIFICATION The technical information of this manual is the property of ALCATEL and must not be copied, reproduced or disclosed to a third party without written consent.
1.2
Handbook applicability
This handbook applies to the following productreleases: PRODUCT 1350 PRODUCT 1350 N.B.: RELEASE 8.1 VERSION (N.B.) 8.1 ANV P/N ANV P/N
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
Handbooks relevant to software applications (typically the Operators Handbooks) are not modified unless the new software version distributed to Customers implies man-machine interface changes or in case of slight modifications not affecting the understanding of the explained procedures. Moreover, should the screen prints included in the handbook contain the productreleases version marking, they are not replaced in the handbooks related to a subsequent version, if the screen contents are unchanged.
ED
RELEASED
Optics
8/157
1.3
Productrelease handbooks
The list of handbooks given here below is valid on the issue date of this Handbook and can be changed without any obligation for ALCATEL to update it in this Handbook. Some of the handbooks listed here below may not be available on the issue date of this Handbook.
The standard Customer Documentation in the English language for the equipment whose productrelease version is stated in para.1.2 on page 7 consists of the following handbooks:
1.3.1 Handbooks related to the specific software application

REF HANDBOOK ANV Part No. THIS HANDBOOK
[1] [2]
1350 Rel8.1 Installation Guide 1350 Rel8.1 Administration Guide
1.3.2 NR 8.1 Related Handbooks

REF HANDBOOK ANV Part No. THIS HAND BOOK
[3]
1350 Rel. 7.1D/7.2/7.3/7.4/8.1 OND Network Management Configuration Guide 1359HA OS-Cluster 7.1 Installation and Administration Guide 1354BMETH 7.3.0.5 Administration Guide 1354BMETH R7.3 Operators Handbook 1353NM 7.3 Administration Guide 1354RM 7.4 Administration Guide 1359HA OS-Resilience 7.1.1 Administration Guide 1355VPN 5.0 Administration Guide 1359IOO 5.2 Administration Guide 1359ISN 5.0 Administration Guide
3AL 88851 AAAA
[4]
3AL 88127 BAAA
[5] [6] [7] [8] [9] [10] [11] [12]
3AL 86503 BAAA 3AL 86503 AAAA 3AL 89082 BAAA 3AL 61112 BAAA 3AL 88129 BAAA 3AL 72136 CAAA 3AL 88346 AAAA 3AL 88219 AAAA
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
9/157
1.4
1. 2. 3. 4. 5.
Registered Trademarks
UNIX is a registered trademark of UNIX System Laboratories in the U.S.A. and other countries. OSF/Motif is a trademark of the Open Software Foundation. HP is a registered trademark of Hewlett-Packard Corporation. HP9000 and HP-UX are trademarks of Hewlett-Packard Corporation. ORACLE is a registered trademark of Oracle Corporation.
1.5
Conventions
The following conventions are used in this manual: [Enter] Courier Bold Courier Courier <data> Reference A key name is shown between square brackets to indicate that you press a named key on the keyboard. Courier font included in a grey box is uses to indicate the output produced by the system or data that you can find. Bold courier indicates information that you must enter from the keyboard. Courier indicates system prompts. Arial shown between angle brackets means that these data depending by the particular instance of the system. It must be substituted with the correct data. Double quotation Arial italic means a cross reference.
For semplicity, throughtout the guide 1 will be used as instance id. Obviously substitute it with the real instance id.
ED
RELEASED
Optics
10/157
1.6
Overview Audience
This document describes the technical process to migrate some1 OND Network Management application running on HP platform to Network Release 8.1. The intended readers are: 1. Alcatel Product Managers 2. Alcatel Project Leaders 3. Alcatel Field Engineers 4. Alcatel employees who have to plan or to execute migration tasks This document was written with the customer in mind but anyhow, it contains Alcatel proprietary information and shall not be released to customers without prior adaptation to customer needs and skills.
Scope
The document contains the technical description of the steps needed to successfully update a TMN application: 1. In System Evolution (ISE): this approach allows updating the running application installing on a separate installation tree the target SW; during this phase the application can be up and running. Note: this document does not describe your particular migration, but should only serve as a guideline for writing your customized handbook. It is not allowed to use this guideline as your customer specific handbook, without needed customizations.
1.7
Document Overview
This document provides the guidelines to upgrade an Alcatel TMN system installed with one of the following configurations to NR8.1PL2 network release: Network Release Mandatory NR7.1T PL1 NR7.1D/7.2 PL2 NR7.3 NR7.4
1
Alcatel Software Components. Any combination of IM or USM or both 1353NM 7.0.13, 1354RM 7.1.42 1353NM 7.0.13, 1354RM 7.1.80, 1354BMETH 7.1.1 P14 2, 1354BMETH 7.3 P1 1353NM 7.0.14, 1354RM 7.3, 1354BMETH 7.1.1 P14 1353NM , 1354RM , 1354BMETH
OS-Kernel 7.1.1 OS-Kernel 7.1.2
OS-Kernel 7.1.2 OS-Kernel 7.1.2
The upgrade is supported only the version specified in Upgradeable NMS software table. The 1354BM ETH is supported only starting with NR7.1D/7.2 PL1.
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
11/157
Any software configuration not included in this table cannot be object of upgrade or migration with this document.
1.8
Whats in this document
This document includes the following topics: 1. Chapter 1 Introduction Document introduction with convention and short chapter descriptions. 2. Chapter 2 Migration project and product information 3. Chapter 3 Migration In A Complex Network 4. Chapter 4 In System Evolution (ISE) It provides the guidelines to upgrade the software on the running system, and switch over to new software when ready. It has been design to reduce the downtime and the system freeze time, and the involved hardware resource. 5. Chapter 5 Migration With Spare System 6. Chapter 6 Verify Pre-conditions This chapter describes how to identify the installed software and verify if the migration precondition are met. 7. Chapter 7 Platform Upgrade It describes how upgrade HP-UX and third party software on the system. 8. Appendixes The appendixes include some common procedure in migration.
ED
RELEASED
Optics
12/157
1AA 00014 0004 (9711) A4
2
MIGRATION PROJECT AND PRODUCT INFORMATION
This chapter provides some hints about the operational aspects of the migration project and some product info like precondition and restrictions
2.1
Restrictions and Preconditions
Hereafter the list of restrictions and precondition to be fulfilled before the migration can start.
2.1.1 Mandatory Patches
NR8.1PL2 DR4 composition + 1354RM 7.5.0.1-P16 + 1354BMETH 8.1.5.3-P6RP1 must be installed on the target system in order to run the migration. NR8.1 PL2 DR4 composition foresees, in addition to the SW delivered via DVD also two additional patches, OS-KERNEL 7.1.2-RP19.6 and 1354RM 7.5.0.1-P15.
2.1.2 RM and BM-ETH DB schema check on the starting NR
To highlight possible differences in RM and BM-ETH db schema of the target NR that already exist in the db schema of the starting NR it is strongly recommended to execute db schema check also on the starting NR, using the procedure detailed hereafter.The procedure can be executed anytime before the migration. If relevant differences are discovered please ask for support before starting the migration. The procedure must be executed on a spare machine installed with the same software/patch of the customer machine. Do not use customer machines! 2.1.2.1 Create DB schema reference files
After creating new databases on the spare machine execute the following procedure. If you are checking 1354RM db schema: 1. Login on the spare machine as user snml 2. If necessary startup 1354RM database: ... ... ... ... $ $ $ $ cd /usr/Systems/1354RM_1 . ./.snmlrc cd ORACLE/databases/dbnml/etc start_db
3. Get a snapshot of the database: ... $ mkdir /alcatel/DEPOT/NR<source NR>_RM_DB_Ref (if you get an error execute, as root: chmod 777 /alcatel/DEPOT e repeat the command) ... $ chmod 777 /alcatel/DEPOT/NR<source NR>_RM_DB_Ref ... $ cd /usr/Systems/1354RM_1/ORACLE/script/ ... $ ./MIB_Contents get /alcatel/DEPOT/NR<source NR>_RM_DB_Ref 4. Stop 1354RM database:
1AA 00014 0004 (9711) A4
... $ cd /usr/Systems/1354RM_1 ... $ cd ORACLE/databases/dbnml/etc ... $ stop_db
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
13/157
If you are checking 1354BMETH db schema:

1. Login on the spare machine as user bmml 2. If necessay startup 1354BMETH database: ... ... ... ... $ $ $ $ cd /usr/Systems/1354BMETH_1 . ./.bmmlrc cd ORACLE/databases/dbnml/etc start_db
3. Get a snapshot of the database: ... $ mkdir /alcatel/DEPOT/NR<source NR>_BMETH_DB_Ref (if you get an error execute, as root: chmod 777 /alcatel/DEPOT e repeat the command) ... $ chmod 777 /alcatel/DEPOT/NR<source NR>_BMETH_DB_Ref ... $ cd /usr/Systems/1354BMETH_1/ORACLE/script/ ... $ ./MIB_Contents get /alcatel/DEPOT/NR<source NR>_BMETH_DB_Ref 4. Stop 1354BMETH database: ... $ cd /usr/Systems/1354BMETH_1 ... $ cd ORACLE/databases/dbnml/etc ... $ stop_db
2.1.2.2
DB Backup/Restore
Backup (or export) RM and/or BMETH db on the customer machine and restore (or import) it on the spare machine.
2.1.2.3
Check DB schema
If you are checking 1354RM db schema: 1. Login on the spare machine as user snml ... ... ... ... ... $ $ $ $ $ cd /usr/Systems/1354RM_1 . ./.snmlrc sqlplus $NXNL_DATABASE mkdir /alcatel/DEPOT/NR<source NR>_RM_DB_Cust chmod 777 /alcatel/DEPOT/NR<source NR>_RM_DB_Cust
2. Get a snapshot of the database: ... $ cd /usr/Systems/1354RM_1/ORACLE/script/ ... $ ./MIB_Contents get /alcatel/DEPOT/NR<source NR>_RM_DB_Cust 3. Compare the current DB schema with the expected one (one only line): ... $ ./MIB_Contents compare /alcatel/DEPOT/NR<source NR>_RM_DB_Ref /alcatel/DEPOT/NR<source NR>_RM_DB > /alcatel/DEPOT/NR<source NR>_RM_DB_Diff.log 4. Check the log file just created: ... $ vi /alcatel/DEPOT/NR<source NR>_RM_DB_Diff.log If you find any significant difference please contact TEC Italy before starting the migration.
1AA 00014 0004 (9711) A4
If you are checking 1354BMETH db schema:
ED
RELEASED
Optics
14/157
1. Login on the spare machine as user bmml ... ... ... ... ... $ $ $ $ $ cd /usr/Systems/1354BMETH_1 . ./.bmmlrc sqlplus $NXNL_DATABASE mkdir /alcatel/DEPOT/NR<source NR>_BMETH_DB chmod 777 /alcatel/DEPOT/NR<source NR>_BMETH_DB
2. Get a snapshot of the database: ... $ cd /usr/Systems/1354BMETH_1/ORACLE/script/ ... $ ./MIB_Contents get /alcatel/DEPOT/NR<source NR>_BMETH_DB 3. Compare the current DB schema with the expected one (one only line): ... $ ./MIB_Contents compare /alcatel/DEPOT/NR<source NR>_BMETH_DB_Ref /alcatel/DEPOT/NR<source NR>_BMETH_DB > /alcatel/DEPOT/NR<source NR>_BMETH_DB_Diff.log 4. Check the log file just created: ... $ vi /alcatel/DEPOT/NR<source NR>_BMETH_DB_Diff.log If you find any significant difference please contact TEC Italy before starting the migration.
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
15/157
MIGRATION IN A COMPLEX NETWORK

The 1350 Management Suite is a hierarchical architecture, where many systems can operate together to perform their job. Apply a migration procedure in this environment requires to have a clear picture of the machine relationship, and how proceed in the upgrade on different machine. When more than one system is involved in migration, it can be performed in two ways: 1. One Shot: all NMSs are migrated at the same time. This approach is mandatory for cohosted Master NMSs. 2. Stepped: first 1354RM and 1354BMETH are migrated, then 1353NM Warning! In any case it is mandatory to migrate 1354RM and 1354BMETH at the same time or at least to ensure that 1354BMETH and 1354RM do not communicate in the temporary period between 1354BMETH migration and 1354RM one. A way to achieve it is, for example, not to start the mediator. Warning! During stepped migrations (with Spare or ISE) always migrate remote client instances after their respective master instance. Not doing so can have disruptive effects on the system!
3.1.1 One Shot ISE Migration

If you have to upgrade from the configuration shown in Figure 1 - to the one shown in Figure 2 - you have to proceed this way: 1. Start the migration on all system at once. 2. Predispose for the final configuration. 3. Install the foreseen software. 4. Customize the off line Master and Client instances of the new software version. 5. Perform Master instances System configuration, data export/import and conversion. 6. Deactivate the source NR and activate the target one. 7. Execute the integration. 8. Start the system. 9. Remove old instances and software.
3.1.2 Stepped ISE Migration

If you have to upgrade from the configuration shown in Figure 1 - to the one shown in Figure 2 - you have to proceed this way: 1. Start with BM-ETH/RM server. a. Predispose the system for the target configuration (new software and new NMS instances) b. Install the entire software requested (BM-ETH 8.1.5, RM 7.4.9 and NM 7.4.5). c. Customize the RM 7.4.9 and BM-ETH 8.1.5 Master instances.
d. Perform Master instances System configuration, data export/import and conversion. e. Deactivate the source NR and activate the target one.
ED
RELEASED
Optics
16/157
f.
Customize each NM 7.0 Client in the target NR.
g. Execute the integration.

h. Start the system. 2. For each 1353NM Master: a. Predispose the system for the target configuration (New software and new NMS instances) b. Install the entire software requested (NM 7.4.5). c. Customize the NM 7.4.5 Master instance.
d. Perform Master instances System configuration, data export/import and conversion. e. Remove integration of NM 7.0 Master from RM 7.4.9/BM-ETH 8.1.2 f. Deactivate the source NR and activate the target one.
g. Decustom NM 7.0 Client instance on RM 7.4.9/BM-ETH 8.1.2 h. Custom NM 7.4.5 Client on RM 7.4.9/BM-ETH 8.1.2 i. j. Execute the integration. Start the system.
3. Only when all the NM 7.0 Clients have been upgraded to 7.4.5 you can remove old instances and software on all the machines.
3.1.3 One Shot Migration with Spare

If you have to upgrade from the configuration shown in Figure 1 - to the one shown in Figure 2 - you have to proceed this way: Install the spare machines. Perform data export/import and conversion. Swap the system. Start the system.
3.1.4 Stepped Migration with Spare

If you have to upgrade from the configuration shown in Figure 1 - to the one shown in Figure 2 - you have to proceed this way: a. Start with BM-ETH/RM server. a. Install target Os-Conf. b. Install old SWPDESC and Install_Wizard. c. Predispose for NM 7.0 SWP and Client Instance.
d. Install NM 7.0 software. e. Upgrade to target SWPDESC and Install_Wizard. f. Predispose the system for the target configuration (new software and new NMS instances)
g. Install the entire software requested (BM-ETH 8.1.5, RM 7.4.9 and NM 7.4.5). h. Customize the RM 7.4.9 and BM-ETH 8.1.5 Master instances. i.
1AA 00014 0004 (9711) A4
Perform Master instances System configuration, data export/import and conversion. Customize each NM 7.0 Client in the target NR.
j.
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
17/157
k. l.
Execute the integration.

Start the system.
1. For each 1353NM Master: 1. Install the spare machine. 2. Predispose the system for the target configuration (New software and new NMS instances) 3. Install the entire software requested (NM 7.4.5). 4. Customize the NM 7.4.5 Master instance. 5. Perform Master instances System configuration, data export/import and conversion. 6. Remove integration of NM 7.0 Master from RM 7.4.9/BM-ETH 8.1.2 7. Switch over to NM 7.4.5 Master. 8. Decustom NM 7.0 Client instance on RM 7.4.9/BMETH 8.1.2 9. Custom NM 7.4.5 Client on RM 7.4.9/BMETH 8.1.2 10. Execute the integration. 11. Start the system. 2. Only when all the NM 7.0 Clients have been upgraded to 7.4.5 you can remove old instances and software on all the machines.
Mise en forme : Puces et numros
ED
RELEASED
Optics
18/157
1AA 00014 0004 (9711) A4
Starting scenario
BM-ETH 7.3 Master ID 1 RM 7.1 Master ID 1 NM 7.0 Client ID 1 NM 7.0 Client ID 2
NM 7.0 Master ID 1
NM 7.0 Master ID 2
Figure 1 - Migration Starting configuration
Target scenario
BM-ETH 8.1.5 Master ID 1 RM 7.4.9 Master ID 1 NM 7.4.5 Client ID 1 NM 7.4.5 Client ID 2
NM 7.4.5 Master ID 1
NM 7.4.5 Master ID 2
Figure 2 - Migration Target configuration
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
19/157
IN SYSTEM EVOLUTION (ISE) Overview

This chapter describes the In System Evolution (ISE) procedure to upgrade an Alcatel NMS reducing as much as possible, the system down time period. The approach is based on the creation of a new instance as data repository and a new installation tree. This allows to perform a big portion of the migration leaving the current system up and running. ISE migration can be performed with both One Shot and Stepped approach. One Shot is mandatory for Master NMS cohosted on the same machine. ISE migration foreseen two phases: the first one allows to install and configure the target NMS and is common to both One Shot and Stepped migration, the second one is specific to the chosen approach. Note: This document does not provide information for upgrading NMS installed with 1359HA OS-Cluster protections; refer 1359HA OS-Cluster 7.1 Installation and Administration Guide [4]
Important Recommendations
Before proceeding with the ISE as described hereafter please verify on TEC WEB site (http://tec.ond.alcatel.it), if there are some additional notes concerning the installation (select NR8 NR8.1PL2 Installation_notes). These notes have to be intended as preparations steps for the ISE described in this chapter.
ED
RELEASED
Optics
20/157
4.1
Preparation Guide Lines
4.1.1 Evaluate the ISE prerequisites
Before to start the migration you have to verify that all requested pre-conditions have been correctly fulfilled, and that you have retrieved all data requested during the upgrade; refer to Verify Pre-conditions chapter for details.
Supprim : Verify Preconditions
4.1.2 Perform the System Backup
Even if ISE procedure foresees a reverting procedure, it is mandatory to have a full system backup. If you do not have one, you have to do it now by follow the instruction shown at Full Backup/Restore chapter of 1350 NM Administration Guide [1]. Note: With disk mirror configuration, backup can be performed on line.
4.1.3 NMS SWPDESC, OS-Conf and Install Wizard Upgrade
1. Login as user root. 2. Refer to chapter APPENDIX D: NMS SWPDESC, OS-CONF AND INSTALL WIZARD UPGRADE for the details related to this upgrade procedure. Only In case of HP ITANIUM system execute step 3: 3. Copy OS-CONF 8.1.2 P01.2 package into /alcatel/DEPOT directory: OS-Conf812P01_2.depot and execute ...,sys,root # swinstall s /alcatel/DEPOT/OS-Conf812P01_2.depot \* (cksum & size: 403368502 51200)
Mis en forme : Police :Gras, Italique, Anglais (Royaume-Uni)
Supprim : APPENDIX D: NMS SWPDESC, OS-CONF AND INSTALL WIZARD UPGRADE
4.1.4 Predispose a temporary file system for Data Export
To be able to perform the Data Export is necessary creating a temporary File System. Retrieve and install the MGT tools as described in the dedicated sections in APPENDIX E: DATA Export/Import Create a temporary file system for storing the exported data by entering: ...,sys,root # cd / ...,sys,root # scextendfs /alcatel/ExpTmp <size> Note: to check in advance the needed disk space perform the following command:
1AA 00014 0004 (9711) A4
Mis en forme : Police :Italique

Supprim : APPENDIX E: DATA Export/Import
...,sys,root # EvalExportSize <NMS>_<NMS Id>-<NMS Ver>
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
21/157
Where:
<NMS Id> is the NMS instance identification number <NMS Ver> is the NMS version The command returned value must be at least doubled to get the needed free space. If you are migrating 1354RM or 1354BMETH execute the following command: ...,sys,root # /usr/local/bin/adjust_ora_group
4.1.5 Predispose the system for the NR8.1PL2 software.
Warning! If you prefer manual predisposition, to avoid future machine reboot predispose all NMSs now.
Warning! If you need to predispose a NM 7.3 Master instance to manage QB3* NEs, predispose manually all the instances with the command ...,sys root # scmanageswp noreboot and go directly to step 6 You have now to create a batch file useful to perform the automatic predisposition of NR8.1PL2 NMS and instances. 1. Login into the system as user root. 2. If present, remove the symbolic links: ...,sys ...,sys ...,sys ...,sys ...,sys root root root root root # # # # # cd rm cd rm rm /alcatel/ 8.1PL2 /usr/Systems/ Global_Instance-7.1.7 Global_Instance_7.1.7_Master
3. Start scautopredispose tool entering: ...,sys root # scautopredispose -o <file name> Where: <file name> is the file previously created with scautopredispose tool. 4. Start scmanageswp tool entering: ...,sys root # scmanageswp noreboot cmdfile <file name> Where: <file name> is the file previously created with scautopredispose tool. Note: Do not forget noreboot option! If its the case, quit the procedure!
Note: The installation from Network Depot can be performed only after the depot set-up, for more information refer to 1350 Rel8.1PL2 Installation Guide [1]. Neglect warnings like the following: Warning: maxdsiz has a new ADD declaration in the same 1354BM_code_kp section on the "1354BMETH 8.1.5" descriptor file. The final value will be the greater.
ED
RELEASED
Optics
22/157
5. The list of software to be installed will be displayed. At the end, on the screen you should have a list of items selected for the configuration, like to the following:
Items SELECTED for the CONFIGURATION Item Type ---------SWP SWP SWP INSTANCE INSTANCE INSTANCE SWP Name --------------OS_KERNEL 1354RM 1353NM OS_KERNEL 1354RM 1353NM SWP Version ----------7.1.7 7.4.9 7.4.5 7.1.7 7.4.9 7.4.5 INSTANCE Number INSTANCE Dimension Opt --------------- -------------------- ---
1 1 1
OSKERNEL 1354RM_IM_Small 1353NM_IM_Small
Enter 'a' to Apply, 'c' to Cancel or 'd' to Display again: 6. In order to preceed in the configuration, enter a. The procedure will ask where to find the software. You can choose between CD-ROM/DVD or network depot. If you choose depot, you have to refer to /alcatel/SCDEPOT on the depot system. If free space currently available on configured disks is not enough for NR8.1PL2 new requested areas, procedure will ask for new disks. See APPENDIX K: New Disk Request for more info. 7. Reply R to the following question to execute file system extension at the next reboot: File System:"/dev/vg00/lvol4" is busy, check process with PID(s): . Press: [T] = Try again (but after you have attempt to close all pid(s) ) [A] = Abort (DANGEROUS - operation is aborted)
Supprim : APPENDIX K: New Disk Request
[R] = Reboot (RECOMMENDED - operation will be completed after next reboot) then press [Enter] At the end of software upgrade, the following message will be shown: scmanageswp noreboot-cmdfile SESSION was successful ATTENTION: to complete the configuration for the Migration use the command: scmanageswp resume NOTE: at resume time the system REBOOT WILL be activated. If the directory /SCINSTALL/execution_parking/ contains some files execute: ...,sys,root # mv /SCINSTALL/execution_parking/* /SCINSTALL/execution/ If the symbolic link /opt/tao_1.4 does not point to /opt/tao1.4l_p7 execute: ...,sys,root # ln -sf /opt/tao1.4l_p7 /opt/tao_1.4
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
23/157
4.1.6 Install NR8.1PL2 software

Overview
Hereafter it is explained how to install NR8.1PL2 software during the ISE procedure. The installation process can be performed either using the CD-ROM or using the Network depot: according the installation method you have to follow the related sections in this chapter. Note: The installation from Network Depot can be performed only after the depot set-up, for more information refer to 1350 Rel8.1PL2 Installation Guide [1].
OS-Kernel Installation
This section describes how to install OS-Kernel from CD-ROM or Depot created for Alcatel TMN software in <depot directory> directory of depot <depot host> system: WARNING: The OS-Conf upgrade can cause the root password expiration; in this case enter a new one.
Login as root user with a Unix shell (without graphical interface: do not execute this procedure via GoGlobal-UX) Enter the following command: ...,sys,root # cd /alcatel/Install_Wizard If CD-ROM installation: Insert SWP-NR81_ADD01 volume 1/1 medium in the CD drive. Start the OS-KERNEL installation by entering the following command sequence. ...,sys,root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM ...,sys,root # ./Install.sh install force OS-KERNEL -cdrom On the screen will appear the following question related to the CD drive: Please enter the Device Name of source media [c0t0d0]: Reply [Enter] to confirm, or type e different CD device file name if the default one is not ok. Replace the CD_ROM with the new one when (and if) requested.. If DEPOT installation: Start the OS-KERNEL installation by entering the following command (one only line). ...,sys,root # ./Install.sh install force OS-KERNEL <depot host> <depot directory>
ED
RELEASED
Optics
24/157
In both cases: The installation script starts. The procedure asks you to select the version to be installed by issuing:
====================================================================== Installation OS-KERNEL package ====================================================================== ---------------------------------------------------------------------1) OS-KERNEL 7.1.2-19.2 (08.01PL2) 2) OS-KERNEL <Version> (<NR version>) E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed ... Neclect the following message: NOTE: Preparing to install ... StartSession[12]: : cannot execute StartSession[12]: INSTALLER | awk '{print }':
not found
Supprim : Table 4
Enter the order number of OS-Kernel according with its target version as reported in table Table 23 belonging to Appendix A: Summary tables This activity takes approximately 45 minutes. Sometime messages like the following will be issued: WARNING: The link /alcatel/Kernel points to an others directory /alcatel/<Version>/Kernel different to the current one /alcatel/8.1PL2/Kernel, skipping it ... Dont worry about it. Verify the correct installation checking the file: /alcatel/Install_Wizard/log/Installation_OSKERNEL_#.log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: ...,sys,root # umount /SD_CDROM
Mis en forme : Police :Gras, Italique

Supprim : Appendix A: Summary tables
NMS Software Installation

This paragraph describes how to install NR8.1PL2 NMS software from CD-Rom or from network depot. Execute this procedure for each NMS you have predisposed the system for. 1. Login into the system as user root. 2. Enter the following command sequence: ...,sys,root # cd /alcatel/Install_Wizard If CD-ROM installation: Insert SWP-NR81_ADD01 volume 1/2 medium in the CD drive. Start the NMS installation by entering the following command sequence. ...,sys,root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM ...,sys,root # ./Install.sh -install force <NMS> -cdrom
1AA 00014 0004 (9711) A4
Where the key <NMS> has to be replaced with the NMS name
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
25/157
On the screen will appear the following question related to the CD drive:
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel Supprim : Table 4
Please enter the Device Name of source media [c0t0d0]: Reply [Enter] to confirm, or type e different CD device file name if the default one is not ok. Replace the CD_ROM with the new one when (and if) requested. If DEPOT installation: Install each NMS subject to ISE Migration entering the following command: ...,sys,root # ./Install.sh -install force <NMS> <depot host> <depot directory> Where the key <NMS> has to be replaced with the NMS name In both cases: The installation script starts. The procedure asks you to select the version to be installed by issuing: ====================================================================== Installation <NMS> package ====================================================================== 1) <NMS> <Version> (08.01PL2) 2) <NMS> <Version> () E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed ... Enter the item ID according the NMS application type you are upgrading and linked target version as reported in table Table 23 belonging to Appendix A: Summary tables. The time requested by activity depends by the installing NMS, the 1353NM can require up to 2h and 30 minutes. Sometime messages like the following will be issued: WARNING: The link /alcatel/Kernel points to an others directory /alcatel/<Version>/Kernel different to the current one /alcatel/8.1PL2/Kernel, skipping it ... Dont worry about them. Repeat steps for each NMS subject to ISE Migration Verify the correct installation checking the file: /alcatel/Install_Wizard/log/Installation_<NMS>_#.log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: ...,sys,root # umount /SD_CDROM

NMC Software Installation (ETH_MEDIATOR / ISN / IOO / etc)

This paragraph describes how to install NR8.1PL2 NMC (Components) software from CD-ROM or Alcatel Depot. Login into the system as user root.
1AA 00014 0004 (9711) A4
Enter the following command sequence:
ED
RELEASED
Optics
26/157
...,sys,root # cd /alcatel/Install_Wizard If CD-ROM installation:

Insert SWP-NR81_ADD01 volume 1/2 medium in the CD drive. Start the NMC installation by entering the following command sequence. ...,sys,root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM ...,sys,root # ./Install.sh -install <NMC> -cdrom Where the key <NMC> has to be substituted as indicated in table in Table 30 On the screen will appear the following question related to the CD drive: Please enter the Device Name of source media [c0t0d0]: Reply [Enter] to confirm, or type e different CD device file name if the default one is not ok. Replace the CD_ROM with the new one when (and if) requested. If DEPOT installation: Install each NMC subject to ISE Migration entering the following command: ...,sys,root # ./Install.sh -install <NMC> <depot host> <depot directory> Where the key <NMC> has to be substituted as indicated in table in Table 30 In both cases: 3. The installation script starts. Sometime messages like the following will be issued: WARNING: The link /alcatel/Kernel points to an others directory /alcatel/<Version>/Kernel different to the current one /alcatel/8.1PL2/Kernel, skipping it ... Dont worry about it. 4. Repeat step for each NMC subject to ISE Migration. 5. Verify the correct installation checking the file: /alcatel/Install_Wizard/log/Installation_<NMC>_#.log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: ...,sys,root # umount /SD_CDROM
Supprim : Table 11 Supprim : Table 11
4.1.7 Customize OS-Kernel
1. Login as root user. 2. Enter the following command sequence. ...,sys,root # cd /alcatel/Install_Wizard ...,sys,root # ./Install.sh custom OS-KERNEL 3. The procedure asks you to select the version to be customized by issuing: ====================================================================== Customization OS-KERNEL package ====================================================================== ---------------------------------------------------------------------1) OS-KERNEL 7.1.2-RP15 ()
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
27/157
2)
OS-KERNEL <Version>
()
E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed ... Enter 1 [Enter], according the OSK target version as reported in table Table 23 belonging to Appendix A: Summary tables Reply n [Enter] to the following question to execute the OS-Kernel customization: NOTE: Edit the file /alcatel/8.1PL2/Kernel/lib/lib_perl/Semaphores.pm and change the line 61 from my $MIN_SEMAPHORE_NUM=7182; to my $MIN_SEMAPHORE_NUM=8182; ...,sys,root # /alcatel/8.1PL2/Kernel/script/KernelCustomize Immediately after KernelCustomize completion execute the following commands: ...,sys,root # cd /usr/Systems/Global_Instance_7.1.7_Master/APACHE/script/ ...,sys,root # ./tomcat_stop.sh ...,sys,root # ./apache_stop.sh Neglect the possible message: httpd (no pid file) not running Verify the correct customization checking the file: /alcatel/Install_Wizard/log/Customization_OSKERNEL_#.log /alcatel/8.1PL2/Kernel/maintenance/log/KernelCustomize.log Do you want to execute OS-KERNEL Custom? [y|n|q]
Supprim : Table 4
4.1.8 Customize Instances Subjected to ISE
Warning! Always migrate any client instance in the topology after its respective master instance. What must be absolutely avoided is to customize the new client instance before its master. Not doing so can have disruptive effects on the system! You can now customize the local NMS master, subject to ISE Migration ( Table 27, Table 28 and Table 29 where New Instance column contains "YES). If GENOS is installed remove from /etc/services all the lines related to almcpa entries (ports 20001 / 20002 / 20003 / 20004 / 20005). If you are migrating 1354RM execute: ...,sys,root # mkdir p /opt/JacORB2.1.3.5/classes a. Login into the system with graphical interface as user root (execute this procedure via GoGlobal-UX).
Supprim : Table 8 Supprim : Table 9 Supprim : Table 10
ED
RELEASED
Optics
28/157
b. Start the custom process by entering: ...,sys root # cd /alcatel/Install_Wizard ...,sys,root # ./Install.sh -custom <NMS>
c.
The procedure asks you to select the version to be customized by issuing:
====================================================================== Customization <NMS> package ====================================================================== ---------------------------------------------------------------------1) <NMS> <Version> () 2) <NMS> <Version> () E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed ... d. Enter the item ID according the NMS application type you are upgrading and linked target version as reported in table Table 23 belonging to Appendix A: Summary tables Reply y [Enter] to the following question to execute the <NMS> customization: NOTE: Do you want to execute <NMS> Custom? [y|n|q]
Supprim : Table 4

The Customize script will issues a sequence of windows depending by the specific NMS, with System,Instances,List
Figure 3 - Upgrade System, Instance, List window
e. Move the cursor on [Choose_One] button and press on mouse selection button to open the list. f. Select New instance and release the button.
g. Pull down the Action menu and select Apply & Exit. A window similar to the following should appear:
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
29/157
Figure 4 - ISE Customize Parameter Definition window.
h. Fill the fields in the Parameter Definition window as specified in the Table 22 (see Appendix A: Summary tables) according the NMS you are customizing. Note: i. Some customization procedure can issue specific sub-configuration window, refer to specific administration guide for more info.
Pull down the Action menu and select Apply & Exit
The customization process takes up to 2 hours, depending by the NMS and the system performances. The log of the activity will be shown in a window like this:
ED
RELEASED
Optics
30/157
1AA 00014 0004 (9711) A4

Figure 5 - Upgrade Custom log window.
Note: j.
The custom can issue warning and error messages that have to be ignored, refer to Appendix J: Custom Warning and Error.

Supprim : Appendix J: Custom Warning and Error
Verify the correct customization of the NMS checking in the files: /alcatel/Install_Wizard/log/Customization_<NMS>_#.log /alcatel/Kernel/maintenance/trace/Custom.trace /alcatel/Kernel/maintenance/log/Custom.log
k.
Launch the following command if you need to customize another new instance or, if finished continue with the next paragraph:
...,sys,root # ./Install.sh custom <NMS> l. Follow points 3 to 9 for each instance to customize.
4.1.9 Preparing for 1354RM Instance Configuration
If the NMS is a 1354RM: 1. Login into the system as root user. 2. Change the following files permission: ...,sys root # chmod R 777 /usr/Systems/1354RM_1-7.4.9/FWK/poller ...,sys root # chmod R 777 /usr/Systems/1354RM_1-7.4.9/trcLevel Ignore warning like the following:
WARNING: chmod: cant change comet2pollingmgr_1354RM_5-7.4.9_: Nor owner WARNING: chmod: cant change stop_poller: Nor owner
3. Save database parameter file (db_params.cfg) entering the following commands: ...,sys root # cd /usr/Systems/1354RM_1-7.4.9 ...,sys root # cd databases/dbsnml/admin/pfile ...,sys root # cp p db_params.cfg db_params.cfg.orig 4. Edit db_params.cfg setting the processes keyword to 100 (3 occurrences).
4.1.10 Export and Import of System Configuration

1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
31/157
For each NMS installed and subjected to ISE migration, perform the export and import of System Configuration executing the following steps: Execute system config export as described in section System Configuration Export of APPENDIX E: DATA Export/Import. Perform system config import as described in section System Configuration Import of APPENDIX E: DATA Export/Import.
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Supprim : System Configuration Export
Mis en forme : Police :Italique, Anglais (tats-Unis)
Mis en forme : Police :Italique Mis en forme : Police :Italique, Anglais (tats-Unis)
Supprim : System Configuration Import Supprim : APPENDIX E: DATA Export/Import
ED
RELEASED
Optics
32/157
4.1.11 Configure Instances Subjected to ISE

Perform the System Configuration of the new Master instances customized in Customize Instances Subjected to ISE 3. Login into the system with a graphical Interface as alcatel user. 4. Start the System Configuration tool by entering: $ . /alcatel/8.1PL2/Kernel/env/Kernel $ /alcatel/8.1PL2/Kernel/etc/SystemConfig <NMS> <NMS Id>-<NMS Version> Where: <NMS> <NMS Id> <NMS Version> is the NMS product. is the NMS instance identification number. is the NMS target version.

Supprim : Customize Instances Subjected to ISE
(e.g.: /alcatel/8.1PL2/Kernel/etc/SystemConfig 1354RM 1-7.4.9) 5. All the subsystems present in the source NMS will be automatically selected. Its mandatory to reconfigure all processes with the mouse right button, creating new databases and updating the parameters that refer to the old Network Release. Also verify their configuration according to the information stored in the Table 24, Table 25 in Appendix A: Summary tables. Remember to add new mandatory subsystems. In case of 1353NM first of all add Supervision_Area_# Subsystem, insert correct values in NECOM. In case of 1354BM-ETH select New for the TAO_Interface Repository, Add EMLIM_Proxy e NMLIM_Proxy subsystems. 6. Pull down Main menu and select Update Config to start the System Configuration. 7. Verify the correct System Configuration of the NMS checking in the files: /alcatel/8.1PL2/Kernel/maintenance/log/SystemConfiguration_<NMS>*.log 8. Repeat the procedure for each new NMS Master instance created and subjected to ISE Migration.
Supprim : Table 5 Supprim : Table 6

4.1.12 Create DB schema reference files
If you are migrating a 1354RM, execute the following commands to create RM DB schema reference files: 1. Login into the system as user snml 2. Startup 1354RM database: ... ... ... ... $ $ $ $ cd /usr/Systems/1354RM_1-7.4.9 . ./.snmlrc cd ORACLE/databases/dbnml/etc start_db
3. Get a snapshot of the database: ... $ mkdir /alcatel/DEPOT/NR81PL2_RM_DB_Ref (if you get an error execute, as root: chmod 777 /alcatel/DEPOT and repeat the command) ... $ chmod 777 /alcatel/DEPOT/NR81PL2_RM_DB_Ref ... $ cd /usr/Systems/1354RM_1-7.4.9/ORACLE/script/ ... $ ./MIB_Contents get /alcatel/DEPOT/NR81PL2_RM_DB_Ref
1AA 00014 0004 (9711) A4
4. Stop 1354RM database: ... $ cd /usr/Systems/1354RM_1-7.4.9
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
33/157
... $ cd ORACLE/databases/dbnml/etc ... $ stop_db If you are migrating a 1354BMETH, execute the following commands to create BMETH DB schema reference files: 1. Login into the system as user bmml 2. Startup 1354BMETH database: ... ... ... ... $ $ $ $ cd /usr/Systems/1354BMETH_1-8.1.5 . ./.bmmlrc cd ORACLE/databases/dbnml/etc start_db
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel Supprim : Data Export Supprim : APPENDIX E: DATA Export/Import
3. Get a snapshot of the database: ... $ mkdir /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref (if you get an error execute, as root: chmod 777 /alcatel/DEPOT and repeat the command) ... $ chmod 777 /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref ... $ cd /usr/Systems/1354BMETH_1-8.1.5/ORACLE/script/ ... $ ./MIB_Contents get /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref 4. Stop 1354BMETH database: ... $ cd /usr/Systems/1354BMETH_1-8.1.5 ... $ cd ORACLE/databases/dbnml/etc ... $ stop_db
4.1.13 Perform the Application Backup
From now onwards no activity on the networks are allowed (stop network construction & provisioning) Perform the SMF backup on tape and disk devices of Network, PM, AS, Operator and SEC on each NMS system. This will allow restoring the data machine by machine.
4.1.14 Export, Import, and Conversion of Instances Subjected to ISE Migration
Hereafter are described the steps to follow in order to execute the export, the import and the conversion of the data. Perform the export, import, conversion executing the following steps: 1. Login into the system as root user 2. Execute data export as described in section Data Export of APPENDIX E: DATA Export/Import. 3. If you are going to import many operators (> 50) execute this wa to save time: cd /alcatel/8.1PL2/Kernel/bin mv UserConfiguration UserConfiguration.sh vi UserConfiguration insert the following 2 lines: #!/bin/sh /alcatel/Kernel/bin/UserConfiguration.sh $* > /dev/null &
1AA 00014 0004 (9711) A4
Mis en forme : Police :Italique, Anglais (tats-Unis) Mis en forme : Police :Italique
ED
RELEASED
Optics
34/157
save and exit chmod 777 UserConfiguration 4. Perform data import as described in section Data Import of APPENDIX E: DATA Export/Import.
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel Supprim : Data Import
5. If the NMS is a 1353NM: Perform data conversion has described in APPENDIX F: 1353NM Data Conversion. 5. If the NMS is a 1354RM: Extract required XML packages from OS_Conf 7.1.2P02. If available on depot: ...,sys,root # swinstall -s <depot_host>:<depot_dir> \ [Enter] XML-NamespaceSupport* XML-SAX* XML-SIMPLE* If available on DVD: a. Insert OS-Conf 7.1.2 P02 (or OS-ConfUX 8.1.1 P05) DVD. b. ...,sys,root # scmount /dev/dsk/ <cxtydz> /SD_CDROM c. ...,sys,root # swinstall -s /SD_CDROM \ [Enter] XML-NamespaceSupport* XML-SAX* XML-SIMPLE* d. ...,sys,root # umount /SD_CDROM e. Extract DVD. Neglect messages starting with: ERROR: Could not apply the software selection .. Perform data conversion has described in APPENDIX G: 1354RM Data Conversion. 6. If the NMS is a 1354BM-ETH: Perform data conversion has described in APPENDIX H: 1354BM-ETH Data Conversion.

Mis en forme : Police :Italique Mis en forme : Police :Italique

Supprim : APPENDIX F: 1353NM Data Conversion
Supprim : APPENDIX G: 1354RM Data Conversion
Mis en forme : Police :Italique Mis en forme : Police :Italique

Supprim : APPENDIX H: 1354BM-ETH Data Conversion
4.1.15 Shutdown the database of the new NMS subjected to ISE Migration
If the NMS is a 1354RM, shutdown the database of the new NMS Master subjected to ISE Migration executing: 1. Login into the system as user snml 2. Execute: $ $ $ $ cd /usr/Systems/1354RM_1-7.4.9 . ./.snmlrc cd ORACLE/databases/dbnml/etc stop_db
4.1.16 Restoring 1354RM DB Initialization file
If the NMS is a 1354RM: 1. Login into the system as snml user. 2. Restore database initialization files entering the following commands: $ cd /usr/Systems/1354RM_1-7.4.9 $ cd databases/dbsnml/admin/pfile $ mv db_params.cfg.orig db_params.cfg
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
35/157
$ cd /usr/Systems/1354RM_1-7.4.9 $ cd ORACLE/databases/dbnml/admin/pfile Edit init1.ora setting the processes keyword (1 occurrence) according to the following table: NMS\db dimension 1354RM Small 200 Medium 400 Large 1100
Processes for 1354RM Database
ED
RELEASED
Optics
36/157
4.2
One Shot ISE Guide Lines
4.2.1 Shutdown running application subjected to ISE Migration.
Note: It is suggested to inform all users in advance that the system will be shutdown. Shutdown any running application by: 1. Login into the system in graphical mode as user alcatel. 2. Start TMN-OS application, by clicking on icon: 3. Identify local NMS Master instances subjected to ISE migration referring to Appendix B: SW Packages, Table 27, Table 27 and Table 28 (depending on your starting NR), where New Instance column contains "YES. 4. Highlight NMS master instance by clicking on the related icon shown in the OSs object area. 5. Click on OS pull down on TMN-OS menu-bar, then on Stop System. 6. Confirm stop command by clicking on OK button of Confirm popup window. 7. Repeat steps 4-6 for each NMS Master subjected to ISE migration. 8. Logout from all user sesssions.
Supprim : Appendix B: SW Packages Supprim : Table 8 Supprim : Table 8 Supprim : Table 9
4.2.2 De-Activate previous OS-Kernel
De-activate previous OS-Kernel executing as user root: ...,sys,root # /alcatel/Kernel/bin/DeactivateKernel.pl
4.2.3 Activate NR8.1PL2 OS-Kernel
You have now to activate the new OS-kernel: Login as user root Adjust the connection manager reference in the /etc/inittab file executing: a. Edit the /etc/inittab file b. Modify the line related with the connection manager. Change from KCM:4:respawn:/alcatel/<source_NR>/Kernel/etc/run_conmgr to KCM:4:respawn:/alcatel/8.1PL2/Kernel/etc/run_conmgr Get connnection manager processes PID executing:
...,sys,root # ps -ef | grep conmgr The command output looks like: root 8148 _conmgr 1 0 Nov 20 ? 0:03 /bin/ksh/alcatel/7.1D/Kernel/etc/run
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
37/157
root 5001
8219
Nov 20
0:40 /alcatel/7.1D/Kernel/bin/conmgr.exe
Get conmgr.exe and run_conmgr PIDs (8148 and 8219 in the example). Kill connnection manager processes executing:
...,sys,root # kill 9 <PIDs> Enter the following command to activate the new kernel:
...,sys,root # /alcatel/8.1PL2/Kernel/bin/ActivateKernel.pl Neglect the message: ERROR: lss not running ... if referred to a client instance. Verify the correct activation of new release by entering:
...,sys,root # ls -l /usr/Systems
lrwxr-xr-x 1 root sys /usr/Systems/1354RM_1_7.4.9_Master lrwxr-xr-x 1 root sys /usr/Systems/1354RM_1_7.4.9_Master drwxrwxr-x 52 snml dba 34 Mar 21 15:41 1354RM_1 -> 34 Mar 20 09:12 1354RM_1-7.4.9 -> 2048 Mar 28 12:35 1354RM_1_7.4.9_Master
lrwxr-xr-x 1 root sys 41 Mar 21 15:41 Global_Instance -> /usr/Systems/Global_Instance_7.1.7_Master lrwxr-xr-x 1 root sys 41 Mar 19 17:30 Global_Instance-7.1.7 -> /usr/Systems/Global_Instance_7.1.7_Master drwxrwxrwx 21 root root Global_Instance_7.1.7_Master 1024 Mar 22 09:22
4.2.4 Resume Predispose.
Now you have to resume the scmanageswp procedure to complete the platform upgrade. 1. Login into the system as user root without using GoGlobal-UX and start scmanageswp entering: ...,sys,root # scmanageswp resume scmanageswp require you to confirm the request with the following message: You request to resume the pending migration. Are you ready to RESUME the migration ? (y/n)
ED
RELEASED
Optics
38/157
1AA 00014 0004 (9711) A4
2. Answer y [Enter] to resume the previously suspended predispose. The system will be reboot. The following message will be shown:
scmanageswp resume SESSION was successful. ATTENTION: now to complete the configuration Shutdown-Reboot will be executed. Press [Enter] to continue. 3. Press [Enter] to proceed. The following message appears: Executing Shutdown-Reboot to complete the configuration. ***** The System reboots automatically, please wait ***** The procedure will rebuild the HP-UX 11i kernel, and it will install 3PP software requested by NR8.1PL2 NMS, before return the prompt. Note: If CD installation has been specified the predispose procedure will ask to provide the CDROMs where the software is stored.
If scmanageswp resume procedure fails and the following (or similar) error appears in /SCINSTALL/scinstall.log: ERROR: "ipb082:/": The software dependencies for 1 products or filesets cannot be resolved. * The analysis phase failed for "ipb082:/". * Analysis had errors. check Appendix N for a possible workaround.
4.2.5 Update Poseidon License
Remember that Poseidon license.dat must be updated, get a valid license file and install it on /opt/Poseidon/etc/license.dat
4.2.6 Upgrade Software Platform
Before starting the upgrade verify if the path /opt/JacORB2.1.3.5 is a normal directory (not a mount point) and has two subdirectories. In such a case execute: ...,sys,root # rm -r /opt/JacORB2.1.3.5 Upgrade the platform software according to chapter Platform Upgrade. IMPORTANT DO NOT FORGET ! Note: The upgrade execution can take up to three hours depending by the installation method and by the server model. It can also require some system reboot!
Supprim : Platform Upgrade
4.2.7 Customize GoGlobal-UX
Note:
1AA 00014 0004 (9711) A4
Do not execute this commands using GoGlobal-UX interface. Customize GoGlobal-UX software: ,sys,root # . /alcatel/8.1PL2/Kernel/env/Kernel
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
39/157
,sys,root # /alcatel/8.1PL2/Kernel/script/XTEmulatorConfigure.pl \ [Enter] KernelCustomize The script asks you the authorization to stop GoGlobal-UX issuing: GoGlobal 2 server will be stopped. Do you want continue ? (yes/no, default=no) Enter yes [Enter] to proceed.
4.2.8 NMS Integration
For each NMS in NR8.1PL2 execute: ...,sys,root # cd /usr/Systems/<NMS>_<NMS Id> ...,sys,root # SMF/tools/br/script/addExternalOs.pl b -d ...,sys,root # SMF/tools/scheduler/script/addSchedJob.pl b If you want to rebuild the old scheduled jobs: ...,sys,root # SMF/tools/scheduler/script/addPlan.pl c and, for any listed command name, e.g. "PurgeAS", ...,sys,root # SMF/tools/scheduler/script/addPlan.pl -cmd PurgeAS Integrate the NMS executing: ..., sys,root # /alcatel/Kernel/script/UpdateNetworkConnections.pl Answer yes to all the integration confirmations requested by the procedure, with the exception of 1354RM Master and 1354BMETH Master configuration, when requested to confirm for PLT and SMF integration of 1354BMETH instance "under" 1354RM instance, answer always no.
4.2.9 Startup NMS applications & verify behaviour
Start the NMS instances and check the system behaviour.
4.2.10 1354RM NE and alarm synchronization
Perform the following steps: 1. Login into the system with a graphical interface as alcatel user 2. Start the TMN-OS application 3. Highlight the 1354RM instance clicking on the related icon shown in the OSs object area 4. Start 1354RM user interface (browser) clicking on the related button 5. Select the nodes that you want to synchronize: Table 1. Choose Actions -> Synchronize -> Synchronize NE
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
40/157
Table 2.
Choose Actions -> Synchronize -> Synchronize Alarm
4.2.11 1354RM audit
The Audit procedure allows to verify 1354RM alignment, taking care of real attributes value read from NE. Perform the following steps: Login into the system with a graphical interface as alcatel user Start the TMN-OS application Highlight the 1354RM instance clicking on the related icon shown in the OSs object area Start 1354RM user interface (browser) clicking on the related button Select the Q3 nodes on which you want to perform the audit: 1. Choose Actions -> Configure Download -> Disable 2. Choose Actions -> Consistency Audit -> Notify Audit 3. Select the related NEs and search for Not aligned objects and Not aligned objects (traffic impacting) The panels show the objects whose value is not aligned between NEs and 1354RM If 1354RM manages QB3* NEs, perform the following actions: 4. From RM browser select the nodes on which you want to perform the audit 5. Choose Actions -> Configure Download -> Disable 6. Open PMC and change 1354RM Run Level to 4 Network Consistency 1. Select one node a time and choose Actions -> Consistency Audit -> Global 7. Select the related NEs and search for Not aligned objects and Not aligned objects (traffic impacting) The panels show the objects whose value is not aligned between NEs and 1354RM 2. From PMC, change 1354RM Run Level to 0 Full Functionality In case of misalignment on 1354RM objects (expecially if traffic impacting) contact TEC, in order to define the action to perform for 1354RM realignment, otherwise on selected nodes perform Actions -> Configure Download -> Enable
4.2.12 1354BMETH align up
The Align Up procedure allows to realign 1354BMETH taking care of real attributes value read from NE. This procedure is mainly used as a post-migration step and has to be executed after an Audit procedure. Perform the following steps: 1. Login into the system with a graphical interface as alcatel user 2. Start the TMN-OS application
1AA 00014 0004 (9711) A4
3. Highlight the 1354BM instance clicking on the related icon shown in the OSs object area
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
41/157
4. Start 1354BMETH Construction graphical user interface clicking on the related button
5. Perform an audit: Choose Utilities -> Audit/Align/Reserve -> Start Procedure Confirm the start of the procedure and select the Auditable NEs on which to execute the audit. 6. Start 1354BMETH Ethernet Management graphical user interface clicking on the related button 7. Choose Utilities -> Align Up in order to display the Align Up panel The panel shows the objects whose value is not aligned between NE and 1354BMETH Choose the objects you want to align up from the shown list and confirm the request.
4.2.13 Alarm Federation configuration
If Alarm Federation was previously configured on the system, then it must be re-configured after migration completion.
4.2.14 1354RM pre-OTN to OTN migration
Only in case of 1354RM migration from NR7.1 or NR7.3, and only if the network contains 1626LM 2.0 or 2.0A NEs, execute the procedure described in APPENDIX M: 1354RM pre-OTN to OTN migration
4.2.15 Remove Obsolete Data and Software
1. Login into the system as user root 2. Run scmanageswp by entering: ...,sys,root # scmanageswp 3. Enter 6 [Enter] to Remove SWP Instance 4. The list of available instances will be shown, enter the instance item number you have to remove. 5. The selected item will be shown for confirmation, check you choice and confirm only if its correct. 6. Repeat steps from 3 to 5 for each SWP Instances you have to remove. Remove also OS-KERNEL instance. 7. Go back to the main menu, entering q [Enter]. 8. Enter 3 [Enter] for Remove SWP 9. The list of available SWP will be shown, enter the instance item number you have to remove. 10. The selected item will be shown for confirmation, check you choice and confirm only if its correct. 11. Repeat steps from 8 to 10 for each SWP Instances you have to remove. Remove also OS-KERNEL. 12. Enter a [Enter] for Apply the selected choices. The procedure will show the selection you made. Double check it before proceeding!
ED
RELEASED
Optics
42/157
13. Execute the removal entering a [Enter] again. 14. Important Note: when the procedure asks for mount points removal as here indicated:
ATTENTION: the next action is NOT REVERSIBLE! If you confirm the following mount points will be removed from system: /usr/Systems/1353NM_1_7.0_Master /usr/Systems/1354RM_1_7.1_Master /home /alcatel/7.1D Do you confirm the removal ? (y/n)
Reply y [Enter]. /home directory wont be removed In case the running processes have some files opened on the file system you are removing, a message similar to the following appears on the screen: Delete Mount Point: /usr/Systems/Global_Instance_7.1.2_Master NOTE: Mount Point: /usr/Systems/Global_Instance_7.1.2_Master is not an empty directory Do you want to kill all processes are unsing Mount Point: /usr/Systems/Global_Instance_7.1.2_Master ? Press [y] for yes or [n] for no, then press [Enter] Enter y Reply y 15. Release the exceeding swap space executing: ,sys,root # scdeletefs g swap 16. Cleanup the link structure by removing symbolic links to old instances under: a. /usr/Systems/ b. /alcatel/BackupArea/ c. /alcatel/MirrorArea/ 17. In case, remove manually the old mount point executing: 4. If (and only if) you are upgrading from NR7.1D PL2: ...,sys,root# scdeletefs /alcatel/7.1D 5. If (and only if) you are upgrading from NR7.3: ...,sys,root# scdeletefs /alcatel/7.3 6. If (and only if) you are upgrading from NR7.4: ...,sys,root# scdeletefs /alcatel/7.4 7. If (and only if) you are upgrading from NR8.1: ...,sys,root# scdeletefs /alcatel/8.1 8. If (and only if) you are upgrading from NR8.1: ...,sys,root# scdeletefs /alcatel/8.1PL1 Remove old software references entering the following command: ...,sys,root # /alcatel/INSTALLER/etc/sw_target_removal <SNR> Where: [Enter] to kill all of them.
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
43/157
<SNR>
has to be replaced with the old Network Release installation sub-directory, that has to be: 7.1D for NR7.1D, NR7.1D PL1, NR7.1D PL2 and all NR7.2 7.3 for NR7.3 7.4 for NR7.4 8.1 for NR8.1 8.1PL1 for NR8.1PL1
In case, remove manually old mount points not removed by deinstallation procedures: ...,sys,root# scdeletefs <mount point> e.g.: ...,sys,root# scdeletefs /usr/local/mysql-5.1.7-beta-hpux11.11-hppa2.0w-64bit If bdf command returns both the lines /opt/oracle10g/ /opt/oracle10g/10.2.0.3 and you wish to free the disk space used by the old version of Oracle (~ 3 GB) execute the following procedure (since it requires a system stop can also be executed later): Stop 1354RM and/or 1354BM-ETH ...,sys,root# cd ...,sys,root# umount /opt/oracle10g/10.2.0.3 ...,sys,root# umount /opt/oracle10g ...,sys,root# mkdir -p /opt/oracle10g/10.2.0.3 ...,sys,root# mkdir /opt/oracle10g/old ...,sys,root# cp -p /etc/fstab /etc/fstab.bck Modify the suitable line in /etc/fstab from: /dev/vg00/lvolxx /opt/oracle10g ..... to: /dev/vg00/lvolxx /opt/oracle10g/old .... ...,sys,root# mountall ...,sys,root# bdf ...,sys,root# scdeletefs /opt/oracle10g/old ...,sys,root# swremove Oracle10g
ED
RELEASED
Optics
44/157
4.3
Stepped ISE Guide Lines
4.3.1 Shutdown running application subjected to ISE Migration.
Note: It is suggested to inform all users in advance that the system will be shutdown. Shutdown any running application by: 1. Login into the system in graphical mode as user alcatel. 2. Start TMN-OS application, by clicking on icon: 3. Identify local NMS Master instances subjected to ISE migration referring to Appendix B: SW Packages, Table 27, Table 27 and Table 28 (depending on your starting NR), where New Instance column contains "YES. 4. Highlight NMS master instance by clicking on the related icon shown in the OSs object area. 5. Click on OS pull down on TMN-OS menu-bar, then on Stop System. 6. Confirm stop command by clicking on OK button of Confirm popup window. 7. Repeat steps 4-6 for each NMS Master subjected to ISE migration. 8. Logout from all user sesssions.
Supprim : Appendix B: SW Packages Supprim : Table 8 Supprim : Table 8 Supprim : Table 9
4.3.2 De-integration
If the system you are upgrading is integrated by a higher level one, login as root on the machine hosting the higher level system and execute: ...,sys root # /alcatel/Kernel/script/deintegration.pl sys <NMS> inst <NMS Id>-<NMS Ver> <nms> <nms Id>-<nms Ver> Where: <NMS> <NMS Id> <NMS Ver> <nms> <nms Id> <nms Ver> higher level system higher level system identification number higher level system version lower level system lower level system identification number lower level system version
...,sys,root # cd /usr/Systems/<NMS>_<NMS Id> ...,sys root # ./SMF/tools/br/script/addExternalOs.pl b d
4.3.3 De-Activate previous OS-Kernel
De-activate previous OS-Kernel executing as user root: ...,sys,root # /alcatel/Kernel/bin/DeactivateKernel.pl

1AA 00014 0004 (9711) A4
Neglect the following message:
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
45/157
Warning: DocumentRoot [<NMS_INSTANCE_DIR>/web/java/] does not exist

4.3.4 Activate NR8.1PL2 OS-Kernel
You have now to activate the new OS-kernel: 1. Login as user root 2. Adjust the connection manager reference in the /etc/inittab file executing: c. Edit the /etc/inittab file
d. Modify the line related with the connection manager. Change from KCM:4:respawn:/alcatel/<source_NR>/Kernel/etc/run_conmgr to KCM:4:respawn:/alcatel/8.1PL2/Kernel/etc/run_conmgr 3. Get connnection manager processes PID executing: ...,sys,root # ps -ef |grep conmgr The command output looks like: root 8148 _conmgr root 5001 8219 1 1 0 0 Nov 20 Nov 20 ? ? 0:03 /bin/ksh/alcatel/7.1D/Kernel/etc/run 0:40 /alcatel/7.1D/Kernel/bin/conmgr.exe
Get conmgr.exe and run_conmgr PIDs (8148 and 8219 in the example). 4. Kill connnection manager processes executing: ...,sys,root # kill 9 <PIDs> 5. Enter the following command to activate the new kernel: ...,sys,root # /alcatel/8.1PL2/Kernel/bin/ActivateKernel.pl Neglect the message: ERROR: lss not running ... if referred to a client instance. 6. Verify the correct activation of new release by entering: ...,sys,root # ls -l /usr/Systems
lrwxr-xr-x 1 root sys /usr/Systems/1354RM_1_7.4.9_Master lrwxr-xr-x 1 root sys /usr/Systems/1354RM_5_7.4.9_Master drwxrwxr-x 52 snml dba 34 Mar 21 15:41 1354RM_1 -> 34 Mar 20 09:12 1354RM_1-7.4.9 -> 2048 Mar 28 12:35 1354RM_1_7.4.9_Master
lrwxr-xr-x 1 root sys 41 Mar 21 15:41 Global_Instance -> /usr/Systems/Global_Instance_7.1.7_Master lrwxr-xr-x 1 root sys 41 Mar 19 17:30 Global_Instance-7.1.7 -> /usr/Systems/Global_Instance_7.1.7_Master drwxrwxrwx 21 root root Global_Instance_7.1.7_Master 1024 Mar 22 09:22
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
46/157
4.3.5 Resume Predispose.

Now you have to resume the scmanageswp procedure to complete the platform upgrade. 3. Login into the system as user root without using GoGlobal-UX and start scmanageswp entering: ...,sys,root # scmanageswp resume scmanageswp require you to confirm the request with the following message: You request to resume the pending migration. Are you ready to RESUME the migration ? (y/n) 4. Answer y to resume the previously suspended predispose. The system will be reboot. The following message will be shown: scmanageswp resume SESSION was successful. ATTENTION: now to complete the configuration Shutdown-Reboot will be executed. Press [Enter] to continue. 5. Press [Enter] to proceed. The following message appears: Executing Shutdown-Reboot to complete the configuration. ***** The System reboots automatically, please wait ***** The procedure will rebuild the HP-UX 11i kernel, and it will install 3PP software requested by NR8.1PL2 NMS, before return the prompt. Note: If CD installation has been specified the predispose procedure will ask to provide the CDROMs where the software is stored.
If scmanageswp resume procedure fails and the following (or similar) error appears in /SCINSTALL/scinstall.log: ERROR: "ipb082:/": The software dependencies for 1 products or filesets cannot be resolved. * The analysis phase failed for "ipb082:/". * Analysis had errors. check Appendix N for a possible workaround.
4.3.6 Update Poseidon License
Remember that Poseidon license.dat must be updated, get a valid license file and install it on /opt/Poseidon/etc/license.dat
4.3.7 Upgrade Software Platform
Before starting the upgrade verify if the path /opt/JacORB2.1.3.5 is a normal directory (not a mount point) and has two subdirectories. In such a case execute: ...,sys,root # rm -r /opt/JacORB2.1.3.5
1AA 00014 0004 (9711) A4
Upgrade the platform software according to chapter Platform Upgrade.

Supprim : Platform Upgrade
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
47/157
IMPORTANT DO NOT FORGET !

Note: The upgrade execution can take up to three hours depending by the installation method and by the server model. It can also require some system reboot!
4.3.8 Customize GoGlobal-UX
Note:
Do not execute this commands using GoGlobal-UX interface. Customize GoGlobal-UX software: ,sys,root # . /alcatel/8.1PL2/Kernel/env/Kernel ,sys,root # /alcatel/8.1PL2/Kernel/script/XTEmulatorConfigure.pl \ KernelCustomize The script asks you the authorization to stop GoGlobal-UX issuing: GoGlobal 2 server will be stopped. Do you want continue ? (yes/no, default=no) Enter yes to proceed.
4.3.9 Customize old client instances
This chapter need to be follow if a master instance has been migrated and when client instance is present on the machine. If you have to keep old client instances to allow the communication with the machine not yet upgraded, you have now to customize these presentation instance with the new OS-Kernel. Adjust software references for old client instances entering the following command as root user: ...,sys,root # /alcatel/INSTALLER/etc/sw_nr_adjuster <SNR> 8.1PL2 Where: <SNR> has to be replaced with the old Network Release installation sub-directory, that has to be: 7.1D for NR7.1D, NR7.1D PL1, NR7.1D PL2 and all NR7.2 7.3 for NR7.3 7.4 for NR7.4 8.1 for NR8.1 8.1PL1 for NR8.1PL1 For each presentation execute the following procedure: If old software is aligned to DR4 version: Login into the system with graphical interface as user root (execute this procedure via GoGlobalUX). ...,sys,root # cd /alcatel/Install_Wizard ...,sys,root # ./Install.sh custom <NMS> Where the key <NMS> has to be replaced with the NMS name The Customize script will issues a sequence of windows depending by the specific NMS, with System,Instances,List
ED
RELEASED
Optics
48/157
1. Move the cursor on [Choose One] button and press on mouse selection button to open the list, and select New instance and release the button. Pull down the Action menu and select Apply & Exit. 2. Fill in Parameter Definition: window with the data related to the presentation of previous version, as specified in the Table 22 (see Appendix A: Summary tables) according the NMS you are customizing. Then pull down the Action menu and select Apply & Exit 3. Verify the correct customization of the NMS checking in the files: /alcatel/Install_Wizard/log/Customization_<NMS>_#.log /alcatel/Kernel/maintenance/trace/Custom.trace /alcatel/Kernel/maintenance/log/Custom.log After customizing NM 7.0 client instance edit the file /usr/Systems/1353NM_1_7.0_Presentation/eml/usmshdata/script/run_atmusm and change the line 11 from $CORBAPORT="5013" to $CORBAPORT="5012" If old software is successive to DR4 version and some post DR4 (raw-)patches have been installed, then recustomize old client instances following the Release Notes of the last installed (raw-)patch. Login as root on remote lower level machines hosting master instances not yet upgraded, still in old Network Release: ..., sys,root # cd /alcatel/ ..., sys,root # ln s <SNR> 8.1PL2 Where <SNR> has to be replaced with the old Network Release installation sub-directory, that has to be: 7.1D for NR7.1D, NR7.1D PL1, NR7.1D PL2 and all NR7.2 7.3 for NR7.3 7.4 for NR7.4 8.1 for NR8.1 8.1PL1 for NR8.1PL1 ..., sys,root # cd /usr/Systems/ ..., sys,root # ln -s Global_Instance_<Ver>_Master \ Global_Instance_7.1.7_Master ..., sys,root # ln -s /usr/Systems/Global_Instance_7.1.7_Master \ Global_Instance-7.1.7
Supprim : Table 3

1AA 00014 0004 (9711) A4
Where:
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
49/157
<Ver>
has to be replaced with the old Network Release Global Instance version, that has to be: 7.1.2 for NR7.1D, NR7.1D PL1, NR7.1D PL2 and all NR7.2 7.1.3 for NR7.3 7.1.4 for NR7.4 7.1.5 for NR8.1 7.1.6 for NR8.1PL1
4.3.10 Remote client instances upgrade
Warning! Always migrate remote client instances after their respective master instance. Not doing so can have disruptive effets on the system! After successful upgrade of a NMS master instance, upgrade also its related client instances hosted by remote higher level systems. Login into the remote higher level system with graphical interface as user root (execute this procedure via GoGlobal-UX). Decustom old presentation instance: ...,sys,root # /alcatel/Kernel/script/Decustom <NMS> <NMS Id>-<NMS Ver> Where: <NMS> <NMS Id> <NMS Ver> is the NMS product name related to the instance that has to be de-customized is the NMS instance identification number is the NMS version identification number
Cleanup the link structure by removing symbolic links to old presentation instance under d. /usr/Systems/ ...,sys,root # cd /alcatel/Install_Wizard ...,sys,root # ./Install.sh custom <NMS> Where the key <NMS> has to be replaced with the NMS name Warning! If the remote higher level system hosts 1354BMETH remember to stop it, re-execute the System Configuration updating EML_PROXY and NML_PROXY configuration and re-integrate it!
4.3.11 NMS Integration
For each NMS in NR8.1PL2 execute: ...,sys,root # cd /usr/Systems/<NMS>_<NMS Id> ...,sys,root # SMF/tools/br/script/addExternalOs.pl b -d ...,sys,root # SMF/tools/scheduler/script/addSchedJob.pl b If you want to rebuild the old scheduled jobs: ...,sys,root # SMF/tools/scheduler/script/addPlan.pl c
ED
RELEASED
Optics
50/157
and, for any listed command name, e.g. "PurgeAS", ...,sys,root # SMF/tools/scheduler/script/addPlan.pl -cmd PurgeAS
If client instances are installed on the machine, execute: ..., sys,root # /alcatel/Kernel/bin/UpdatePresentation.pl force Then integrate the NMS executing: ..., sys,root # /alcatel/Kernel/script/UpdateNetworkConnections.pl Answer yes to all the integration confirmations requested by the procedure, with the exception of 1354RM Master and 1354BMETH Master configuration, when requested to confirm for PLT and SMF integration of 1354BMETH instance "under" 1354RM instance, answer always no.
4.3.12 Startup NMS applications & Verify Behaviour
Do a logout/login, start the NMS instances and check the system behaviour.
4.3.13 1354RM NE and alarm synchronization
Perform the following steps: Login into the system with a graphical interface as alcatel user Start the TMN-OS application Highlight the 1354RM instance clicking on the related icon shown in the OSs object area Start 1354RM user interface (browser) clicking on the related button Select the nodes that you want to synchronize: Table 3. Table 4. Choose Actions -> Synchronize -> Synchronize NE Choose Actions -> Synchronize -> Synchronize Alarm
4.3.14 1354RM Audit
The Audit procedure allows to verify 1354RM alignment, taking care of real attributes value read from NE. Perform the following steps: Login into the system with a graphical interface as alcatel user Start the TMN-OS application Highlight the 1354RM instance clicking on the related icon shown in the OSs object area Start 1354RM user interface (browser) clicking on the related button Select the Q3 nodes on which you want to perform the audit: Table 5. Table 6.
1AA 00014 0004 (9711) A4
Choose Actions -> Configure Download -> Disable Choose Actions -> Consistency Audit -> Notify Audit
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
51/157
Table 7. Select the related NEs and search for Not aligned objects and Not aligned objects (traffic impacting) The panels show the objects whose value is not aligned between NEs and 1354RM If 1354RM manages QB3* NEs, perform the following actions: Table 8. Table 9. From RM browser select the nodes on which you want to perform the audit Choose Actions -> Configure Download -> Disable
Table 10. Open PMC and change 1354RM Run Level to 4 Network Consistency 1. Select one node a time and choose Actions -> Consistency Audit -> Global Table 11. Select the related NEs and search for Not aligned objects and Not aligned objects (traffic impacting) The panels show the objects whose value is not aligned between NEs and 1354RM 2. From PMC, change 1354RM Run Level to 0 Full Functionality In case of misalignment on 1354RM objects (expecially if traffic impacting) contact TEC, in order to define the action to perform for 1354RM realignment, otherwise on selected nodes perform Actions -> Configure Download -> Enable
4.3.15 1354BMETH align up
The Align Up procedure allows to realign 1354BMETH taking care of real attributes value read from NE. This procedure is mainly used as a post-migration step and has to be executed after an Audit procedure. Perform the following steps: 1. Login into the system with a graphical interface as alcatel user 2. Start the TMN-OS application 3. Highlight the 1354BM instance clicking on the related icon shown in the OSs object area 4. Start 1354BMETH Construction graphical user interface clicking on the related button 5. Perform an audit: Choose Utilities -> Audit/Align/Reserve -> Start Procedure Confirm the start of the procedure and select the Auditable NEs on which to execute the audit. 6. Start 1354BMETH Ethernet Management graphical user interface clicking on the related button 7. Choose Utilities -> Align Up in order to display the Align Up panel The panel shows the objects whose value is not aligned between NE and 1354BMETH Choose the objects you want to align up from the shown list and confirm the request.
4.3.16 Alarm Federation configuration
ED
RELEASED
Optics
52/157
4.3.17 1354RM pre-OTN to OTN migration

4.3.18 Remove Obsolete Data and Software
Warning! In case of stepped ISE the old software is still necessary for the system to work properly. Remove obsolete data and software only after all the machines have been upgraded to the new Network Release!
In this paragraph it is described how to remove the obsolete data and software from the disks, to free the disk space no more useful. Login into the system as user root Run scmanageswp by entering: ...,sys,root # scmanageswp Enter 6 [Enter] to Remove SWP Instance The list of available instances will be shown, enter the instance item number you have to remove. The selected item will be shown for confirmation, check you choice and confirm only if its correct. Repeat steps from 3 to 5 for each SWP Instances you have to remove. Remove also OS-KERNEL instance. Go back to the main menu, entering q [Enter]. Enter 3 [Enter] for Remove SWP The list of available SWP will be shown, enter the instance item number you have to remove. The selected item will be shown for confirmation, check you choice and confirm only if its correct. Repeat steps from 8 to 10 for each SWP Instances you have to remove. Remove also OS-KERNEL. Enter a [Enter] for Apply the selected choices. The procedure will show the selection you made. Double check it before proceeding! Execute the removal entering a [Enter] again. Important Note: when the procedure asks for mount points removal as here indicated:
ATTENTION: the next action is NOT REVERSIBLE! If you confirm the following mount points will be removed from system: /usr/Systems/1353NM_1_7.0_Master /usr/Systems/1354RM_1_7.1_Master /home /alcatel/7.1D Do you confirm the removal ? (y/n)
1AA 00014 0004 (9711) A4
Reply y [Enter]. /home directory wont be removed
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
53/157
In case the running processes have some files opened on the file system you are removing, a message similar to the following appears on the screen: Delete Mount Point: /usr/Systems/Global_Instance_7.1.2_Master NOTE: Mount Point: /usr/Systems/Global_Instance_7.1.2_Master is not an empty directory Do you want to kill all processes are unsing Mount Point: /usr/Systems/Global_Instance_7.1.2_Master ? Press [y] for yes or [n] for no, then press [Enter] Enter y Reply y Release the exceeding swap space executing: ,sys,root # scdeletefs g swap Cleanup the link structure by removing symbolic links to old instances under: /usr/Systems/ /alcatel/BackupArea/ /alcatel/MirrorArea/ 3. In case, remove manually the old mount point executing: If (and only if) you are upgrading from NR7.1D PL2: ...,sys,root# scdeletefs /alcatel/7.1D If (and only if) you are upgrading from NR7.3: ...,sys,root# scdeletefs /alcatel/7.3 If (and only if) you are upgrading from NR7.4: ...,sys,root# scdeletefs /alcatel/7.4 If (and only if) you are upgrading from NR8.1: ...,sys,root# scdeletefs /alcatel/8.1 If (and only if) you are upgrading from NR8.1: ...,sys,root# scdeletefs /alcatel/8.1PL1 Remove old software references entering the following command: ...,sys,root # /alcatel/INSTALLER/etc/sw_target_removal <SNR> Where: <SNR> has to be replaced with the old Network Release installation sub-directory, that has to be: 7.1D for NR7.1D, NR7.1D PL1, NR7.1D PL2 and all NR7.2 7.3 for NR7.3 7.4 for NR7.4 8.1 for NR8.1 8.1PL1 for NR8.1PL1 In case, remove manually old mount points not removed by deinstallation procedures: ...,sys,root# scdeletefs <mount point> e.g.: ...,sys,root# scdeletefs /usr/local/mysql-5.1.7-beta-hpux11.11-hppa2.0w-64bit
1AA 00014 0004 (9711) A4 All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel
[Enter] to kill all of them.
ED
RELEASED
Optics
54/157
If bdf command returns both the lines /opt/oracle10g/

/opt/oracle10g/10.2.0.3 and you wish to free the disk space used by the old version of Oracle (~ 3 GB) execute the following procedure (since it requires a system stop can also be executed later): Stop 1354RM and/or 1354BM-ETH ...,sys,root# cd ...,sys,root# umount /opt/oracle10g/10.2.0.3 ...,sys,root# umount /opt/oracle10g ...,sys,root# mkdir -p /opt/oracle10g/10.2.0.3 ...,sys,root# mkdir /opt/oracle10g/old ...,sys,root# cp -p /etc/fstab /etc/fstab.bck Modify the suitable line in /etc/fstab from: /dev/vg00/lvolxx /opt/oracle10g ..... to: /dev/vg00/lvolxx /opt/oracle10g/old .... ...,sys,root# mountall ...,sys,root# bdf ...,sys,root# scdeletefs /opt/oracle10g/old ...,sys,root# swremove Oracle10g
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
55/157
MIGRATION WITH SPARE SYSTEM Overview

Migration with spare system defines the guidelines for who has in charge a machine replacement in conjunction with software migration. This approach requires a spare system with characteristic useful to execute the application software as described in 1350 Rel. 71.D/7.2/7.3/7.4/8.1 OND Network Management Configuration Guide [3]. Within this chapter the system running the software that have to be migrate will be called source and the spare system that will take over will be called target. Migration with Spare System can be performed with both One Shot and Stepped approach. One Shot is mandatory for Master NMS cohosted on the same machine. This migration foreseen two phases: the first one is specific to the chosen approach (One Shot or Stepped), the second one is common to both One Shot and Stepped migration. NOTE: This procedure is applicable for Migration from NR7.1D/7.2 PL2, NR7.3, NR7.4, NR8.1 or NR8.1PL1.
Important Recommendations
Before proceeding with any migration or upgrade as described hereafter, please verify on TEC WEB site (http://tec.ond.alcatel.it), if there are some additional notes concerning the installation (select NR8 NR8.1PL2 Installation_notes). These notes have to be intended as preparations steps for the ISE described in this chapter.
ED
RELEASED
Optics
56/157
5.1
One Shot Migration with Spare System Overview
This section describes the first phase specific to One Shot Migration with spare system. It allows preparing the target system ready in advance, it can be done weeks before the migration. The things that will be done are:
1. Obtain source system variables. 2. Install hp-ux on target system 3. Install & Predispose the system for the NR8.1PL2 software. 4. Install the application software on target system 5. Customize the application software on target system At this point continue the migration applying the Migration with Spare System Common Procedure.
5.1.1 Obtain source system variables.
NOTE:
From this point and onwards, no changes to hp-ux configuration are allowed the entire system has been completely migrated to the target machine. In case any modification have to be performed on hp-ux, the procedure has to be repeated starting from this step.
To be able to properly install the target system, you must retrieve some information for the source one. There are two kind of information: 1. HP-UX operating system information, retrieve them following APPENDIX L: Retrieve HP-UX System Information. 2. Alcatel NMS information, in terms of NMS type and instance present on the source system, to retrieve them follow the Identify the current software paragraph 6.1.1 and fill in the table in Appendix A: Summary tables.
Supprim : APPENDIX L: Retrieve HP-UX System Information Supprim : Identify the current software
5.1.2 Install hp-ux on target system
NOTE:
Because the target system must have the same network configuration of source one, the target system cant be connected to the LAN where the source is connected to, it suggested to connect it to a stand alone LAN HUB.
HP-UX operating system has to be installed on the target system using the same configuration provided for the source one. The most important are: hostname and IP address of lan0, both these data have to be provided at installation time. Detailed instruction for HP-UX installation are available on 1350 Rel8.1PL2 Installation Guide [1]. When the installation is completed, recover the routing configuration: 1. IP configuration for LAB card different than LAN0. 2. Routing configuration. 3. Gated configuration
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
57/157
5.1.3 Install & Predispose the system for the NR8.1PL2 software.
NR8.1PL2 SWPDESC and Install Wizard Upgrade

a. Login as user root. b. Refer to paragraph Install NMS SWPDESC, and Install Wizard in the APPENDIX D for the details related to this upgrade procedure.
Supprim : Install NMS SWPDESC, and Install Wizard
Predispose the NR8.1PL2 software

NOTE: To be able to carry out the software installation you must require temporary license for both GoGlobal-UX and Alcatel NMS application you have to upgrade/migrate. Warning! To avoid future machine reboot predispose all NMSs now, in particular 1353NM 7.4.5 SWP and instances. You have now to predispose for Alcatel NMS SW of target machine. Note: The installation from Network Depot can be performed only after the depot set-up, for more information refer to 1350 Rel8.1PL2 Installation Guide [1].
Note: It is mandatory that the predispose and the creation of the new instance is performed in one shot for the entire system. It is not allowed to perform this activity in multiple steps. To predispose the system for the new NMS software you have to: 1. Login into the system as user root. 2. Start scmanageswp tool entering: ...,sys root # scmanageswp 3. Enter 1 at SWP MAIN MENU in order to choose Predispose new SWP 4. Enter 2 at Predispose new SWP menu in order to use the installed NMS description. Now it will appear the list of the software packages (with related version) that can be installed. 5. Choose from the list, the item corresponding to the target version of the SWP you want to upgrade. Predispose for: OS-Kernel 7.1.7, and for all the NMS SWP involved in the migration. 6. Enter, for each choice, the item ID correspondent to the choice previously done. 7. Enter q twice to get back to SWP MAIN MENU 8. Enter 4 at the SWP MAIN MENU to get in Create a new INSTANCE section menu
Create NMS instance.

Its now requested to create the instance for SWP above predispose. 1. On the screen you should have the Create a new INSTANCE section menu that shows you the NMS present on the system and previously predisposed (e.g. hereafter): Create new INSTANCE Item SWP Name SWP Version
ED
RELEASED
Optics
58/157
---1 2 3 4
--------------1353NM 1353NM 1354RM OS_KERNEL
----------7.0 7.4.5 7.4.9 7.1.7
Enter 'q' to Quit, 'd' to Display again or the Item Number : 2. Predispose for: OS-KERNEL 7.1.7 and all NMS Master instances and for all needed NMS client instances. 3. Select the Item ID that has the value Instance dimension equal to the one present in the table Table 21, column Instance Size/Type. 4. Insert the instance number as described in the column instance number shown in the table Table 21 5. Enter n for multi-volume group. 6. Enter q twice to get back to SWP MAIN MENU and there enter a twice to execute. The procedure will ask where to find the software. You can choose between CD-ROM/DVD or network depot. If you choose depot, you have to refer to /alcatel/SCDEPOT on the depot system. If free space currently available on configured disks is not enough for NR8.1PL2 new requested areas, procedure will ask for new disks. See APPENDIX K: New Disk Request for more info. At the end of software installation, the shutdown-reboot will be automatically executed.
Supprim : APPENDIX K: New Disk Request Supprim : Table 2 Supprim : Table 2
5.1.4 Install the application software on target system
Install the same Alcatel NMS present on the source hp server, but with the software version foreseen for NR8.1PL2. In this activity you have to keep the same instance ID of source system, previously written into Appendix A: Summary tables.

OS-Kernel Installation & Customization

This section describes how to install OS-Kernel from CD-ROM or Depot created for Alcatel TMN software in <depot directory> directory of depot <depot host> system: 1. Login as root user with a Unix shell (without graphical interface: do not execute this procedure via GoGlobal-UX) 2. Enter the following command: ...,sys,root # cd /alcatel/Install_Wizard If CD-ROM installation: a. Insert SWP-NR81_ADD01 volume 1/1 medium in the CD drive. b. Start the OS-KERNEL installation by entering the following command sequence. ...,sys,root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM ...,sys,root # ./Install.sh OS-KERNEL -cdrom On the screen will appear the following question related to the CD drive: Please enter the Device Name of source media [c0t0d0]:
1AA 00014 0004 (9711) A4
Reply [Enter] to confirm, or type e different CD device file name if the default one is not ok.
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
59/157
Replace the CD_ROM with the new one when (and if) requested..
If DEPOT installation: c. Start the OS-KERNEL installation by entering the following command.
...,sys,root # ./Install.sh OS-KERNEL <depot host> <depot directory> In both cases: 1. The installation script starts. This activity takes approximately 30 minutes. Sometime messages like the following will be issued: WARNING: The link /alcatel/Kernel points to an others directory /alcatel/<Version>/Kernel different to the current one /alcatel/8.1PL2/Kernel, skipping it ... Dont worry about it. 2. Reply y to the following question to execute the OS-Kernel customization: NOTE: Do you want to execute OS-KERNEL Custom? [y|n|q]
3. Enter yes to the following question in order to start Go-Global UX customization (if requested): GoGlobal 2 server will be stopped. Do you want continue ? (yes/no, default=no) 4. Verify the correct installation and customization checking the files: /alcatel/Install_Wizard/log/Installation_OSKERNEL_#.log /alcatel/Install_Wizard/log/Customization_OSKERNEL_#.log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: ...,sys,root # umount /SD_CDROM

This paragraph describes how to install NR8.1PL2 NMS software from CD-Rom or from network depot. Execute this procedure for each NMS. 1. Login into the system as user root. 2. Enter the following command sequence: ...,sys,root # cd /alcatel/Install_Wizard If CD-ROM installation: d. Insert SWP-NR81_ADD01 volume 1/2 medium in the CD drive. e. Start the NMS installation by entering the following command sequence. ...,sys,root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM ...,sys,root # ./Install.sh -install <NMS> -cdrom
1AA 00014 0004 (9711) A4
Where the key <NMS> has to be replaced with the NMS name On the screen will appear the following question related to the CD drive:
ED
RELEASED
Optics
60/157
Please enter the Device Name of source media [c0t0d0]: Reply [Enter] to confirm, or type e different CD device file name if the default one is not ok.
Replace the CD_ROM with the new one when (and if) requested. If DEPOT installation: 1. Install each NMS subject to ISE Migration entering the following command: ...,sys,root # ./Install.sh -install <NMS> <depot host> <depot directory> Where the key <NMS> has to be replaced with the NMS name When 1353NM cases: The procedure could asks you to select the version to be installed by issuing: ====================================================================== Installation <NMS> package ====================================================================== 1) 1353NM 7.0.15-P09 () 2) 1353NM 7.4 () E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed ... Select the item ID according the 1353NM 7.4 application. 1. The time requested by activity depends by the installing NMS, approximately 15 minutes for 1354RM, approximately 75 minutes for 1353NM. Sometime messages like the following will be issued: WARNING: The link /alcatel/Kernel points to an others directory /alcatel/<Version>/Kernel different to the current one /alcatel/8.1PL2/Kernel, skipping it ... Dont worry about them. 2. Verify the correct installation checking the file: /alcatel/Install_Wizard/log/Installation_<NMS>_#.log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: ...,sys,root # umount /SD_CDROM

This paragraph describes how to install NR8.1PL2 NMC (Components) software from CD-ROM or Alcatel Depot. Login into the system as user root. Enter the following command sequence: ...,sys,root # cd /alcatel/Install_Wizard If CD-ROM installation:
1AA 00014 0004 (9711) A4
f.
Insert SWP-NR81_ADD01 volume 1/2 medium in the CD drive.
g. Start the NMC installation by entering the following command sequence.
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
61/157
Where the key <NMC> has to be substituted as indicated in table in Table 30 On the screen will appear the following question related to the CD drive: Please enter the Device Name of source media [c0t0d0]: Reply [Enter] to confirm, or type e different CD device file name if the default one is not ok. Replace the CD_ROM with the new one when (and if) requested. If DEPOT installation: 2. Install each NMC subject to ISE Migration entering the following command: ...,sys,root # ./Install.sh -install <NMC> <depot host> <depot directory> Where the key <NMC> has to be substituted as indicated in table in Table 30 In both cases: 6. The installation script starts. Sometime messages like the following will be issued: WARNING: The link /alcatel/Kernel points to an others directory /alcatel/<Version>/Kernel different to the current one /alcatel/8.1PL2/Kernel, skipping it ... Dont worry about it. 7. Repeat step for each NMC subject to ISE Migration. 8. Verify the correct installation checking the file: /alcatel/Install_Wizard/log/Installation_<NMC>_#.log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: ...,sys,root # umount /SD_CDROM
5.1.5 Customize the application software on target system
Warning! Always migrate any client instance in the tolology after its respective master instance. What must be absolutely avoided is to customize the new client instance before its master. Not doing so can have disruptive effects on the system! Now you have to customize all the NMS Master and all necessary Client instances. 1. Login into the system with graphical interface as user root (execute this procedure via GoGlobal-UX). 2. Start the custom process by entering: ...,sys root # cd /alcatel/Install_Wizard ...,sys,root # ./Install.sh -custom <NMS> When 1353NM cases: The procedure asks you to select the version to be installed by issuing:
1AA 00014 0004 (9711) A4
====================================================================== Installation <NMS> package
ED
RELEASED
Optics
62/157
...,sys,root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM ...,sys,root # ./Install.sh -install <NMC> -cdrom
Supprim : Table 11
Supprim : Table 11
====================================================================== 1) 1353NM 7.0.15-P09 () 2) 1353NM 7.4 ()

E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed ... Select the item ID according to the related Master instance version. 1. Reply y to the following question to execute the <NMS> customization: NOTE: Do you want to execute <NMS> Custom? [y|n|q]
2. Move the cursor on [Choose_One] button and press on mouse selection button to open the list. 1. Select New instance and release the button. 2. Pull down the Action menu and select Apply & Exit. A window similar to the following should appear:
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
63/157
Figure 8 - Customize Parameter Definition window.
3. Fill the fields in the Parameter Definition window as specified in the Table 22 (see Appendix A: Summary tables) according the NMS you are customizing. Note: Some customization procedure can issue specific sub-configuration window, refer to specific administration guide for more info.
4. Pull down the Action menu and select Apply & Exit The customization process takes up to 2 hours, depending by the NMS and the system performances. The log of the activity will be shown in a window like this:
ED
RELEASED
Optics
64/157
1AA 00014 0004 (9711) A4

Note:

5. Verify the correct customization of the NMS checking in the files: /alcatel/Install_Wizard/log/Customization_<NMS>_#.log /alcatel/Kernel/maintenance/trace/Custom.trace /alcatel/Kernel/maintenance/log/Custom.log 6. Launch the following command if you need to customize another new instance or, if finished continue with the next paragraph: ...,sys,root # ./Install.sh custom <NMS> 7. Follow points 2 to 9 for each instance to customize.
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
65/157
5.2
Stepped Migration with Spare System Overview

This section describes the first phase specific to Stepped Migration with spare system. It allows preparing the target system ready in advance, it can be done weeks before the migration. The things that will be done are:
6. Obtain source system variables. 7. Install hp-ux on target system 8. Install & predispose for old presentation instance 9. Install & predispose the system for the NR8.1PL2 software 10. Install the application software on target system 11. Customize the application software on target system At this point continue the migration applying the Migration with Spare System Common Procedure.
5.2.1 Obtain source system variables.
NOTE:
From this point and onwards, no changes to hp-ux configuration are allowed the entire system has been completely migrated to the target machine. In case any modification have to be performed on hp-ux, the procedure has to be repeated starting from this step.
To be able to properly install the target system, you must retrieve some information for the source one. There are two kind of information: 1. HP-UX operating system information, retrieve them following APPENDIX L: Retrieve HP-UX System Information. 2. Alcatel NMS information, in terms of NMS type and instance present on the source system, to retrieve them follow the Identify the current software paragraph 6.1.1 and fill in the table in Appendix A: Summary tables.
Supprim : APPENDIX L: Retrieve HP-UX System Information Supprim : Identify the current software
5.2.2 Install hp-ux on target system

Warning! Do not install old Os-Conf and upgrade to the latest one. Install straight the latest OsConf.
NOTE:
Because the target system must have the same network configuration of source one, the target system cant be connected to the LAN where the source is connected to, it suggested to connect it to a stand alone LAN HUB.
HP-UX operating system has to be installed on the target system using the same configuration provided for the source one. The most important are: hostname and IP address of lan0, both these data have to be provided at installation time.
1AA 00014 0004 (9711) A4
Detailed instruction for HP-UX installation are available on 1350 Rel8.1PL2 Installation Guide [1].
ED
RELEASED
Optics
66/157
When the installation is completed, recover the routing configuration: 4. IP configuration for LAB card different than LAN0.
5. Routing configuration. 6. Gated configuration
5.2.3 Install & predispose for old client instances
If you have to keep old client instances to allow the communication with the machine not yet upgraded, you have now to install and predispose them.
Install previous NR version SWPDESC & Install_Wizard

Note: Install_Wizard uses /alcatel/DEPOT as a temporary area to store temporary files needed for installation. Therefore, it is strongly suggested to have /alcatel/DEPOT with a minimum of 1Gb free space before to start Install_Wizard tool Install Alcatel NMS Software Description and Install_Wizard belonging to NR installed on the source NMS. 1. Login into the system as user root. If CD-ROM installation: Insert the SWPNRxxx volume 1/x in the CD or DVD driver and mount it: ...,sys,root ...,sys,root ...,sys,root ...,sys,root ...,sys,root ...,sys,root ...,sys,root If DEPOT installation: Retrieve the software from depot machine: ...,sys,root # mkdir p /alcatel/DEPOT ...,sys,root # cd /alcatel/DEPOT
...,sys,root # rcp p <depot host>:<directory>/Install_Wizard-Rx.x.x-Px . ...,sys,root # rcp p <depot host>:<directory>/Install_Wizard_CMD-Rx.x.x-Px . ...,sys,root # rcp p <depot host>:<directory>/SWPDESCVxxxx.sdpkg .
# # # # # # #
scmountcd /dev/dsk/<cdrom device file> /SD_CDROM swinstall s /SD_CDROM/SWPDESCVxxxx.sdpkg \ * cd /SD_CDROM sh ./Install_Wizard-Rx.x.x-Px sh ./Install_Wizard_CMD-Rx.x.x-Px cd / umount /SD_CDROM
Install software description by entering hereafter command sequence: ...,sys,root # swinstall s /alcatel/DEPOT/SWPDESCVxxxx.sdpkg \* ...,sys,root # sh ./Install_Wizard-Rx.x.x-Px ...,sys,root # sh ./Install_Wizard_CMD-Rx.x.x-Px
Predispose the system for previous version software

Predispose for previous version 1353NM SWP Master and for all needed 1353NM client SWP instances.
1AA 00014 0004 (9711) A4
1. Login into the system as user root.
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
67/157
2. Start scmanageswp tool entering:

...,sys root # scmanageswp 3. Enter 1 at SWP MAIN MENU in order to choose Predispose new SWP 4. Enter 2 at Predispose new SWP menu in order to use the installed NMS description. Now it will appear the list of the software packages (with related version) that can be installed. 5. Choose from the list, and enter the item ID corresponding to the previous version SWP. 6. Enter q twice to get back to SWP MAIN MENU 7. Enter 4 at the SWP MAIN MENU to get in Create a new INSTANCE section menu
Predispose old client instances

Its now requested to create an instance for all needed old client instances. 1. Highlight in the table Table 21 belonging to Appendix A: Summary tables all previous version packages that must be manage in NR8.1PL2. On the screen you should have the Create a new INSTANCE section menu that shows you the previous version item (e.g. hereafter): Create new INSTANCE Item SWP Name SWP Version Session ---- --------------- ----------- ------1 1353NM 7.0 NEW Enter 'q' to Quit, 'd' to Display again or the Item Number : 2. Enter 1 at Create a new INSTANCE according to one of the items highlighted at point 3. You will get as output the list of the instance dimension. Item ---1 2 3 4 5 6 7 8 List of available INSTANCE dimension for SWP: 1353NM 7.0 INSTANCE Dimension INSTANCE Description -------------------- -------------------------------------------1353NM_IM_Test 1353NM Master (IM) System Small Configuration 1353NM_IM_Small 1353NM Master (IM) System Small Configuration 1353NM_IM_Medium 1353NM Master (IM) System Medium Configuration 1353NM_IM_Large 1353NM Master (IM) System Large Configuration 1353NM_US 1353NM Client (US) 1353NM_IM_S_CLSSpare 1353NM Master (IM) Small System for OS-Cluster 1353NM_IM_M_CLSSpare 1353NM Master (IM) Medium System for OS-Cluster 1353NM_IM_L_CLSSpare 1353NM Master (IM) Large System for OS-Cluster

Enter 'q' to Quit, 'd' to Display again or the Item Number : 4. Select from the list the Item ID that has the value Instance dimension equal to the one present in the table Table 21, column Instance Size/Type. 5. Insert the instance number as described in the column NMS instance number shown in the table Table 21 6. Enter n for multi-volume group. 7. Enter q to go back to Create a new INSTANCE menu.
1AA 00014 0004 (9711) A4 Supprim : Table 2 Supprim : Table 2
8. Repeat steps 2-5 for all needed previous version Client SWP instaces, highlighted at point 1.
ED
RELEASED
Optics
68/157
9. Enter q twice to get back to SWP MAIN MENU and there enter a twice to execute. Then procedure start executing the requested predispositions.
The procedure will ask where to find the software. You can choose between CD-ROM/DVD or network depot. If you choose depot, you have to refer to /alcatel/SCDEPOT on the depot system. If free space currently available on configured disks is not enough for NR7.4 new requested areas, procedure will ask for new disks. See APPENDIX K: New Disk Request for more info. 10. Reply R to the following question to execute file system extension at the next reboot: File System:/dev/vg00/lvol5 is busy, check process with pid(s): . Press: [T] for Try again, [A] for Abort, [R] for Reboot,then press [Enter] At the end of software installation, the shutdown-reboot will be automatically executed.
Supprim : APPENDIX K: New Disk Request
Install previous version software.

Install only previous version software without customizing any instance, by executing: 1. Login into the system as user root. 2. Enter the following command sequence: ...,sys,root # cd /alcatel/Install_Wizard If CD-ROM installation: h. Insert SWP-NRxxx volume 1/x medium in the CD drive. i. Start the previous version software installation by entering the following command sequence.
...,sys,root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM ...,sys,root # ./Install.sh -install <NMS> -cdrom On the screen will appear the following question related to the CD drive: Please enter the Device Name of source media [c0t0d0]: Reply [Enter] to confirm, or type e different CD device file name if the default one is not ok. Replace the CD_ROM with the new one when (and if) requested. If DEPOT installation: 3. Start the previous version software installation by entering the following command sequence: ...,sys,root # ./Install.sh install <NMS> <depot host> <depot directory> In both cases: 1. The installation script starts. The time requested by install activity can require up to 2h and 30 minutes. Sometime messages like the following will be issued: 2. Verify the correct installation checking the file: /alcatel/Install_Wizard/log/Installation_<NMS>_#.log If CD-ROM installation:
1AA 00014 0004 (9711) A4
Dismount the CD-ROM and remove the medium from the drive:
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
69/157
...,sys,root # umount /SD_CDROM

Remove SWPDESC, Install_Wizard and INSTALLER of previous NR version

1. Login as user root. 2. Remove the installed software description tool executing: ...,sys,root # swremove SWPDESC
3. Remove Installer tool executing: ...,sys root # rm -f /alcatel/INSTALLER ...,sys root # rm -Rf /alcatel/<SNR>/INSTALLER Where: <SNR> is equal to 7.1D if NR7.1D/7.2_PL2 7.3 if NR7.3 7.4 if NR7.4 8.1 if NR8.1 8.1 if NR8.1PL1
4. Remove the temporary file: ...,sys,root # rm ...,sys,root # rm /alcatel/DEPOT/Install_Wizard-Rx.x.x-Px /alcatel/DEPOT/Install_Wizard_CMD-Rx.x.x-Px
5.2.4 Install & predispose the system for the NR8.1PL2 software
NR8.1PL2 SWPDESC and Install Wizard Upgrade

Login as user root. Refer to paragraph Install NMS SWPDESC, and Install Wizard in the APPENDIX D for the details related to this upgrade procedure.
Supprim : Install NMS SWPDESC, and Install Wizard
Predispose the NR8.1PL2 software

NOTE: To be able to carry out the software installation you must require temporary license for both GoGlobal-UX and Alcatel NMS application you have to upgrade/migrate. Warning! To avoid future machine reboot predispose all NMSs now, in particular 1353NM 7.4.5 SWP and instances. You have now to predispose for Alcatel NMS SW of target machine. Note: The installation from Network Depot can be performed only after the depot set-up, for more information refer to 1350 Rel8.1PL2 Installation Guide [1].
To predispose the system for the new NMS software you have to: Login into the system as user root. Start scmanageswp tool entering:
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
70/157
...,sys root # scmanageswp

Enter 1 at SWP MAIN MENU in order to choose Predispose new SWP Enter 2 at Predispose new SWP menu in order to use the installed NMS description. Now it will appear the list of the software packages (with related version) that can be installed.
Choose from the list, the item corresponding to the target version of the SWP you want to upgrade. Predispose for: OS-Kernel 7.1.7, and for all the NMS SWP involved in the migration. Enter, for each choice, the item ID correspondent to the choice previously done. Enter q twice to get back to SWP MAIN MENU Enter 4 at the SWP MAIN MENU to get in Create a new INSTANCE section menu
Create NMS instance.

Its now requested to create the instance for SWP above predispose. On the screen you should have the Create a new INSTANCE section menu that shows you the NMS present on the system and previously predisposed (e.g. hereafter): Item ---1 2 3 4 Create new INSTANCE SWP Name SWP Version --------------- ----------1353NM 7.0 1353NM 7.4.5 1354RM 7.4.9 OS_KERNEL 7.1.7
Enter 'q' to Quit, 'd' to Display again or the Item Number : Predispose for: OS-KERNEL 7.1.7 and all NMS Master instances and for all needed NMS client instances. Select the Item ID that has the value Instance dimension equal to the one present in the table Table 21, column Instance Size/Type. Insert the instance number as described in the column instance number shown in the table Table 21 Enter n for multi-volume group. Enter q twice to get back to SWP MAIN MENU and there enter a twice to execute. The procedure will ask where to find the software. You can choose between CD-ROM/DVD or network depot. If you choose depot, you have to refer to /alcatel/SCDEPOT on the depot system. If free space currently available on configured disks is not enough for NR8.1PL2 new requested areas, procedure will ask for new disks. See APPENDIX K: New Disk Request for more info. At the end of software installation, the shutdown-reboot will be automatically executed.
Supprim : APPENDIX K: New Disk Request Supprim : Table 2 Supprim : Table 2
5.2.5 Install the application software on target system
Install the same Alcatel NMS present on the source hp server, but with the software version foreseen for NR8.1PL2. In this activity you have to keep the same instance ID of source system, previously written into Appendix A: Summary tables.
1AA 00014 0004 (9711) A4

ED
RELEASED
Optics
8DG 31466 AAAATCZZA
71/157
OS-Kernel Installation & Customization

This section describes how to install OS-Kernel from CD-ROM or Depot created for Alcatel TMN software in <depot directory> directory of depot <depot host> system: Login as root user with a Unix shell (without graphical interface: do not execute this procedure via GoGlobal-UX) Enter the following command: ...,sys,root # cd /alcatel/Install_Wizard If CD-ROM installation: j. k. Insert SWP-NR81_ADD01 volume 1/1 medium in the CD drive. Start the OS-KERNEL installation by entering the following command sequence.
...,sys,root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM ...,sys,root # ./Install.sh OS-KERNEL -cdrom On the screen will appear the following question related to the CD drive: Please enter the Device Name of source media [c0t0d0]: Reply [Enter] to confirm, or type e different CD device file name if the default one is not ok. Replace the CD_ROM with the new one when (and if) requested.. If DEPOT installation: l. Start the OS-KERNEL installation by entering the following command.
...,sys,root # ./Install.sh OS-KERNEL <depot host> <depot directory> In both cases: 5. The installation script starts. This activity takes approximately 30 minutes. Sometime messages like the following will be issued: WARNING: The link /alcatel/Kernel points to an others directory /alcatel/<Version>/Kernel different to the current one /alcatel/8.1PL2/Kernel, skipping it ... Dont worry about it. 6. Reply y to the following question to execute the OS-Kernel customization: NOTE: Do you want to execute OS-KERNEL Custom? [y|n|q]
7. Enter yes to the following question in order to start Go-Global UX customization (if requested): GoGlobal 2 server will be stopped. Do you want continue ? (yes/no, default=no) 8. Verify the correct installation and customization checking the files: /alcatel/Install_Wizard/log/Installation_OSKERNEL_#.log /alcatel/Install_Wizard/log/Customization_OSKERNEL_#.log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive:
ED
RELEASED
Optics
72/157
...,sys,root # umount /SD_CDROM

This paragraph describes how to install NR8.1PL2 NMS software from CD-Rom or from network depot. Execute this procedure for each NMS. Login into the system as user root. Enter the following command sequence: ...,sys,root # cd /alcatel/Install_Wizard If CD-ROM installation: m. Insert SWP-NR81_ADD01 volume 1/2 medium in the CD drive. n. Start the NMS installation by entering the following command sequence. ...,sys,root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM ...,sys,root # ./Install.sh -install <NMS> -cdrom Where the key <NMS> has to be replaced with the NMS name On the screen will appear the following question related to the CD drive: Please enter the Device Name of source media [c0t0d0]: Reply [Enter] to confirm, or type e different CD device file name if the default one is not ok. Replace the CD_ROM with the new one when (and if) requested. If DEPOT installation: 4. Install each NMS subject to ISE Migration entering the following command: ...,sys,root # ./Install.sh -install <NMS> <depot host> <depot directory> Where the key <NMS> has to be replaced with the NMS name The procedure could asks you to select the version to be installed by issuing (e.g. hereafter): ====================================================================== Installation <NMS> package ====================================================================== 1) 1353NM 7.0.15-P09 () 2) 1353NM 7.4 () E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed ... Select the item ID according to NR8.1PL2 application. 3. The time requested by activity depends by the installing NMS, approximately 15 minutes for 1354RM, approximately 75 minutes for 1353NM. Sometime messages like the following will be issued: WARNING: The link /alcatel/Kernel points to an others directory /alcatel/<Version>/Kernel different to the current one /alcatel/8.1PL2/Kernel, skipping it ...
1AA 00014 0004 (9711) A4
Dont worry about them.
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
73/157
4. Verify the correct installation checking the file:

All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel Supprim : Table 11 Supprim : Table 11 1AA 00014 0004 (9711) A4
/alcatel/Install_Wizard/log/Installation_<NMS>_#.log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: ...,sys,root # umount /SD_CDROM

This paragraph describes how to install NR8.1PL2 NMC (Components) software from CD-ROM or Alcatel Depot. Login into the system as user root. Enter the following command sequence: ...,sys,root # cd /alcatel/Install_Wizard If CD-ROM installation: o. Insert SWP-NR81_ADD01 volume 1/2 medium in the CD drive. p. Start the NMC installation by entering the following command sequence. ...,sys,root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM ...,sys,root # ./Install.sh -install <NMC> -cdrom Where the key <NMC> has to be substituted as indicated in table in Table 30 On the screen will appear the following question related to the CD drive: Please enter the Device Name of source media [c0t0d0]: Reply [Enter] to confirm, or type e different CD device file name if the default one is not ok. Replace the CD_ROM with the new one when (and if) requested. If DEPOT installation: 5. Install each NMC subject to ISE Migration entering the following command: ...,sys,root # ./Install.sh -install <NMC> <depot host> <depot directory> Where the key <NMC> has to be substituted as indicated in table in Table 30 In both cases: The installation script starts. Sometime messages like the following will be issued: WARNING: The link /alcatel/Kernel points to an others directory /alcatel/<Version>/Kernel different to the current one /alcatel/8.1PL2/Kernel, skipping it ... Dont worry about it. Repeat step for each NMC subject to ISE Migration. Verify the correct installation checking the file: /alcatel/Install_Wizard/log/Installation_<NMC>_#.log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: ...,sys,root # umount /SD_CDROM
ED
RELEASED
Optics
74/157
5.2.6 Customize the application software on target system

Warning! Always migrate any client instance in the tolology after its respective master instance. What must be absolutely avoided is to customize the new client instance before its master. Not doing so can have disruptive effects on the system! Now you have to customize all the NMS Master instances, and all necessary old client instances. Adjust software references for old client instances entering the following command as root user: Login into the system as user root and execute: ...,sys,root # /alcatel/Install_Wizard/etc/sw_nr_adjuster <SNR> 8.1PL2 Where: <SNR> has to be replaced with the Network Release installation sub-directory, that has to be: 7.1D 7.3 7.4 8.1 8.1PL1 for NR7.1D, NR7.1D PL1, NR7.1D PL2 and all NR7.2 for NR7.3 for NR7.4 for NR8.1 for NR8.1PL1
8. Login into the system with graphical interface as user root (execute this procedure via GoGlobal-UX). 9. Start the custom process by entering: ...,sys root # cd /alcatel/Install_Wizard ...,sys,root # ./Install.sh -custom <NMS> The procedure could asks you to select the version to be installed by issuing (e.g. hereafter): ====================================================================== Installation <NMS> package ====================================================================== 1) 1353NM 7.0.15-P09 () 2) 1353NM 7.4 () E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed ... Select the item ID according to the related old master instance version. 1. Reply y to the following question to execute the <NMS> customization: NOTE: Do you want to execute <NMS> Custom? [y|n|q]
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
75/157
2. Move the cursor on [Choose_One] button and press on mouse selection button to open the list. 3. Select New instance and release the button. 4. Pull down the Action menu and select Apply & Exit. A window similar to the following should appear:
Figure 11 - Customize Parameter Definition window. 1AA 00014 0004 (9711) A4
5. Fill the fields in the Parameter Definition window as specified in the Table 22 (see Appendix A: Summary tables) according the NMS you are customizing.
ED
RELEASED
Optics
76/157

Note:
Some customization procedure can issue specific sub-configuration window, refer to specific administration guide for more info.
6. Pull down the Action menu and select Apply & Exit
The customization process takes up to 2 hours, depending by the NMS and the system performances. The log of the activity will be shown in a window like this:
Note:

7. Verify the correct customization of the NMS checking in the files: /alcatel/Install_Wizard/log/Customization_<NMS>_#.log /alcatel/Kernel/maintenance/trace/Custom.trace /alcatel/Kernel/maintenance/log/Custom.log After customizing NM 7.0 client instance edit the file /usr/Systems/1353NM_1_7.0_Presentation/eml/usmshdata/script/run_atmusm and change the line 11 from $CORBAPORT="5013" to $CORBAPORT="5012"
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
77/157
5.3
Migration with Spare System Common Procedure

This section describes the phase common to both One Shot and Stepped Migration with Spare System. It allows exporting/importing configuration and data and swap to target systems. The things that will be done are: 8. NMS Master System Configuration 9. Create DB schema reference files 10. Install migration tools 11. Data Export from Source and Import to Target System 12. Data Conversion 13. System Swap
5.3.1 NMS Master System Configuration
Perform the System Configuration of the Master instances customized in Customize the application software on target system 1. Login into the system with a graphical Interface as alcatel user. 2. Start the System Configuration tool from TMN-OSs window. 3. Verify the correct System Configuration of the NMS checking in the files: /alcatel/8.1PL2/Kernel/maintenance/log/SystemConfiguration_<NMS>*.log 4. Repeat the procedure for each new NMS Master instance created and subjected to Migration.

Supprim : Customize the application software on target system
5.3.2 Create DB schema reference files
If you are migrating a 1354RM, execute the following commands to create RM DB schema reference files: Login into the system as user snml Startup 1354RM database: ... ... ... ... $ $ $ $ cd /usr/Systems/1354RM_1-7.4.9 . ./.snmlrc cd ORACLE/databases/dbnml/etc start_db
Get a snapshot of the database: ... $ mkdir /alcatel/DEPOT/NR81PL2_RM_DB_Ref (if you get an error execute, as root: chmod 777 /alcatel/DEPOT e repeat the command) ... $ chmod 777 /alcatel/DEPOT/NR81PL2_RM_DB_Ref ... $ cd /usr/Systems/1354RM_1/ORACLE/script/ ... $ ./MIB_Contents get /alcatel/DEPOT/NR81PL2_RM_DB_Ref Stop 1354RM database:
1AA 00014 0004 (9711) A4
... $ cd /usr/Systems/1354RM_1-7.4.9 ... $ cd ORACLE/databases/dbnml/etc
ED
RELEASED
Optics
78/157
... $ stop_db If you are upgrading a 1354BMETH, execute the following commands to create BMETH DB schema reference files:
Login into the system as user bmml Startup 1354BMETH database: ... ... ... ... $ $ $ $ cd /usr/Systems/1354BMETH_1-8.1.5 . ./.bmmlrc cd ORACLE/databases/dbnml/etc start_db
Get a snapshot of the database: ... $ mkdir /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref (if you get an error execute, as root: chmod 777 /alcatel/DEPOT e repeat the command) ... $ chmod 777 /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref ... $ cd /usr/Systems/1354BMETH_1-8.1.5/ORACLE/script/ ... $ ./MIB_Contents get /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref Stop 1354BMETH database: ... $ cd /usr/Systems/1354BMETH_1-8.1.5 ... $ cd ORACLE/databases/dbnml/etc ... $ stop_db
5.3.3 Install migration tools
In order to export System Configuration and data from source machine and import then on target machine, you have to install migration tools on both machines, source and target, following instructions of paragraph Install Migration Tools in APPENDIX E: DATA Export/Import".
Supprim : Install Migration Tools Supprim : APPENDIX E: DATA Export/Import
5.3.4 Data Export from Source and Import to Target System
NOTE:
From this point and onwards, no changes to the network are allowed the entire system has been completely migrated to the target machine. In case any modification have to be performed on the network configuration, the procedure has to be repeated starting from this step.
For each NMS installed and subjected to migration, perform the export and import of Data executing the following steps: On both machines, predispose a temporary file system for Data Export: ...,sys,root # cd / ...,sys,root # scextendfs /alcatel/ExpTmp <size> Note: to check in advance the needed disk space perform the following command: ...,sys,root # EvalExportSize <NMS>_<NMS Id>--<NMS Ver> Where: <NMS Id> is the NMS instance identification number <NMS Ver> is the NMS version
1AA 00014 0004 (9711) A4
The command returned value must be at least doubled to get the needed free space.
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
79/157
On source machine:
a. execute data export as described in section Data Export of APPENDIX E: DATA Export/Import. a. copy the entire contents of /alcatel/ExpTmp file system on to tape device, by entering the following commands: ...,sys,root # cd /alcatel ...,sys,root # tar cf /dev/rmt/0m ./ExpTmp a. Check the tape contents entering: ...,sys,root # tar tvf /dev/rmt/0m On target machine: b. copy data from tape, by entering the following commands: ...,sys,root # cd /alcatel ...,sys,root # tar xf /dev/rmt/0m c. Perform data import as described in section Data Import of APPENDIX E: DATA Export/Import.
Supprim : Data Export
Supprim : Data Import
5.3.5 Data Conversion
If the NMS is a 1353NM: Perform data conversion has described in APPENDIX F: 1353NM Data Conversion. If the NMS is a 1354RM: Perform data conversion has described in APPENDIX G: 1354RM Data Conversion. If the NMS is a 1354BM-ETH: Perform data conversion has described in APPENDIX H: 1354BM-ETH Data Conversion.
Supprim : APPENDIX F: 1353NM Data Conversion

Supprim : APPENDIX G: 1354RM Data Conversion

Supprim : APPENDIX H: 1354BMETH Data Conversion
5.3.6 System Swap
In this phase we swap the network management systems, switching off the source system and replacing it with the target one. During this chapter we will have a period of no surveillance while the target system is starting. We are going to do the following things in this order: 3. Swap preparation. 4. Swap source system with the target NR8.1PL2 5. Start NR8.1PL2 master systems. 6. Register all NMS with the other ones.
1AA 00014 0004 (9711) A4
7. Verify that the target NR8.1PL2 correctly works.
ED
RELEASED
Optics
80/157
Swap preparation
Before proceed with swap you have to be sure that all system setups are correct for the operating environment, the most relevant data that has to be recover now are related to the DNS and license. 1. Shutdown Alcatel NMS on target system. 2. Restore the DNS configuration file resolv.conf if it was present on source. 3. Review the license files for Poseidon and GOGlobal-UX.
Swap source system with the target NR8.1PL2

The NMS system swap consists of replacing the two servers: 5. Ask all operators to disconnect from the source system. If you are doing a one-shot migration jump directly to point 4, otherwise proceed with next point. 6. If the system you are going to swap is integrated by a higher level one, login as root on the machine hosting the higher level system and execute: ...,sys,root # /alcatel/Kernel/script/deintegration.pl sys <NMS> inst <NMS Id>-<NMS Ver> <nms> <nms Id>-<nms Ver> Where: <NMS> <NMS Id> <NMS Ver> <nms> <nms Id> <nms Ver> higher level system higher level system identification number higher level system version lower level system lower level system identification number lower level system version
...,sys,root # cd /usr/Systems/<NMS>_<NMS Id> ...,sys,root # ./SMF/tools/br/script/addExternalOs.pl b d Decustom old presentation instance: ...,sys,root # /alcatel/Kernel/script/Decustom <NMS> <NMS Id>-<NMS Ver> Where: <NMS> <NMS Id> <NMS Ver> is the NMS product name related to the instance that has to be de-customized is the NMS instance identification number is the NMS version identification number
Cleanup the link structure by removing symbolic links to old presentation instance under /usr/Systems/ Custom new presentation instance: ...,sys,root # cd /alcatel/Install_Wizard ...,sys,root # ./Install.sh custom <NMS> Where the key <NMS> has to be replaced with the NMS name
1AA 00014 0004 (9711) A4
Warning! If the remote higher level system hosts 1354BMETH remember to stop it, reexecute the System Configuration updating EML_PROXY and NML_PROXY configuration and
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
81/157
re-integrate it!
7. If the system you are going to swap integrates a lower level one still in old Network Release, login as root on the machine hosting the lower level system not yet upgraded and execute: ...,sys,root # cd /alcatel/ ...,sys,root # ln s <SNR> 8.1PL2 Where <SNR> has to be replaced with the old Network Release installation sub-directory, that has to be: 7.1D for NR7.1D, NR7.1D PL1, NR7.1D PL2 and all NR7.2 7.3 for NR7.3 7.4 for NR7.4 8.1 for NR8.1 8.1PL1 for NR8.1PL1 ..., sys,root # cd /usr/Systems/ ..., sys,root # ln -s Global_Instance_<Ver>_Master \ Global_Instance_7.1.7_Master ..., sys,root # ln -s /usr/Systems/Global_Instance_7.1.7_Master \ Global_Instance-7.1.7 Where: <Ver> has to be replaced with the old Network Release Global Instance version, that has to be: 7.1.2 for NR7.1D, NR7.1D PL1, NR7.1D PL2 and all NR7.2 7.1.3 for NR7.3 7.1.4 for NR7.4 7.1.5 for NR8.1 7.1.6 for NR8.1PL1 8. Disconnect all LAN connection of source system. 9. Connect all LAN connection of target system. 10. Verify the LAN connectivity: a. Verify the connectivity with the default gateway. b. Verify the connectivity with the DNS server (when it is present). c. Verify the connectivity with the license servers (if there is other ones).
d. Verify the connectivity pinging all the other NMS servers (if any).
NMS Integration
If client instances are installed on the machine, execute: ..., sys,root # /alcatel/Kernel/bin/UpdatePresentation.pl force Then integrate the NMS executing: ..., sys,root # /alcatel/Kernel/script/UpdateNetworkConnections.pl
ED
RELEASED
Optics
82/157
Answer yes to all the integration confirmations requested by the procedure, with the exception of 1354RM Master and 1354BMETH Master configuration, when requested to confirm for PLT and SMF integration of 1354BMETH instance "under" 1354RM instance, answer always no.
Startup NR 8.1PL2 NMS applications & Verify

Do a logout/login, start the NMS instances and check the system behaviour.
1354RM NE and alarm synchronization

Perform the following steps: Login into the system with a graphical interface as alcatel user Start the TMN-OS application Highlight the 1354RM instance clicking on the related icon shown in the OSs object area Start 1354RM user interface (browser) clicking on the related button Select the nodes that you want to synchronize: Table 12. Choose Actions -> Synchronize -> Synchronize NE Table 13. Choose Actions -> Synchronize -> Synchronize Alarm
1354RM Audit
The Audit procedure allows to verify 1354RM alignment, taking care of real attributes value read from NE. Perform the following steps: Login into the system with a graphical interface as alcatel user Start the TMN-OS application Highlight the 1354RM instance clicking on the related icon shown in the OSs object area Start 1354RM user interface (browser) clicking on the related button Select the Q3 nodes on which you want to perform the audit: Table 14. Choose Actions -> Configure Download -> Disable Table 15. Choose Actions -> Consistency Audit -> Notify Audit Table 16. Select the related NEs and search for Not aligned objects and Not aligned objects (traffic impacting) The panels show the objects whose value is not aligned between NEs and 1354RM If 1354RM manages QB3* NEs, perform the following actions: Table 17. From RM browser select the nodes on which you want to perform the audit Table 18. Choose Actions -> Configure Download -> Disable Table 19. Open PMC and change 1354RM Run Level to 4 Network Consistency 3. Select one node a time and choose Actions -> Consistency Audit -> Global
1AA 00014 0004 (9711) A4
Table 20. Select the related NEs and search for Not aligned objects and Not aligned objects (traffic impacting)
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
83/157
The panels show the objects whose value is not aligned between NEs and 1354RM
4. From PMC, change 1354RM Run Level to 0 Full Functionality In case of misalignment on 1354RM objects (expecially if traffic impacting) contact TEC, in order to define the action to perform for 1354RM realignment, otherwise on selected nodes perform Actions -> Configure Download -> Enable
1354BMETH align up
The Align Up procedure allows to realign 1354BMETH taking care of real attributes value read from NE. This procedure is mainly used as a post-migration step and has to be executed after an Audit procedure. Perform the following steps: 1. Login into the system with a graphical interface as alcatel user 2. Start the TMN-OS application 3. Highlight the 1354BM instance clicking on the related icon shown in the OSs object area 4. Start 1354BMETH Construction graphical user interface clicking on the related button 5. Perform an audit: Choose Utilities -> Audit/Align/Reserve -> Start Procedure Confirm the start of the procedure and select the Auditable NEs on which to execute the audit. 6. Start 1354BMETH Ethernet Management graphical user interface clicking on the related button 7. Choose Utilities -> Align Up in order to display the Align Up panel The panel shows the objects whose value is not aligned between NEs and 1354BMETH Choose the objects you want to align up from the shown list and confirm the request.
Alarm Federation configuration

1354RM pre-OTN to OTN migration

ED
RELEASED
Optics
84/157
6
VERIFY PRE-CONDITIONS Overview
In this chapter are summarised all needed steps to be performed in advance with respect the migration in order to successfully perform the update or ISE process. These steps should be performed some weeks in advance with respect the start of the upgrade or ISE in order to identify and solve all critical issues.
6.1
Check software requirements Overview
This paragraph describes the steps to identify software to be updated, and the software needed to perform the upgrade or ISE procedure: 1. Identify the current software 2. Identify the target software
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
85/157
6.1.1 Identify the current software Overview

The first important point is to clearly identify the software installed. To do that you have to: 1. Identify the NMS predisposed. 2. Retrieve NMS configuration data for each instance. 3. Check the 1359HA Configuration. 4. Identify application software level.
Identify the NMS predisposed

You need first to check for which NMS the machine has been predisposed. Do the following: 1. Login the system as user root and open a terminal. 2. Lunch scmanageswp tool by entering: ...,sys,root # scmanageswp
3. Press 2 in order to show View predisposed SWP, an output like the following will be provided: SWP predisposed on system SWP Name --------------1353NM 1354RM OS_KERNEL SWP Version Session ----------- ------7.0 7.1 7.1.2
Total number of SWP on this system is: 3 [Enter] to continue. Note: the information shown depends from the specific configuration installed on your machine. 4. Fill the table Upgrade/ISE - Software Packages and Data Instances you can find in the Appendix A: Summary tables, columns SWP Name and SWP Version with the values displayed. 5. Press [Enter], then SWP MAIN MENU appears again. 6. Select [5], View created SWP INSTANCE. An output similar to the following will appear. INSTANCE created on system SWP Name --------------1353NM 1354RM OS_KERNEL SWP Version ----------7.0 7.1 7.1.2 INSTANCE Number --------------7 2 1 INSTANCE Dimension Ses... ------------------- ---1353NM_IM_Medium 1354RM_IM_Medium OSKERNEL
Mis en forme : Police :Gras, Italique, Anglais (tats-Unis) Mis en forme : Police :Gras, Italique, Anglais (tats-Unis)
Supprim : Upgrade/ISE - Software Packages and Data Instances

Total number of INSTANCE on this system is: 3 [Enter] to continue.

1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
86/157
Note: the information shown depends from the specific configuration installed on your machine. 7. Fill the table Upgrade/ISE - Software Packages and Data Instances you can find in the Appendix A: Summary tables, columns Instance Number and Instance Size.
Mis en forme : Police :Gras, Italique, Anglais (tats-Unis)

Supprim : Upgrade/ISE Software Packages and Data Instances
8. Press [Enter], to go back to SWP MAIN MENU and e to exit the procedure.
Retrieve NMS instance configuration data

It is now requested to save the NMS instance configurations since the migration/upgrade process does not keep them. Here after the procedure to retrieve the relevant data: 1. Login the system as root with graphical interface. 2. Start Kernel customize script by entering ...,sys,root # /alcatel/Kernel/script/Custom The following window will be shown on the screen:
Mis en forme : Police :Gras, Italique, Anglais (tats-Unis) Mis en forme : Police :Gras, Italique
Figure 13 - Prerequisite System Instances List Window
3. Move the pointer on Choose_one button, press the mouse selection button. 4. Press the mouse selection button and choose one instance you have to upgrade from the shown list ( move the pointer on the instance name to be selected and release it) 5. Click on Action pull down menu, select Apply & Exit to activate your choice. 6. Fill the table Upgrade/ISE - NMS Instance Information you can find in the Appendix A: Summary tables, section configuration tables, with the corresponding information displayed. 7. Select Close, from the Action pull down menu, to close the window without start any action. Ignore the error message shown on the terminal window. 8. Repeat actions from 2 to 7 for each instance registered in Upgrade/ISE - Software Packages and Data Instances of Appendix A: Summary tables.
Supprim : Upgrade/ISE NMS Instance Information

Check the 1359HA Configuration

Alcatel TMN foreseen two High Availability product: 1359HA OS-Resilience and 1359HA OS-Cluster. The upgrade procedure depends by this software; if one of them is present, please refer to the specific administration guide.
Mis en forme : Police :Gras, Italique, Anglais (tats-Unis) Mis en forme : Police :Gras, Italique, Anglais (tats-Unis)
Supprim : Upgrade/ISE Software Packages and Data Instances

Supprim : Appendix A: Summary tables 1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
87/157
Identify NMS Application software level

To be able to upgrade the NMS application to the target release you have to know which is the current one. Hereafter it is explained how to identify any NMS component version and verify when the NMS upgrade prerequisite are met.
Login the system with a graphical interface as user alcatel. Start the TMN-OS application., by clicking on icon: Highlight interesting NMS instance by clicking on the related icon shown in the OSs object area. Press the [Information] button to get the NMS detailed description.
Check that all the software items shown in table Upgradeable NMS software part of Appendix B: SW Packages are present in the information window.
Supprim : Upgradeable NMS software Supprim : Appendix B: SW Packages
ED
RELEASED
Optics
88/157
6.1.2 Identify the target software

Overview
Hereafter are described the steps necessary to correctly identify the software to be installed.
Bill of material
To correctly identify the distribution kits needed to perform the upgrade/migration please refer to the table .
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
89/157
6.2
Check Hardware requirements

Overview
The upgrade/migration requires some hardware requirements are met to be able to carry out the entire process. This paragraph describes the checks that have to be performed.
Disk Requirements
The target software uses more space on disk with respect the current one; moreover the upgrade process requires an extra temporary space requirement. To be sure to be able complete the upgrade, you have to verify the amount of free space available the disks. Hereafter the instruction to perform these checks: Compute the required space. Check left available space on in use disks. Check unused disks.
Compute the Required Space

The free disk space required depends on the software currently installed, the NMS installed, the upgrade method chosen. To compute the amount of space requested to carry out this activity please refer to APPENDIX C: Required Disk Space.
Supprim : APPENDIX C: Required Disk Space
Check Available Disk Space

Now you have to compare the free space you need with the one you currently have on disks. To know the free space currently available do the following: Login the system as user root. Launch the following command: ...,sys,root # scextendfs -i Do not Press [Enter} to continue and take note of the value of FreePE. This value corresponds to the amount of free Physical Extents (PE). Check if the amount of free physical extends is higher than the required one you computed in the previous section of this chapter. If the free space is higher please skip the next section.
ED
RELEASED
Optics
90/157
1AA 00014 0004 (9711) A4
Check Available Unused Disk Units

If you dont have enough space on disks (see previous section) to perform the requested update activities you should verify if some unused disks are available: 1. Login the system as user root. 2. Launch the following command: ...,sys,root # scextendfs -i Press [Enter} to continue. You should get an output similar to the following: Disks Selection ______________________________________________________________________ Device MByte Hardware Path Usage Type VolGroup ______________________________________________________________________ c1t2d0 8680 0/0/1/1.2.0 Pri_Boot _Main_ vg00 c2t2d0 8680 0/0/2/0.2.0 Alt_Boot _Copy_ vg00 c4t0d0 8680 0/4/0/0.0.0 __Data__ _Main_ vg00 c4t1d0 8680 0/4/0/0.1.0 _(free)_ ______ ________ c5t8d0 8680 0/6/0/0.8.0 __Data__ _Copy_ vg00 c5t9d0 8680 0/6/0/0.9.0 _(free)_ ______ ________ ______________________________________________________________________ Press [Enter] to continue.... 3. Look for the disks that have the value _(free)_ in the column Usage to identify the disk units not yet allocated to a volume group, and look at the Mbyte column to know the disk size (bold underlined in the output example). 4. Add the Mega bytes of the disk to the space left on the current volume group configuration. Note: If you have mirror protection, the upgrade requires adding a double hard disk amount to the configuration, and also the SCSI disk chain can be relevant (see 1350 Installation guide [1] paragraph OPERATING SYSTEM Installation paragraph).
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
91/157
6.3
Check Software requirements

Poseidon License Configuration for ISE purposes

Please note that there is significant difference between NR7.1D/7.2 PL2 license to compare with NR8.1PL2 . Therefore when using ISE Migration approach its necessary to generate and adapt license.dat file accordingly.
ED
RELEASED
Optics
92/157
7
PLATFORM UPGRADE Overview
This chapter describes how to upgrade the HP-UX 11i platform and the third party software platform to correctly hold the NR8.1PL2 software. Note: The installation from Network Depot can be performed only after the depot set-up, for more information refer the 1350 Rel8.1PL2 Installation Guide [1].
7.1
Upgrade Platform to the latest OS-Conf patch
This paragraph describes how to execute the software platform upgrade to the lastest OS-Conf patch. Note: The OS-Conf upgrade must be executed without using GoGlobal-UX.
3. Start the upgrade procedure by entering: ...,sys,root # cd / ...,sys,root # /SCINSTALL/etc/scupgrade 4. Enter 1 to choose the CDROM or 2 to choose the DEPOT and consequently follow the related section: --------------------------------------------------------OS-Conf 7.1.1 P08 Upgrade Procedure --------------- LAYERED PRODUCTS Repository ------------1 - DVD/CDRom 2 DEPOT q - quit Insert choice and press [Enter]: 5. Next question depends by chosen repository: a. For CD/DVD you have to provide driver file name, the proposed default is usually correct. Enter q to Quit or the CD device [def=/dev/dsk/c2t2d0]: b. For depot you have to enter the depot host name followed by /alcatel/SCDEPOT (example: rmsouth:/alcatel/SCDEPOT) when you get on the screen the following message: --- Depot selection for LAYERED Products installation Enter 'q' to Quit or the Depot absolute path name: 6. The procedure will check the file systems free space, and enlarge them when needed. If any enlarged file system is in use, the following question will be issued: File System:/dev/vg00/lvol5 is busy, check process with pid(s): . Press: [T] for Try again, [A] for Abort, [R] for Reboot, then press[Enter] Reply R to execute file system extension at the next reboot: ----
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
93/157
Press [y] for yes or [n] for no, then press [Enter] In this case you must stop all the activities and reply with y. After the reboot the file system will be enlarged, and installation will start automatically. 7. Login as user root 8. Check for any error during the installations process: ...,sys,root # more /SCINSTALL/scinstall.log
ED
RELEASED
Optics
94/157
1AA 00014 0004 (9711) A4
----------------------- ATTENTION -----------------------------Upgrade OS-Conf install product(s) and/or Patch(es) System could automaticaly reboot All Application must be stopped (example: RM, NM, Resilience ec...) Do you want continue ?
8
APPENDIX A: SUMMARY TABLES Overview
This appendix summarises all table that must be useful to store the information requested during the migration/upgrade process. You should print this appendix and use it when requested inside the document.
Configuration tables
Use this table to insert the information about the software packages for which the machine has been predisposed. scmanageswp Information SWP Name OS-KERNEL SWP Version NMS Instance Number Instance Size/Type 1 OSKERNEL
Table 21. Upgrade/ISE - Software Packages and Data Instances Use this table to insert the information concerning the instance configuration, for each instance to be upgrade/migrated.
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
95/157
System_Version System_Instance_Id System_Instance_Role System_Instance_Name Master_HostName Master_Kernel_Type Driver_Version Language NMS Instance System_Version System_Instance_Id System_Instance_Role System_Instance_Name Master_HostName Master_Kernel_Type Driver_Version Language
System_Version System_Instance_Id System_Instance_Role System_Instance_Name Master_HostName Master_Kernel_Type Driver_Version Language NMS Instance System_Version System_Instance_Id System_Instance_Role System_Instance_Name Master_HostName Master_Kernel_Type Driver_Version Language Table 22. Upgrade/ISE - NMS Instance Information
ED
RELEASED
Optics
96/157
1AA 00014 0004 (9711) A4
NMS Instance
NMS Instance
Network Management Subsystem

Install Wizard Version for NR7.4 OS-KERNEL 7.1.2-P13 1353NM 7.3.6-P09 1354RM 7.4.3-2-P9 1354BM 7.3.0.5-P2RP4
OS-KERNEL 1353NM 1354RM 1354BMETH
Table 23. NR7.4 NMS version for Install_Wizard
1354RM Process Configuration LOG RM_PerfMon PMDS_UI_SubSystem EPIM_SubSystem RM_Tsd-Feps Identification Numbers RM_USM RM_MTNM PMDS_DB_SubSystem RM_WEB System_Tuning Alarm_SubSystem RM_F-Agent ORACLE_DB Security_SubSystem
RM_Snmp-Feps Identification Numbers
Table 24. 1354RM Process Configuration
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
97/157
ED 1353NM Process Configuration Table 25. 1353NM Process Configuration

1AA 00014 0004 (9711) A4
Optics
RELEASED
98/157
9
APPENDIX B: SW PACKAGES
Overview
This appendix provides an overview on the SW configuration needed to perform the upgrade/migration.
Upgradeable NMS
The table hereafter summarises the versions of Alcatel NMS that are supported. Software Component Network Release 7.1T PL1 OS-Kernel 7.1.1
OSK-ENGINE 7.1.1 Patch P01 OSK-ENGINE 7.1.1 Patch P02 OSK-ENGINE 7.1.1 Patch RP02.1 OSK-ENGINE 7.1.1 Patch RP02.2 OSK-ENGINE 7.1.1 RP2.3 OSK-ENGINE 7.1.1 RP2.4 OSK-ENGINE 7.1.1 RP2.5 OSK-ENGINE 7.1.1 RP2.6 OSK-ENGINE 7.1.1 RP2.7 OSK-ENGINE 7.1.1 RP2.8
Network Release 7.1D/7.2 PL2 OS-Kernel 7.1.2

OSK-ENGINE 7.1.2 Patch P08 OSK-ENGINE 7.1.2 Patch P09 OSK-ENGINE 7.1.2 Patch RP09.1 OSK-ENGINE 7.1.2 Patch RP09.2 OSK-ENGINE 7.1.2 Patch RP09.3
Network Release 7.3 OS-Kernel 7.1.2

OSK-ENGINE 7.1.2 Patch P01 OSK-ENGINE 7.1.2 Patch P08 OSK-ENGINE 7.1.2 Patch RP08.1 OSK-ENGINE 7.1.2 Patch RP08.2
OS-Kernel
1353NM 1354RM 1354BMETH 1355VPN? 1354BMPR
7.0.13 7.1.42 N.A.
7.0.15 7.1.80 7.1.1 P14 7.3.0.5
7.0.14 7.3.1 7.1.1 P14
N.A. N.A. Table 26. Upgradeable NMS software
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
99/157
NR7.4 NMS Versions

The versions shown in the following table must be read this way: 1. Version out of brackets is the one that have to be provided for predisposal. 2. Version between brackets is the real product version. Software Component NR 7.1T Versions NR7.4 Versions Data Conversion N.A. YES YES New Instance
OS-Kernel 1353NM 1354RM
7.1 (7.1.1 any P) 7.0 (7.0.12 any P ) 7.1 (7.1.42)
7.1 .4(7.1.2 P13) 7.3 (7.3.6 P9) 7.4 (7.4.3-2)
YES YES YES
Table 27. NMS Versions from NR7.1 to NR 7.4
Software Component
NR7.1D/7.2 Versions 7.1.2 (7.1.2 any P) 7.0 (7.0.15 any P) 7.1 (7.1.80) 7.1 (7.1.1 P12) 7.3 (7.3.0.5 P1)
NR7.4 Versions
Data Conversion N.A. YES YES YES NO
New Instance
OS-Kernel 1353NM 1354RM 1354BMETH
7.1 (7.1.2 P13) 7.3 (7.3.6 P9) 7.4 (7.4.3-2) 7.3 (7.3.0.5 P2) 7.3 (7.3.0.5 P2)
YES YES YES YES NO
Table 28. NMS Version from NR 7.1D/7.2 to NR 7.4
Software Component OS-Kernel 1353NM 1354RM 1354BMETH
NR7.3 Versions 7.1.3 (7.1.2 any P) 7.0 (7.0.14 any P) 7.3 (7.3.1 any P) 7.1 (7.1.1 P14)
NR7.4 Versions 7.1 .4(7.1.2 P13) 7.3 (7.3.6 P9) 7.4 (7.4.3-2) 7.3 (7.3.0.5 P2)
Conversion N.A. YES YES YES
New Instance YES YES YES YES
Table 29. NMS Version from NR7.3 to NR7.4
ED
RELEASED
Optics
100/157
NMC keys list

This table shows the relation between the Network Management Component (NMC) and the key that has to be used in the installation phase <NMC> key 1359ISN 1359IOO ETH-MEDIATOR Table 30. NMC keys Component ISN IOO (GENOS) Ethernet Mediator
NMS Administrator Users

This table shows the administrator specific user for each NMS. Network Management Subsystem 1353NM 1354RM 1354BM ETH User axadmin snml bmml
Table 31. NMS Specific Administration Users
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
101/157
10 APPENDIX C: REQUIRED DISK SPACE

The following table shows the disk space requested for swap, program installation, and depot packages. The value are specified in M bytes.
NMS OS-Kernel 1353NM 1354BM ATM 1354BM ETH 1354BM PR 1354RM 1354SY 1359HA 1359IOO 1359ISN
Swap Required 100 500 500 500 200 500 500 N.A. N.A. N.A.
Software Size 3600 7500 1120 1120 100 1320 1000 10 N.A. N.A.
Depot Package Size 1390 3210 100 285 41 1250 105 3 15 42
Table 32. Disk requirements for NMS Software for NR8.1 PL2
ED
RELEASED
Optics
102/157
NMS
Master Small Swap Data 200 3000 3000 3000 2700 3500 1000 3000 600
Master Medium Swap N.A. 2000 3500 3500 3500 12500 1500 3500 200 Data N.A. 5000 5000 5000 4000 5000 2000 5000 1500
Master Large Swap N.A. 3000 7500 7500 3500 21000 2500 7500 500 Data N.A. 9000 9000 9000 6000 9000 5000 9000 3000
Presentation Swap N.A. 250 2000 2000 3000 2000 300 2000 400(*) Data N.A. 250 200 200 500 400 300 400 160(*)
OS-Kernel 1353NM 1354BM ATM 1354BM ETH 1354BM PR 1354RM 1354SN 1354SY 1359HA
0 1500 1500 2000 3500 8000 1000 1500 100
Table 33. Disk requirements for NMS Software for NR8.1 PL2
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
103/157
11 APPENDIX D: NMS SWPDESC, OS-Conf and Install Wizard Upgrade Overview

This appendix explains the procedure to upgrade NMS Software Description (SWPDESC), the OS-Conf engine and the Install Wizard tool.
Remove Current OS-Conf, OSC-3PP and SWPDESC

Login into the system as user root and remove the installed software description and OS-Conf. In case of HP9000 PA-RISC system: ...,sys,root # swremove OS-CONF OSC-3PP SWPDESC In case of HP ITANIUM system: ...,sys,root # swremove OS-CONF OSC-3PP-UXIA SWPDESC
Install OS-Conf and OSC-3PP

If CD/DVD installation: Insert the CD/DVD medium into the media drive. ...,sys,root # mount o rr /dev/dsk/<cdrom device file> /SD_CDROM In case of HP9000 PA-RISC system: ...,sys,root # swinstall s /SD_CDROM/OS-Conf<version>.sd OS-CONF OSC-3PP In case of HP ITANIUM system: ...,sys,root # swinstall s /SD_CDROM/OS-ConfUX<version>.sd OS-CONF OSC-3PP-UXIA Dismount the CD by entering the following command: ...,sys,root # umount /SD_CDROM If DEPOT installation: Install OS-Conf by entering: In case of HP9000 PA-RISC system: ...,sys,root # swinstall s <depot host>:<depot dir> OS-CONF OSC-3PP In case of HP Integrity ITANIUM system: ...,sys,root # swinstall s <depot host>:<depot dir> OS-CONF OSC-3PP-UXIA
Install NMS SWPDESC, and Install Wizard

Note: Install_Wizard uses /alcatel/DEPOT as a temporary area to store temporary files needed for installation. Therefore, it is strongly suggested to have /alcatel/DEPOT with a minimum of 1Gb free space before to start Install_Wizard tool This section explain how to install the target software description and OS-Conf:
ED
RELEASED
Optics
104/157
If CD-ROM installation: Replace the CD in the drive and install new software description by entering hereafter command sequence:
...,sys,root ...,sys,root ...,sys,root ...,sys,root ...,sys,root ...,sys,root ...,sys,root If DEPOT installation:
# # # # # # #
scmountcd /dev/dsk/<cdrom device file> /SD_CDROM swinstall s /SD_CDROM/SWPDESCV<version>.sdpkg \* cd /SD_CDROM sh ./Install_Wizard-R<version> sh ./Install_Wizard_CMD-R<version> cd / umount /SD_CDROM
Retrieve the software from depot machine:

...,sys,root ...,sys,root ...,sys,root ...,sys,root ...,sys,root ...,sys,root # # # # # # mkdir p /alcatel/DEPOT chmod 777 /alcatel/DEPOT cd /alcatel/DEPOT rcp p <depot host>:<directory>/Install_Wizard-R<version> . rcp p <depot host>:<directory>/Install_Wizard_CMD-R<version> . rcp p <depot host>:<directory>/SWPDESCV<version>.sdpkg .
Install new software description by entering hereafter command sequence: ...,sys,root # swinstall s /alcatel/DEPOT/SWPDESC_V<version>.sdpkg \* ...,sys,root # sh ./Install_Wizard-R<version> ...,sys,root # sh ./Install_Wizard_CMD-R<version> In both cases execute: ...,sys,root # scupdate_swpdesc all all replace Note: in case of installation from scratch, the last command will terminate with error; ignore the error and continue the installation. Note: neglect the following errors, and similar, if present. ERROR: Not installed descriptor file for OS_KERNEL 7.1.4 ERROR: Not installed descriptor file for 1353NM 7.0
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
105/157
12 APPENDIX E: DATA EXPORT/IMPORT Overview

This appendix describes how to install and use export/import tool to move the data from a file system to an other. Hereafter the steps described in this appendix: 1. Install Migration tools 2. Export system configuration of the leaving version instance. 3. Import system configuration into the coming version instance. 4. Export data from then leaving version instance workspace. 5. Importing data into the coming version instance workspace
Install Migration Tools

Retrieve the Migration Tools MGT_R3036.sdpkg.gz (cksum & size: 3672562568 122880) and install them executing: Login into the system as user root Install the MGT tools (one only line): ...,sys,root # swinstall -s /alcatel/DEPOT/MGT_R3036.sdpkg.gz x allow_incompatible=true x reinstall=true \* ...,sys,root # /tmp/migration_tools/Install Dont worry of the following message: rm: /alcatel/MGT/* non-existent
ED
RELEASED
Optics
106/157
System Configuration Export

This paragraph describes how to export the system configuration of a NMS Master in an archive file: 1. Define the source Network Release entering: ...,sys,root # cd / ...,sys,root # mkdir /alcatel/ExpTmp/<NMS>_<NMS Id> ...,sys,root # export KERNEL_RELEASE=<NR Version> Where: < NR Version > is the Network Release Source version: 7.1D for NR7.1D, NR7.1D PL1, NR7.1D PL2 and all NR7.2. 7.3 for NR7.3. 7.4 for NR7.4. 8.1 for NR8.1. 8.1PL1 for NR8.1PL1
2. Launch the Export GUI: ...,sys,root # G_ExpMigData The following window is displayed:
Figure 14 - Export GUI window
3. Select the NMS instance from INST_ID list. Enter /alcatel/ExpTmp/<NMS>_<NMS Id> into WORK_AREA parameter. Select none value for GROUPS parameter. Select OFF value for MIGR_CFG parameter. Select ON value for KEEP_SYSCONF parameter. Then choose Actions -> Apply & Exit
1AA 00014 0004 (9711) A4
4. Verify that the Export of the system config has been correctly executed checking the log file /tmp/ExpMigData.log
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
107/157
5. Verify that /alcatel/ExpTmp/<NMS>_<NMS Id> directory contains an archive file in the format: <NMS>_<NMS Id>-<NMS Version>_expdata-<data_type>.tar.gz that has to be used during import procedure.
System Configuration Import

This paragraph describes how to import the system configuration of a NMS Master from an archive file: Define the target Network Release entering: ...,sys,root # cd / ...,sys,root # mkdir /alcatel/ExpTmp/<NMS>_<NMS Id> ...,sys,root # export KERNEL_RELEASE=8.1PL2 Launch the Import GUI: ...,sys,root # G_ImpMigData The following window is displayed:
Figure 15 - Import GUI window
Select the target NMS instance from INST_ID list. Enter /alcatel/ExpTmp/<NMS>_<NMS Id> into WORK_AREA parameter. Enter the full path name of the archive created with Export procedure in ARCHIVE_NAME parameter (point 5 of System Configuration Export).
1AA 00014 0004 (9711) A4

Supprim : System Configuration Export
Select none value for GROUPS parameter.
ED
RELEASED
Optics
108/157
Select OFF value for MIGR_CFG parameter. Select ON value for KEEP_SYSCONF parameter.
Then choose Actions -> Apply & Exit Verify that the Import of the system config has been correctly executed checking the log file /tmp/ImpMigData.log and files in /alcatel/ExpTmp/<NMS>_<NMS Id>/MigrDataRestoring/Log directory.
Data Export
Note: Before execute the data export procedure, archive the AS current alarms.
This paragraph describes how to export the data of a NMS Master in an archive file: Define the source Network Release entering: ...,sys,root # cd / ...,sys,root # mkdir /alcatel/ExpTmp/<NMS>_<NMS Id> ...,sys,root # export KERNEL_RELEASE=<NR Version> Where: < NR Version > is the Network Release Source version: 7.1D for NR7.1D, NR7.1D PL1, NR7.1D PL2 and all NR7.2 7.3 for NR7.3 7.4 for NR7.4 8.1 for NR8.1 8.1PL1 for NR8.1PL1
Only if you are going to export RM data from NR7.4 or NR8.1 execute the following W/A: edit the file /usr/Systems/1354RM_1/PMDS_DB/script/backupDB.pl and change the line 29 from use mysql ; to # use mysql ; Update DataGroups.cfg file: ...,sys,root # update_DG <NMS>_<NMS Id>-<NMS Version> Where: <NMS Version> <NMS Id> <NMS Version> Launch the Export GUI: ...,sys,root # G_ExpMigData The Export GUI window is displayed (see Figure 17 - Export GUI window). Select the NMS instance from INST_ID list. Enter /alcatel/ExpTmp/<NMS>_<NMS Id> into WORK_AREA parameter. For GROUPS parameter select one of the following values:
1AA 00014 0004 (9711) A4
is the NMS product. is the NMS instance identification number. is the NMS source version.
Network: can be used for NM, RM and BMETH and exports NEs data for NM, Oracle database for RM and BMETH
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
109/157
PM: can be used only for NM and exports MySQL database and PM data
Network_and_PM: can be used only for NM and exports NEs data, MySQL database and PM data Alarms: can be used for NM, RM and BMETH and exports current and archived alarms any : can be used for NM, RM and BMETH and exports all data none Note: in case of migration with spare only Network and PM can be exported Note: archived PM are not migrated Select ON value for MIGR_CFG parameter. Select OFF value for KEEP_SYSCONF parameter. Then choose Actions -> Apply & Exit Neglect the following messages, if present: interpreter "/opt/perl/bin/perl" not found file link resolves to "/opt/perl_32/bin/perl Verify that the Export of the data has been correctly executed checking the log file /tmp/ExpMigData.log and files in /alcatel/ExpTmp/<NMS>_<NMS Id>/MigrDataRepository/Log directory. Neglect the following messages, if present: in file NE_DB_backup.log /usr/Systems/1353NM_1-7.0/SMF/script/axdbread[45]: axremsh: not found in export_db.log: EXP-00091: Exporting questionable statistics. Verify that /alcatel/ExpTmp/<NMS>_<NMS Id> directory contains a file in the format: <NMS>_<NMS Id>-<NMS Version>_expdata-<data_type>.tar.gz that has to be used during import procedure. Restore DataGroups files: ...,sys,root # update_DG <NMS>_<NMS Id>-<NMS Version> restore Ignore warnings like the following:
WARNING: restore invoked on a not-existing ./PMDS_DB/Kernel/conf/MIGR.cfg.1354RM_1-7.4 file!! WARNING: restore invoked on a not-existing ./RM_DB/Kernel/conf/MIGR.cfg.1354RM_17.4 file!!
Data Import
This paragraph describes how to import the data of a NMS Master from a temporary area: Check the file /opt/oracle10g/10.2.0.3/bin/sqlplus. If the UID bit is set, like in this example: -rwsr-s--x 1 oracle oinstall 78336 Apr 7 2008 sqlplus
unset it with the command: ...,sys,root # chmod a-s /opt/oracle10g/10.2.0.3/bin/sqlplus
ED
RELEASED
Optics
110/157
so that you have: -rwxr-x--x 1 oracle

oinstall
78336 Apr 7 2008 sqlplus
Define the target Network Release entering: ...,sys,root # cd / ...,sys,root # mkdir /alcatel/ExpTmp/<NMS>_<NMS Id> ...,sys,root # export KERNEL_RELEASE=8.1PL2 Update DataGroups.cfg file: ...,sys,root # update_DG <NMS>_<NMS Id>-<NMS Version> Where: <NMS> <NMS Id> <NMS Version> Launch the Import GUI: ...,sys,root # G_ImpMigData The Import GUI window is displayed (see Figure 15 - Import GUI window). Select the target NMS instance from INST_ID list. Enter /alcatel/ExpTmp/<NMS>_<NMS Id> into WORK_AREA parameter. Enter the full path name of the archive created with Export procedure in ARCHIVE_NAME parameter (point 0 of Data Export). Select any value for GROUPS parameter. Select ON value for MIGR_CFG parameter. Select OFF value for KEEP_SYSCONF parameter. Then choose Actions -> Apply & Exit Neglect the following messages, if present: interpreter "/opt/perl/bin/perl" not found file link resolves to "/opt/perl_32/bin/perl Verify that the Import of the data has been correctly executed checking the log file /tmp/ImpMigData.log and files in /alcatel/ExpTmp/<NMS>_<NMS Id>/MigrDataRestoring/Log directory. When importing 1354RM or 1354BMETH database inside import_db.log neglect messages like these:
ORA-00942: table or view does not exist ORA-02273: this unique/primary key is referenced by some foreign keys ORA-02443: Cannot drop constraint - nonexistent constraint
Supprim : 7
is the NMS product. is the NMS instance identification number. is the NMS target version. (e.g.: for 1354RM is 7.4.9).

Supprim : Data Export
IMP-00015: following statement failed because the object already exists IMP-00041: Warning: object created with compilation warnings
Instead check Appendix N if import_db.log contains one of the following errors:

1AA 00014 0004 (9711) A4
ORA-01650: unable to extend rollback segment xxx by xxx in tablespace <ts_name>
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
111/157
ORA-01652: unable to extend temp segment by xxx in tablespace <ts_name> ORA-01653: unable to extend table xxx by xxx in tablespace <ts_name> ORA-01654: unable to extend index xxx by xxx in tablespace <ts_name> ORA-01659: unable to allocate MINEXTENTS beyond xx in tablespace <ts_name>
Neglect the following messages, if present: in file ASdbManager_restore.log //usr/Systems/1353NM_1-7.4.5/AS/script/../data/ascurim//configDb.sav file not found in file SEC_AC_adjust.log /usr/local/bin/AC_create_links: /usr/Systems/1353NM_1-7.4.5/ac_info: not found. ERROR: Cannot open file: /usr/Systems/1353NM_1-7.4.5/ac_info/../Kernel/data/INDEX at /alcatel/7.1D/Kernel/etc/../lib/lib_perl/CfgParser.pm line 83. ERROR: Cannot open file: /usr/Systems/1353NM_1-7.4.5/ac_info/../Kernel/data/INDEX at /alcatel/7.1D/Kernel/etc/../lib/lib_perl/CfgParser.pm line 83. sed: Cannot find or open file users.ac. in file SEC_import.log Error, line #2080: Unknown Function. Error, line #3873: Unknown Application. Error, line #2084: Name Already Used. in file restoreDB_PM.log /usr/local/bin/pmdb_restore[3]: /usr/Systems/1353NM_2-7.3//MYSQL/script/envMYSQL.sh: not found. in file as_imp_action.log glob failed (child exited with status 1) at /usr/Systems/1353NM_2-7.4.5/AS/script/migrate.pl line 10. in file updateSMFconfig.log ERROR: keys file not found Restore DataGroups files: ...,sys,root # update_DG <NMS>_<NMS Id>-<NMS Version> restore Where: <NMS> <NMS Id> <NMS Version> is the NMS product. is the NMS instance identification number. is the NMS target version. (e.g.: for 1354RM is 7.4.9).
Ignore warnings like the following:

WARNING: restore invoked on a not-existing ./PMDS_DB/Kernel/conf/MIGR.cfg.1354RM_1-7.4 file!! WARNING: restore invoked on a not-existing ./RM_DB/Kernel/conf/MIGR.cfg.1354RM_17.4 file!!
ED
RELEASED
Optics
112/157
1AA 00014 0004 (9711) A4
13 APPENDIX F: 1353NM DATA CONVERSION Overview

This appendix describes the steps to be performed in order to convert the data from the source to the target version. Please use this appendix only when referenced to.
1353NM Data conversion

Warning! Conversion scripts can be launched only once! If you have to relaunch them, it is mandatory to re-import and re-convert data from the beginning. Login as axadmin user and execute the following command: ... ... ... ... $ $ $ $ /usr/Systems/1353NM_1-7.4.5/MYSQL/script/db_start.pl cd /usr/Systems/1353NM_1-7.4.5/PMDS_DB/script ./pms_upgrade /usr/Systems/1353NM_1-7.4.5/MYSQL/script/db_stop.pl
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
113/157
14 APPENDIX G: 1354RM DATA CONVERSION Overview

This appendix describes the steps to be performed in order to convert the data from the source to the target version. Please use this appendix only when referenced to .
1354RM DB conversion
Warning! Conversion scripts can be launched only once! If you have to relaunch them, it is mandatory to re-import and re-convert data from the beginning. To perform the DB conversion the following sections must be followed in sequence: 1. Retrieve conversion tools 2. Define how to migrate to 1354RM 7.4.9 3. Install and customize DB migration tool to get to 1354RM 7.3 DB 4. Convert DB to 1354RM 7.3 level 5. Install and customize DB migration tool to get to 1354RM 7.4s3 DB 6. Convert DB to 1354RM 7.4s3 level 7. Create Payload MAP tables entries 8. Install and customize DB migration tool to get to 1354RM 7.4s4 DB 9. Convert DB to 1354RM 7.4s4 level 10. Install and customize DB migration tool to get to 1354RM 7.4s5 DB 11. Convert DB to 1354RM 7.4s5 level 12. Install and customize DB migration tool to get to 1354RM 7.4s6 DB 13. Convert DB to 1354RM 7.4s6 level 14. Install and customize DB migration tool to get to 1354RM 7.4s7 DB 15. Convert DB to 1354RM 7.4s7 level 16. Install and customize DB migration tool to get to 1354RM 7.4s9 DB 17. Convert DB to 1354RM 7.4s8 level 18. Convert DB to 1354RM 7.4s9 level 19. Install and customize DB migration tool to get to 1354RM 7.5s0 DB 20. Convert DB to 1354RM 7.5s0 level 21. Check DB conversion
Retrieve Conversion Tools

Copy 1354RM conversion tools into /alcatel/DEPOT directory: a. 1354RM-NRMIG.R7.4.2-7-B1.tar.gz b. 1354RM-NRMIG.R7.4.3-10-B1.tar.gz (cksum & size: 3568575964 85862) (cksum & size: 2508726815 9926040)
ED
RELEASED
Optics
114/157
c. 1354RM-NRMIG_7.4.4.2_B1.tar.gz d. 1354RM-NRMIG_7.4.5.3_B2.tar.gz
(cksum & size: 4229474999 16231) (cksum & size: 3090942239 24909) (cksum & size: 3632164844 32855) (cksum & size: 4164855359 45979) (cksum & size: 260089226 22959)
e. 1354RM-NRMIG_7.4.7.7_B1.tar.gz f. 1354RM-NRMIG_7.4.9.10_B1.tar.gz g. 1354RM-NRMIG_7.5.0.7_B2.tar.gz
Warning: after download completion, it is recommended to check the package file checksum.
Before starting conversion perform the following w/a: ...,sys,root # chmod 777 \ [Enter] /alcatel/8.1PL2/NMA/RM_MIG/7.4.9/rm/migtool/bin/setNetworkInterfaceLevel.pl
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
115/157
Convert database
Hereafter are described steps needed to convert 1354RM database. The paragraphs to be followed to convert your specific database depends on the your source release and your target version. The table hereafter explain you which paragraphs of this appendix must be followed to perform the conversion: Source NR
Target NR = 8.1PL2 Install RM_NRMIG Tool 7.4.4 & Convert database to 7.4s4 Install RM_NRMIG Tool 7.4.5 & Convert database to 7.4s5 Install RM_NRMIG Tool 7.4.4 & Convert database to 7.4s4 Install RM_NRMIG Tool 7.4.5 & Convert database to 7.4s5 Install RM_NRMIG Tool 7.4.4 & Convert database to 7.4s4 Install RM_NRMIG Tool 7.4.5 & Convert database to 7.4s5 Install RM_NRMIG Tool 7.4.6 & Convert database to 7.4s6 Install RM_NRMIG Tool 7.4.7 & Convert database to 7.4s7 Install RM_NRMIG Tool 7.4.6 & Convert database to 7.4s6 Install RM_NRMIG Tool 7.4.7 & Convert database to 7.4s7 Install RM_NRMIG Tool 7.4.6 & Convert database to 7.4s6 Install RM_NRMIG Tool 7.4.7 & Convert database to 7.4s7 Install RM_NRMIG Tool 7.4.6 & Convert database to 7.4s6 Install RM_NRMIG Tool Install RM_NRMIG Tool 7.4.9 & Convert database to 7.4s8 and 7.4s9 Install RM_NRMIG Tool 7.5.0 & Convert database to 7.5s0 Install RM_NRMIG Tool 7.4.9 & Convert database to 7.4s8 and 7.4s9 Install RM_NRMIG Tool 7.5.0 & Convert database to 7.5s0 Install RM_NRMIG Tool 7.4.9 & Convert database to 7.4s8 and 7.4s9 Install RM_NRMIG Tool 7.5.0 & Convert database to 7.5s0 Install RM_NRMIG Tool 7.4.9 & Convert database to 7.4s8 and 7.4s9 Install RM_NRMIG Tool
NR7.1DPL2 NR7.2PL2
Install RM_NRMIG Tool 7.4.2 & Convert database to NR7.3
Install RM_NRMIG Tool 7.4.3 & Convert database to 7.4s3 (NR7.4)
NR7.3
NM
Install RM_NRMIG Tool 7.4.3 & Convert database to 7.4s3
NR7.4
NM
NM
NR8.1
NM
NM
NM
ED
RELEASED
Optics
116/157
7.4.7 & Convert database to 7.4s7

7.5.0 & Convert database to 7.5s0 Install RM_NRMIG Tool 7.4.9 & Convert database to 7.4s8 and 7.4s9 Install RM_NRMIG Tool 7.5.0 & Convert database to 7.5s0
NR8.1PL1
NM
NM
NM
NM
NM = Not meaningful To know which sections you have to follow simply establish you starting NR and look for the correspondent row in the table above. Then follow in sequence the sections mentioned in the green cells according the diagonal of the matrix up your target NR (defined by the column).
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
117/157
Install and Customize NRMIG 7.4.2

Warning! Installing this software you overwrite any other version. If you have to repeat the conversion, you have to execute ...,sys,root # rm -r /alcatel/8.1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time. Before NRMIG 7.4.2 installation execute: ...,sys,root # cd /usr/Systems/1354RM_1-7.4.9/migtool ...,sys,root # ln sf /alcatel/8.1PL2/NMA/RM_NRMIG/7.4/rm/migtool/sql Install the conversion tool. Login into the system as user root and Install the tools executing: ...,sys,root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG.R7.4.2-7-B1.tar.gz interactive=no Some messages like the following will be issued:
WARNING: The link /alcatel/NMC/ points to an others directory /alcatel/<Version>/NMC/ different to the current one /alcatel/8.1PL2/NMC/, skipping it ...
sql
Dont worry about them. Customize the conversion tool: ...,sys,root # /alcatel/8.1PL2/Kernel/script/updateInstance.pl \ [Enter] -sys 1354RM -inst 1-7.4.9 -type NMA comp RM_NRMIG -skipconfig light
Adaptation to keep the log of the conversion

Here described the steps to follow to adapt the RM migration tool in order to keep the log file of the conversion: Login into the system as user root Execute:
...,root # cd /usr/Systems/1354RM_1-7.4.9/migtool/bin/ ...,root # cp p old_db_incremental_migration \ [Enter] old_db_incremental_migration.orig
Edit the file old_db_incremental_migration in order to put a comment before the commands that delete the log files (lines 46, 58). The file should look like:
[] # Mib migration ${MIG_TOOL} $* ${MIG_OPT} >> ${MIG_TOOL_LOG} 2>&1 if [ $? -eq 0 ] then echo "NOTE:\tDatabase schema migration OK\n" # rm -rf ${NXNL_PRD}/migtool/log/err_MIG* else
ED
RELEASED
Optics
118/157
echo "ERROR:\tduring database schema migration (log in ${MIG_TOOL_LOG})\n" exit 1 fi

# Fix sql script ${MIG_TOOL} -x $* -u >> ${MIG_TOOL_LOG} 2>&1 if [ $? -eq 0 ] then echo "NOTE:\tFix database upgrade OK\n" # rm -rf ${NXNL_PRD}/migtool/log/err_MIG* else echo "ERROR:\tduring fix database upgrade (log in ${MIG_TOOL_LOG})\n" exit 1 fi
Save and exit
Convert database to 1354RM 7.3

Follow this section only if required (see section convert database). In this phase the NR7.1D/7.2 (NR7.1D/7.2 PL2) database will be converted to NR7.3 . 1. Open a shell on the target 1354RM machine as snml user 2. Set the environment for the 1354RM Instance ... $ cd /usr/Systems/1354RM_1-7.4.9 ... $ . ./.snmlrc 3. Change to directory: ... $ cd migtool/bin 4. Execute the conversion of the database using the RM_migration tool: ... $ ./old_db_incremental_migration -v f \ [Enter] ../conf/migrationNR71DtoNR73.txt Take care to write correctly migrationNR71DtoNR73.txt otherwise you risk to launch other, similar, scripts corrupting your DB! Wait that the conversion ends (this could take long time for big networks). If all Its OK the following message appears when conversion finishes: NOTE: Fix database upgrade OK
In this case continue with the step 5 If the conversion ends with error: 1. Change to the directory: ... $ cd /usr/Systems/1354RM_1-7.4.9/migtool/log 2. In this directory search file with name: err_MIG_NR71DtoNR73.sql.lst In these files look for ORA- tag with: ... $ grep ORA- err_MIG_NR71DtoNR73.sql.lst | sort -u Check the log for critical errors. Hereafter a list of possible message that you should ignore.
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
119/157
Oracle code ORA-00942 ORA-00955 ORA-01418 ORA-01430 ORA-01442 ORA-02264 ORA-02273 ORA-02275 ORA-02289 ORA-02430 ORA-02443 ORA-04043: table or view does not exist
Meaning
name is already used by an existing object specified index does not exist column being added already exists in table column to be modified to NOT NULL is already NOT NULL name already used by an existing constraint this unique/primary key is referenced by some foreign keys such a referential constraint already exists in the table sequence does not exist cannot enable constraint - no such constraint cannot drop constraint - nonexistent constraint object <object name> does not exist
If there is no errors outside the table you can proceed in the migration, otherwise ask for support. 5. Run the following in order to fix a problem on map visualization: ... $ cd /usr/Systems/1354RM_1-7.4.9/databases/dbsnml/admin/conv ... $ ./migPTRSUBLINK.pl $NXNL_DATABASE After conversion execute, as root: ...,sys,root # cd /usr/Systems/1354RM_1-7.4.9/migtool ...,sys,root # ln sf /alcatel/8.1PL2/NMA/RM_MIG/7.4.7/rm/migtool/sql sql
ED
RELEASED
Optics
120/157
1AA 00014 0004 (9711) A4

Warning! Installing this software you overwrite any other version. If you have to repeat the conversion, you have to execute ...,sys,root # rm -r /alcatel/8.1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time. Install the conversion tool. Login into the system as user root and Install the tools executing: ...,sys,root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG.R7.4.3-10-B1.tar.gz interactive=no Some messages like the following will be issued:
Dont worry about them. Customize the conversion tool: ...,sys,root # /alcatel/8.1PL2/Kernel/script/updateInstance.pl \ [Enter] -sys 1354RM -inst 1-7.4.9 -type NMA comp RM_NRMIG -skipconfig light ...,sys,root # cd /usr/Systems/1354RM_1/NRMIG/sql sys,root # ln sf /alcatel/8.1PL2/NMA/RM_KERNEL/7.4.9/rm/lib/perl/Config Config
Adaptation to keep the log of the conversion

Here are described the steps to follow to adapt the RM_migration tool in order to keep the log files of the conversion: 1. Login into the system as user root 2. Execute:
...,root # cd /usr/Systems/1354RM_1-7.4.9/NRMIG/bin ...,root # cp p RM_migration RM_migration.orig
3. Edit the file RM_migration in order to put a comment before the commands that delete the log files (lines 52, 53, 65, 66). The file should look like:
[] # Mib migration ${MIG_TOOL} $* ${MIG_OPT} if [ $? -eq 0 ] then echo "NOTE:\tDatabase schema migration OK\n" # rm -rf ${NXNL_PRD}/NRMIG/log/MIG_* # rm -rf ${NXNL_PRD}/NRMIG/log/autoalarmclear.* else echo "ERROR:\tduring database schema migration (log in ${MIG_TOOL_LOG})\n" exit 1 fi
1AA 00014 0004 (9711) A4
# Fix sql script
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
121/157
4. Save and exit
Convert database to 1354RM7.4s3

Follow this section only if required (see section convert database). In this phase the NR7.3 database will be converted to NR 7.4. 1. Open a shell on the target 1354RM machine as snml user 2. Set the environment for the 1354RM Instance ... $ cd /usr/Systems/1354RM_1-7.4.9 ... $ . ./.snmlrc 3. Check that /usr/Systems/1354RM_1-7.4.9/NRMIG/log has the write access right for alcatel user with: ... $ ll d /usr/Systems/1354RM_1-7.4.9/NRMIG/log If not, remove any write protection entering: ... $ su ... $ chmod 777 /usr/Systems/1354RM_1-7.4.9/NRMIG/log ... $ exit 4. Change to the directory: ... $ cd NRMIG/bin 5. Execute ... $ sqlplus $NXNL_DATABASE SQL> select index_name from all_indexes where table_name='PMTRAN' or table_name='PMTP'; If the query returns the following indexes INDEX_PMTRAN_LABEL IDX_PMTP_USERLABEL INDEX_PMTP_PMMEASUREID drop them with the command SQL> drop index <index name>; 6. Execute the conversion of the database using the RM_migration tools. ... $ ./RM_migration -v -f ../conf/migrationNR73toNR74s3.txt
ED
RELEASED
Optics
122/157
1AA 00014 0004 (9711) A4
Take care to write correctly migrationNR73toNR74s3.txt otherwise you risk to launch other, similar, scripts corrupting your DB!
${MIG_TOOL} -x -t ${MIG_TOOL_LOG} -u if [ $? -eq 0 ] then echo "NOTE:\tFix database upgrade OK\n" # rm -rf ${NXNL_PRD}/NRMIG/log/MIG_* # rm -rf ${NXNL_PRD}/NRMIG/log/autoalarmclear.* else echo "ERROR:\tduring fix database upgrade (log in ${MIG_TOOL_LOG})\n" exit 1 fi
Wait that the conversion ends (this could take long time for big networks). If everything works fine, the following message appears when conversion finishes:
NOTE:
Fix database upgrade OK
In this case continue with the next command, otherwise proceed with this : 1. Change to the directory: ... $ cd /usr/Systems/1354RM_1-7.4.9/NRMIG/log 2. In this directory search file with name: MIG_ORACLE_NR73toNR74s3 In these files look for ORA- tag with: ... $ grep ORA- MIG_ORACLE_NR73toNR74s3.err | sort -u Check the log for critical errors. Table 16 shows the list of message that you should ignore. 7. Always execute: ... $ sqlplus $NXNL_DATABASE SQL> spool /usr/Systems/1354RM_1-7.4.9/NRMIG/log/postMigration743.log SQL> @/usr/Systems/1354RM_1-7.4.9/NRMIG/sql/postMigration743.sql SQL> commit; SQL> quit Check the log for critical errors. Table 16 shows the list of message that you should ignore.
Create Payload MAP tables entires

Create the payload Map tables executing the following command: 1. Open a shell on the target 1354RM machine as snml user with graphical interface: ... $ cd /usr/Systems/1354RM_1-7.4.9 ... $ . ./.snmlrc ... $ cd NRMIG/bin ... $ export SHLIB_PATH=/usr/Systems/1354RM_1-7.4.9/NRMIG/lib:$SHLIB_PATH ... $ export NXNL_NE_FEATURES_DIR=/usr/Systems/1354RM_1-7.4.9/NRMIG/conf ... $ ./paymapMig -allMib -log \ [Enter] /usr/Systems/1354RM_1-7.4.9/NRMIG/log/payMapBuilder.log 2. Check logs file payMapBuilder.log to see if errors have been detached entering: ... $ grep i e error e warning \ [Enter] /usr/Systems/1354RM_1-7.4.9/NRMIG/log/payMapBuilder.log If present ignore messages similar to these: aFILT 00002 WARNING in file GenericFilter.cc at line 567: Filter size (50) exceeded: reallocating Mib 00002 ERROR in file MibDescriptor.cc at line 84: MIB array attributes is NULL ! 3. Execute the script checkAZtopId.sql and ensure that no rows are selected from the Database: ... $ sqlplus $NXNL_DATABASE \ [Enter] @/usr/Systems/1354RM_1-7.4.9/NRMIG/sql/checkAZtopId.sql
1AA 00014 0004 (9711) A4
In case of rows presence please contact TEC Italy.
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
123/157
Warning! Installing this software you overwrite any other version. If you have to repeat the conversion, you have to execute ...,sys,root # rm -r /alcatel/8.1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time. Install the conversion tool. Login into the system as user root and Install the tools executing: ...,sys,root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG_7.4.4.2_B1.tar.gz interactive=no Some messages like the following will be issued:
Dont worry about them. Customize the conversion tool: ...,sys,root # /alcatel/8.1PL2/Kernel/script/updateInstance.pl \ [Enter] -sys 1354RM -inst 1-7.4.9 -type NMA comp RM_NRMIG -skipconfig light Edit the file /usr/Systems/1354RM_1/NRMIG/bin/RM_migration putting a comment before the line 8: . /usr/snml/.snmlrc ...,sys,root # cd /usr/Systems/1354RM_1/NRMIG/sql sys,root # ln sf /alcatel/8.1PL2/NMA/RM_KERNEL/7.4.9/rm/lib/perl/Config Config (Re)execute the adaptation to keep the log of the conversion at lines 46, 47, 59, 60 (see previous paragraph).

Follow this section only if required (see section convert database). In this phase the RM7.4s3 (NR7.4) database will be converted to RM 7.4s4. 1. Open a shell on the target 1354RM machine as snml user 2. Set the environment for the 1354RM Instance ... $ cd /usr/Systems/1354RM_1-7.4.9 ... $ . ./.snmlrc 3. Check the /usr/Systems/1354RM_1-7.4.9/NRMIG/log has the write access right for alcatel user with: ... $ ll d /usr/Systems/1354RM_1-7.4.9/NRMIG/log If not, remove any write protection entering: ... $ su ... $ chmod 777 /usr/Systems/1354RM_1-7.4.9/NRMIG/log ... $ exit
ED
RELEASED
Optics
124/157
1AA 00014 0004 (9711) A4
4. Change to the directory: ... $ cd NRMIG/bin

5. Execute the conversion of the database using the RM_migration tools: ... $ export SHLIB_PATH=/usr/Systems/1354RM_1-7.4.9/NRMIG/lib:$SHLIB_PATH ... $ ./RM_migration -v -f ../conf/migrationNR74s3toNR74s4.txt Take care to write correctly migrationNR74s3toNR74s4.txt otherwise you risk to launch other, similar, scripts corrupting your DB! Wait that the conversion ends (this could take long time for big networks). If everything works fine, the following message appears when conversion finishes: NOTE: Fix database upgrade OK
In this case continue with the next section, otherwise proceed with this : Change to the directory: ... $ cd /usr/Systems/1354RM_1-7.4.9/NRMIG/log In this directory search file with name: MIG_ORACLE_NR74s3toNR74s4 In these files look for ORA- tag with: ... $ grep ORA- MIG_ORACLE_NR74s3toNR74s4.err | sort -u Check the log for critical errors. Table 16 shows the list of message that you should ignore.
Dont worry about them. Customize the conversion tool: ...,sys,root # /alcatel/8.1PL2/Kernel/script/updateInstance.pl \ [Enter] -sys 1354RM -inst 1-7.4.9 -type NMA -comp RM_NRMIG -skipconfig light ...,sys,root # cd /usr/Systems/1354RM_1/NRMIG/sql sys,root # ln sf /alcatel/8.1PL2/NMA/RM_KERNEL/7.4.9/rm/lib/perl/Config Config (Re)execute the adaptation to keep the log of the conversion at lines 52, 53, 67, 68 (see previous paragraph).
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
125/157

Follow this section only if required (see section convert database). In this phase the RM7.4s4 database will be converted to RM 7.4s5 (NR8.1). Open a shell on the target 1354RM machine as snml user Set the environment for the 1354RM Instance ... $ cd /usr/Systems/1354RM_1-7.4.9 ... $ . ./.snmlrc Check the /usr/Systems/1354RM_1-7.4.9/NRMIG/log has the write access right for alcatel user with: ... $ ll d /usr/Systems/1354RM_1-7.4.9/NRMIG/log If not, remove any write protection entering: ... $ su ... $ chmod 777 /usr/Systems/1354RM_1-7.4.9/NRMIG/log ... $ exit Change to the directory: ... $ cd NRMIG/bin Execute the conversion of the database using the RM_migration tools: ... $ ./RM_migration -v -f ../conf/migrationNR74s4toNR74s5.txt Take care to write correctly migrationNR74s4toNR74s5.txt otherwise you risk to launch other, similar, scripts corrupting your DB! Wait that the conversion ends (this could take long time for big networks). If everything works fine, the following message appears when conversion finishes: NOTE: Fix database upgrade OK
Warning! Installing this software you overwrite any other version. If you have to repeat the conversion, you have to execute ...,sys,root # rm -r /alcatel/8.1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time.
ED
RELEASED
Optics
126/157
Install the conversion tool. Login into the system as user root and Install the tools executing: ...,sys,root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG_7.4.6.5_B1.tar.gz interactive=no
Some messages like the following will be issued:

Dont worry about them. Customize the conversion tool: ...,sys,root # /alcatel/8.1PL2/Kernel/script/updateInstance.pl \ [Enter] -sys 1354RM -inst 1-7.4.9 -type NMA -comp RM_NRMIG -skipconfig light (Re)execute the adaptation to keep the log of the conversion at lines 62, 63, 77, 78 (see previous paragraph).

Follow this section only if required (see section convert database). In this phase the RM7.4s5 database will be converted to RM 7.4s6 (NR8.1PL1). 4. Open a shell on the target 1354RM machine as snml user 5. Set the environment for the 1354RM Instance ... $ cd /usr/Systems/1354RM_1-7.4.9 ... $ . ./.snmlrc 6. Check the /usr/Systems/1354RM_1-7.4.9/NRMIG/log has the write access right for alcatel user with: ... $ ll d /usr/Systems/1354RM_1-7.4.9/NRMIG/log If not, remove any write protection entering: ... $ su ... $ chmod 777 /usr/Systems/1354RM_1-7.4.9/NRMIG/log ... $ exit 7. Change to the directory: ... $ cd NRMIG/bin 8. Execute the conversion of the database using the RM_migration tools: ... $ ./RM_migration -v -f ../conf/migrationNR74s5toNR74s6.txt Take care to write correctly migrationNR74s5toNR74s6.txt otherwise you risk to launch other, similar, scripts corrupting your DB! Wait that the conversion ends (this could take long time for big networks). If everything works fine, the following message appears when conversion finishes: NOTE: Fix database upgrade OK
In this case continue with the next section, otherwise proceed with this : Change to the directory: ... $ cd /usr/Systems/1354RM_1-7.4.9/NRMIG/log
1AA 00014 0004 (9711) A4
In this directory search file with name: MIG_ORACLE_NR74s5toNR74s6
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
127/157
In these files look for ORA- tag with:

... $ grep ORA- MIG_ORACLE_NR74s5toNR74s6.err | sort -u Check the log for critical errors. Table 16 shows the list of message that you should ignore.
Dont worry about them. Customize the conversion tool: ...,sys,root # /alcatel/8.1PL2/Kernel/script/updateInstance.pl \ [Enter] -sys 1354RM -inst 1-7.4.9 -type NMA -comp RM_NRMIG -skipconfig light (Re)execute the adaptation to keep the log of the conversion at lines 62, 63, 77, 78 (see previous paragraph).

Follow this section only if required (see section convert database). In this phase the RM7.4s6 database will be converted to RM 7.4s7 (NR8.1PL1). a. Open a shell on the target 1354RM machine as snml user b. Set the environment for the 1354RM Instance ... $ cd /usr/Systems/1354RM_1-7.4.9 ... $ . ./.snmlrc c. Check the /usr/Systems/1354RM_1-7.4.9/NRMIG/log has the write access right for alcatel user with:
... $ ll d /usr/Systems/1354RM_1-7.4.9/NRMIG/log If not, remove any write protection entering: ... $ su ... $ chmod 777 /usr/Systems/1354RM_1-7.4.9/NRMIG/log ... $ exit d. Change to the directory:
ED
RELEASED
Optics
128/157
... $ cd NRMIG/bin e. Execute the conversion of the database using the RM_migration tools:
... $ ./RM_migration -v -f ../conf/migrationNR74s6toNR74s7.txt Take care to write correctly migrationNR74s6toNR74s7.txt otherwise you risk to launch other, similar, scripts corrupting your DB! If you get the following (or similar) error: Migration hist. file: ../conf/migrationNR74s6toNR74s7.txt doesn't exist at /usr/Systems/1354RM_17.4.7/NRMIG/bin/RM_migration.pl line 499. ERROR: during database schema migration ! try to execute: ... $ cd .. ... $ cd bin and repeat the command. Wait that the conversion ends (this could take long time for big networks). If everything works fine, the following message appears when conversion finishes: NOTE: Fix database upgrade OK

Warning! Installing this software you overwrite any other version. If you have to repeat the conversion, you have to execute ...,sys,root # rm -r /alcatel/8.1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time. Login into the system as user root Install the tools executing:
...,sys,root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG_7.4.9.10_B1.tar.gz interactive=no Some messages like the following will be issued:
Dont worry about them.

1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
129/157
Customize the conversion tool:

...,sys,root # /alcatel/8.1PL2/Kernel/script/updateInstance.pl \ [Enter] -sys 1354RM inst 1-7.4.9 -type NMA -comp RM_NRMIG -skipconfig light Execute adaptation to keep the log of the conversion:
...,root # cd /usr/Systems/1354RM_1-7.4.9/NRMIG/bin ...,root # cp p RM_migration RM_migration.orig ...,root # vi RM_migration
put a comment before the commands that delete the log files (lines 59, 60, 74, 75)

In this phase the RM7.4s8 database will be converted to RM 7.4s9 (NR8.1PL2). Login as snml user Set the environment for the 1354RM Instance ... $ cd /usr/Systems/1354RM_1-7.4.9 ... $ . ./.snmlrc Check the /usr/Systems/1354RM_1-7.4.9/NRMIG/log has the write access right for alcatel user with: ... $ ll d /usr/Systems/1354RM_1-7.4.9/NRMIG/log If not, remove any write protection entering: ... $ su ... $ chmod 777 /usr/Systems/1354RM_1-7.4.9/NRMIG/log ... $ exit Only if migrating from NR8.1PL1 from 1354RM 7.4.7.5 P17 or lower execute: ... $ cd NRMIG/bin ... $ ./RM_migration v -f ../conf/migration_SKIPPED_747_p18.txt ... $ cd ../.. Execute: ... ... ... ... ... $ $ $ $ $ cd ORACLE/databases/dbnml/etc start_db cd /usr/Systems/1354RM_1-7.4.9/NRMIG/sql ./setSch747_814.pl cd ../bin
Execute the conversion of the database using the RM_migration tools: ... $ ./RM_migration -v -f ../conf/migrationNR74s7toNR74s8.txt ... $ ./RM_migration -v -f ../conf/migrationNR74s8toNR74s9.txt Take care to write correctly migrationNR74s7toNR74s8.txt and migrationNR74s8toNR74s9.txt otherwise you risk to launch other, similar, scripts corrupting your DB! If you get the following (or similar) error: Migration hist. file: ../conf/migrationNR74s7toNR74s8.txt doesn't exist at /usr/Systems/1354RM_17.4.9/NRMIG/bin/RM_migration.pl line 499. ERROR: during database schema migration ! try to execute:
ED
RELEASED
Optics
130/157
... $ cd .. ... $ cd bin

and repeat the command. Wait that the conversion ends (this could take long time for big networks). If everything works fine, the following message appears when conversion finishes: NOTE: Fix database upgrade OK
In this case continue with the next section, otherwise proceed with this : Change to the directory: ... $ cd /usr/Systems/1354RM_1-7.4.9/NRMIG/log In this directory search files with name: MIG_ORACLE_NR74s7toNR74s8 and MIG_ORACLE_NR74s8toNR74s9 In these files look for ORA- tag with: ... $ grep ORA- MIG_ORACLE_NR74s7toNR74s8.err | sort u ... $ grep ORA- MIG_ORACLE_NR74s8toNR74s9.err | sort -u Check the log for critical errors. Table 16 shows the list of message that you should ignore.

Warning! Installing this software you overwrite any other version. If you have to repeat the conversion, you have to execute ...,sys,root # rm -r /alcatel/8.1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time. Login into the system as user root Install the tools executing: ...,sys,root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG_7.5.0.7_B2.tar.gz interactive=no Some messages like the following will be issued:
Dont worry about them. Customize the conversion tool: ...,sys,root # /alcatel/8.1PL2/Kernel/script/updateInstance.pl \ [Enter] -sys 1354RM inst 1-7.4.9 -type NMA -comp RM_NRMIG -skipconfig light

In this phase the RM7.4s9 database will be converted to RM 7.5s0 (NR8.1PL2/MD4+). Login as snml user
1AA 00014 0004 (9711) A4
Set the environment for the 1354RM Instance
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
131/157
... $ cd /usr/Systems/1354RM_1-7.4.9 ... $ . ./.snmlrc Check the /usr/Systems/1354RM_1-7.4.9/NRMIG/log has the write access right for alcatel user with: ... $ ll d /usr/Systems/1354RM_1-7.4.9/NRMIG/log If not, remove any write protection entering: ... $ su ... $ chmod 777 /usr/Systems/1354RM_1-7.4.9/NRMIG/log ... $ exit Change to the directory: ... $ cd NRMIG/bin Execute the conversion of the database using the RM_migration tools: ... $ ./RM_migration -v -f ../conf/migrationNR74s9toNR75s0.txt Take care to write correctly migrationNR74s9toNR75s0.txt otherwise you risk to launch other, similar, scripts corrupting your DB! Wait that the conversion ends (this could take long time for big networks). If everything works fine, the following message appears when conversion finishes: NOTE: Fix database upgrade OK
PMDS 2.0 DB Upgrade

Always follow this section. In this phase some database old tables will be dropped. Open a shell on the target 1354RM machine as snml user Set the environment for the 1354RM Instance ... ... ... ... $ $ $ $ cd /usr/Systems/1354RM_1-7.4.9 . ./.snmlrc cd ORACLE/databases/dbnml/etc start_db
Mise en forme : Puces et numros Mise en forme : Puces et numros
Change to the directory: ... $ cd /usr/Systems/1354RM_1-7.4.9/PMDS_DB/script/ Execute the script:

1AA 00014 0004 (9711) A4
... $ ./PMDS_2.0_NML_DB_UPGRADE.sh logpath \ [Enter] /usr/Systems/1354RM_1-7.4.9/PMDS_DB/trace/ -v
ED
RELEASED
Optics
132/157
Change to the directory: ... $ cd /usr/Systems/1354RM_1-7.4.9/PMDS_DB/trace/

Look for ORA- tag with: ... $ grep ORA- drop_pmds_useless_obj.log | sort -u Check the log for critical errors. Table 16 shows the list of message that you should ignore. Its recommended to check converted DB structure following Check DB conversion paragraph.
Check DB conversion
Hereafter are described the steps to follow to compare the current database schema with the expected one. Login on the 1354RM target machine as user snml ... ... ... SQL SQL ... ... $ $ $ > > $ $ cd /usr/Systems/1354RM_1-7.4.9 . ./.snmlrc sqlplus $NXNL_DATABASE purge recyclebin; quit mkdir /alcatel/DEPOT/NR81PL2_RM_DB chmod 777 /alcatel/DEPOT/NR81PL2_RM_DB
Get a snapshot of the database: ... $ cd /usr/Systems/1354RM_1-7.4.9/ORACLE/script/ ... $ ./MIB_Contents get /alcatel/DEPOT/NR81PL2_RM_DB Compare the current DB schema with the expected one: ... $ ./MIB_Contents compare /alcatel/DEPOT/NR81PL2_RM_DB_Ref \ [Enter] /alcatel/DEPOT/NR81PL2_RM_DB > \ [Enter] /alcatel/DEPOT/NR81PL2_RM_DB_Diff.log Check the log file just created: ... $ vi /alcatel/DEPOT/NR81PL2_RM_DB_Diff.log If you find any significant difference please contact TEC Italy before continue with the conversion.
Neglect the following differences (or similar): "<" indicates NR8.1PL2 database ">" indicates migrated database
COMPARING COLUMN DATA < NLSSTR < NLSSTR < NLSSTR LANGID STRINGID TRANSLATION VARCHAR2 30 NUMBER 22 VARCHAR2 100
1AA 00014 0004 (9711) A4
> COUREP_BAK > COUREP_BAK > COUREP_BAK > COUREP_BAK > COUREP_BAK > COUREP_BAK > COUREP_BAK
CSVREPOSITORY NUMBER 22 PMCOUNTREPID NUMBER 22 PMDOMID NUMBER 22 PMREPDESTNAME VARCHAR2 80 PMREPORTDESTTYPE NUMBER 22 PMREPORTFORMAT NUMBER 22 PMREPORTRESOL NUMBER 22
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
133/157
> PMREOP_TEST > PMREOP_TEST > PMREOP_TEST > PMREOP_TEST > PMREOP_TEST > PMREOP_TEST > PMREOP_TEST
PMENDPERIOD PMFROMSEC PMMEASUREID PMREPORTID PMREPORTOPID PMREPORTTYPE PMTOSEC
NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER NUMBER
22 22 22 22 22 22 22
COMPARING DEFAULT DATA < NLSSTR < NLSSTR < NLSSTR < CONNEC --> CONNEC LANGID STRINGID TRANSLATION ALRENABLINGRULE ALRENABLINGRULE CSVREPOSITORY PMCOUNTREPID PMDOMID PMREPDESTNAME PMREPORTDESTTYPE PMREPORTFORMAT PMREPORTRESOL PMREPORTWINDOW SECURITYLABEL USERLABEL 1 0
> COUREP_BAK > COUREP_BAK > COUREP_BAK > COUREP_BAK > COUREP_BAK > COUREP_BAK > COUREP_BAK > COUREP_BAK > COUREP_BAK > COUREP_BAK < CTRPLANE --> CTRPLANE < PATH --> PATH < PATH --> PATH < PMTCA --> PMTCA < PMTCA --> PMTCA < PRT --> PRT
NATIVENAME NATIVENAME ''
ACTIVECONCLEVEL ACTIVECONCLEVEL CONCATENATIONLEVEL CONCATENATIONLEVEL FESESLOW FESESLOW SESLOW SESLOW NULL ''
1AA 00014 0004 (9711) A4
NULL
NULL
NULL
ACCCONTROLDOMAIN ACCCONTROLDOMAIN
ED
RELEASED
Optics
134/157
> COUREP_BAK PMREPORTWINDOW NUMBER > COUREP_BAK SECURITYLABEL NUMBER > COUREP_BAK USERLABEL VARCHAR2
22 22 24
< PRT --> PRT < PRT --> PRT < PRT --> PRT < PRT --> PRT
CONNECTIVITYPOINTER CONNECTIVITYPOINTER EXTERNALVLANID EXTERNALVLANID EXTVLANPRIORITY EXTVLANPRIORITY
''
NULL
NULL '4080/16' 4080
LCASMAXRSACKTIMEOUT LCASMAXRSACKTIMEOUT
COMPARING CONSTRAINT DATA > COUREP_BAK SYS_C005578 C USERLABEL IS NOT NULL ENABLED > COUREP_BAK SYS_C005579 C PMREPORTDESTTYPE IS NOT NULL ENABLED > COUREP_BAK SYS_C005580 C PMREPDESTNAME IS NOT NULL ENABLED > COUREP_BAK SYS_C005581 C PMREPORTWINDOW IS NOT NULL ENABLED > COUREP_BAK SYS_C005582 C PMREPORTFORMAT IS NOT NULL ENABLED > COUREP_BAK SYS_C005583 C PMDOMID IS NOT NULL ENABLED > COUREP_BAK SYS_C005584 C SECURITYLABEL IS NOT NULL ENABLED < NLSSTR NN_NLSSTR_LANGID C LANGID IS NOT NULL ENABLED < NLSSTR NN_NLSSTR_STRINGID C STRINGID IS NOT NULL ENABLED < NLSSTR NN_NLSSTR_TRANSLATION C TRANSLATION IS NOT NULL ENABLED < PMBOPE SYS_C005166 C PMBOOKPERIODID IS NOT NULL ENABLED < PMBOPE SYS_C005167 C PMFROMDATE IS NOT NULL ENABLED < PMBOPE SYS_C005168 C PMTODATE IS NOT NULL ENABLED < PMBOPE SYS_C005169 P ENABLED --> PMBOPE SYS_C007712 C PMBOOKPERIODID IS NOT NULL ENABLED > PMBOPE SYS_C007713 C PMFROMDATE IS NOT NULL ENABLED > PMBOPE SYS_C007714 C PMTODATE IS NOT NULL ENABLED > PMBOPE SYS_C007715 P ENABLED < PMBOPESPE SYS_C005170 C PMBOOKPERIODID IS NOT NULL ENABLED < PMBOPESPE SYS_C005171 C ENTITYTYPE IS NOT NULL ENABLED < PMBOPESPE SYS_C005172 C ENTITYID IS NOT NULL ENABLED < PMBOPESPE SYS_C005173 P ENABLED --> PMBOPESPE SYS_C007716 C PMBOOKPERIODID IS NOT NULL ENABLED > PMBOPESPE SYS_C007717 C ENTITYTYPE IS NOT NULL ENABLED > PMBOPESPE SYS_C007718 C ENTITYID IS NOT NULL ENABLED > PMBOPESPE SYS_C007719 P ENABLED > PMREOP_TEST SYS_C006484 C PMMEASUREID IS NOT NULL ENABLED > PMREOP_TEST SYS_C006485 C PMREPORTID IS NOT NULL ENABLED > PMREOP_TEST SYS_C006486 C PMREPORTTYPE IS NOT NULL ENABLED > PMREOP_TEST SYS_C006487 C PMENDPERIOD IS NOT NULL ENABLED
1AA 00014 0004 (9711) A4
< PMTP NN_PMTP_PMAVCOID C PMAVCOID IS NOT NULL ENABLED
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
135/157
< ROUTLISBL FK_ROUTLISBL_ROUTLINKID R ENABLED < ROUTLISBL FK_ROUTLISBL_SUBLINKID R ENABLED

COMPARING INDEX DATA < PMBOPE SYS_C005169 < PMBOPESPE SYS_C005173 < PMBOPESPE SYS_C005173 < PMBOPESPE SYS_C005173 --> PMBOPE SYS_C007715 > PMBOPESPE SYS_C007719 > PMBOPESPE SYS_C007719 > PMBOPESPE SYS_C007719 UNIQUE PMBOOKPERIODID UNIQUE PMBOOKPERIODID UNIQUE ENTITYID UNIQUE ENTITYTYPE UNIQUE PMBOOKPERIODID UNIQUE PMBOOKPERIODID UNIQUE ENTITYID UNIQUE ENTITYTYPE 1 3 2 22 ASC 1 22 ASC 22 ASC 22 ASC
22 ASC 1 22 ASC 3 22 ASC 2 22 ASC
COMPARING SEQUENCE DATA > SCHEDULER_SEQUENCE 1 1.0000E+27 1N N 20
Warning! Sometimes the compare tool detects false differences.
So neglect: 1) identical lines like these: < B_EVCTC > B_EVCTC < B_EVCTERM > B_EVCTERM IN_BEVCTC_EVCFRAGTCID IN_BEVCTC_EVCFRAGTCID NONUNIQUE NONUNIQUE TCID TCID PORTID PORTID 2 2 2 2 22 ASC 22 ASC 22 ASC 22 ASC
IN_BEVCTERM_EVCTERMPORTID IN_BEVCTERM_EVCTERMPORTID
NONUNIQUE NONUNIQUE
2) meaningless lines like these: < < --> OR propClassOid = 14 > OR propClassOid = 15 123,124c123,124 < < --> OR updClassOid = 14 > OR updClassOid = 15 125a126 OR UPDCLASSOID = 14 OR UP OR PROPCLASSOID = 14 OR
ED
RELEASED
Optics
136/157
1AA 00014 0004 (9711) A4
<
<
>
---
499a500
ED OR DISJCLASS = 135
497,498c498
> OR disjClass = 135
Optics
RELEASED
8DG 31466 AAAATCZZA
137/157
15 APPENDIX H: 1354BM-ETH DATA CONVERSION Overview

This appendix describes the steps to be performed in order to convert the data from the source to the target version. Please use this appendix only when referenced to. Warning! Conversion scripts can be launched only once! If you have to relaunch them, it is mandatory to re-import and re-convert data from the beginning.
Retrieve Conversion Tool

Copy 1354BMETH conversion tools into /alcatel/DEPOT directory: 1354BMETH_MIBCONV_8.1.5.22.tar.gz (cksum & size: 3771959693 58713)
Warning: after download completion, it is recommended to check the package file checksum.
Install and Customize MIBCONV 8.1.5
Install the conversion tool. Login into the system as user root and Install the tools executing: ...,sys,root # /alcatel/INSTALLER/Install 1354BMETH <hostname> \ [Enter] file=/alcatel/DEPOT/1354BMETH_MIBCONV_8.1.5.22.tar.gz interactive=no Some messages like the following will be issued:
Dont worry about them. Customize the conversion tool: ...,sys,root # /alcatel/8.1PL2/Kernel/script/updateInstance.pl \ [Enter] -sys 1354BMETH -inst 1-8.1.5 -type NMA -comp BM_ETH_MIBCONV skipconfig light
Convert database
To perform the DB conversion the following sections must be followed in sequence: Login into the system as user bmml 1. Startup 1354BMETH database: ... $ . /usr/Systems/1354BMETH_1-8.1.5/.bmmlrc ... $ /usr/Systems/1354BMETH_1-8.1.5/ORACLE/databases/dbnml/etc/start_db ... $ cd /usr/Systems/1354BMETH_1-8.1.5/databases/dbbmml/admin/create 2. Connect to the ORACLE database and run the migration script to convert database (choose the first script according to BMETH starting version; for example, if you have BM-ETH 7.3.0.5P2RP4
ED
RELEASED
Optics
138/157
choose as first script MigrateFrom7305P2RP1To7305P2RP6.sql): If upgrading from NR7.1DPL2 execute:

... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFrom711P14RP2To7305P1RP1.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFrom7305P1RP1To7305P2RP1.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFrom7305P2RP1To7305P2RP6.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFrom7305P2RP6To8103.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8103ToDB8104.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8104ToDB8135.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8135ToDB8141.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8141ToDB8157.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8157ToDB8158.sql If upgrading from NR7.4 execute: ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFrom7305P2RP6To8103.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8103ToDB8104.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8104ToDB8135.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8135ToDB8141.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8141ToDB8157.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8157ToDB8158.sql If upgrading from NR8.1 execute: ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8104ToDB8135.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8135ToDB8141.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8141ToDB8157.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8157ToDB8158.sql If upgrading from NR8.1PL1 execute: ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8141ToDB8157.sql ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8157ToDB8158.sql Verify that the migration of the data has been correctly executed checking the files having the extension .lst in the directory: ... $ grep -i error *.lst Check the log for critical errors. Hereafter a list of possible message that you should ignore.
Oracle code ORA-00942

1AA 00014 0004 (9711) A4
Meaning table or view does not exist
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
139/157
ORA-00955 ORA-01418 ORA-01430 ORA-01442 ORA-02264 ORA-02273 ORA-02275 ORA-02289 ORA-02430 ORA-02443 ORA-04043:
name is already used by an existing object specified index does not exist column being added already exists in table column to be modified to NOT NULL is already NOT NULL name already used by an existing constraint this unique/primary key is referenced by some foreign keys such a referential constraint already exists in the table sequence does not exist cannot enable constraint - no such constraint cannot drop constraint - nonexistent constraint object does not exist
Table 34. Oracle Not Relevant Errors In Database Conversion If there is no errors outside the table you can proceed in the migration, otherwise ask for support 3. Execute the script: $ ./renameUnamedConstraints.sh 1> ./renameUnamedConstraints.log 2>&1 Its recommended to check converted DB structure following Check DB conversion paragraph.
Check DB conversion
Hereafter are described the steps to follow to compare the current database schema with the expected one. Login on the 1354BMETH target machine as user bmml ... ... ... SQL SQL ... ... $ $ $ > > $ $ cd /usr/Systems/1354BMETH_1-8.1.5 . ./.bmmlrc sqlplus $NXNL_DATABASE purge recyclebin; quit mkdir /alcatel/DEPOT/NR81PL2_BMETH_DB chmod 777 /alcatel/DEPOT/NR81PL2_BMETH_DB
Get a snapshot of the database:

1AA 00014 0004 (9711) A4
... $ cd /usr/Systems/1354BMETH_1-8.1.5/ORACLE/script/ ... $ ./MIB_Contents get /alcatel/DEPOT/NR81PL2_BMETH_DB
ED
RELEASED
Optics
140/157
Compare the current DB schema with the expected one: ... $ ./MIB_Contents compare /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref \ [Enter] /alcatel/DEPOT/NR81PL2_BMETH_DB > \ [Enter] /alcatel/DEPOT/NR81PL2_BMETH_DB_Diff.log Check the log file just created: ... $ vi /alcatel/DEPOT/NR81PL2_BMETH_DB_Diff.log If you find any significant difference please contact TEC Italy before continue with the conversion.
Neglect the following differences (or similar): "<" indicates NR8.1PL2 database ">" indicates migrated database
COMPARING CONSTRAINT DATA < B_PBTERM FK_BPBTERM_ETHSWITCHID R ENABLED
Warning! Sometimes the compare tool detects false differences.
They are due to input files bad format. So neglect: 1) identical lines like these: < B_EVCTC > B_EVCTC < B_EVCTERM > B_EVCTERM IN_BEVCTC_EVCFRAGTCID IN_BEVCTC_EVCFRAGTCID NONUNIQUE NONUNIQUE TCID TCID PORTID PORTID 2 2 2 2 22 ASC 22 ASC 22 ASC 22 ASC
IN_BEVCTERM_EVCTERMPORTID IN_BEVCTERM_EVCTERMPORTID
NONUNIQUE NONUNIQUE
2) meaningless lines like these: < < --> OR propClassOid = 14 > OR propClassOid = 15 123,124c123,124 < < --> OR updClassOid = 14 > OR updClassOid = 15 125a126
1AA 00014 0004 (9711) A4
OR PROPCLASSOID = 14 OR
OR UPDCLASSOID = 14 OR UP
>
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
141/157
>
<
<
---
ED 499a500 497,498c498 > OR disjClass = 135 OR DISJCLASS = 135

1AA 00014 0004 (9711) A4
Optics
RELEASED
142/157
16 APPENDIX I: 1354RM SEC (SECURITY) DATABASE ADAPTATION

Adapt the 1354RM SEC database executing: 1. Verify you are still logged in as user alcatel in graphical mode 2. Open the SEC graphical interface executing ... $ cd /usr/Systems/1354RM_1-7.4.9/SEC ... $ script/secusm The SEC graphical interface will be opened. 3. Expand from the list on the left side of the SEC graphical interface the Operator tag (click with the mouse selection button (MB1) on the Operator branch in the window left side). The windows will appears as following
Figure 16 - Operator in SEC graphical interface
4. For each operator belonging to the Operator list (shown in the red circle): 1. Expand it (click with the mouse selection button (MB1) on the inscription of the Operator on the window left side) 2. On the right side of the window, select the profile with the same name of the operator (click with the mouse selection button (MB1) on the inscription of the operator) 3. Clicking the quick choice button of the mouse (MB3), select from the Action List Remove <user> from the SEC database as appears in the figure below
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
143/157
Figure 17 - Remove of the profile with the same name of Operator
4. Answer yes to the question appearing in the message box 5. After the deletion of all the profiles with the same name of the Operator, click (with the mouse selection button (MB1)) on Operator profile tag in the left side of the window in order to verify that all the profile has been really removed. The window will appears as following
Figure 18 - Operator profile list 1AA 00014 0004 (9711) A4
6. Exit from SEC graphical interface selecting Application -> Exit and answering yes to the question in the message box.
ED
RELEASED
Optics
144/157
7. Logout from NMS graphical interface 8. Login as user root.

9. Remove (if they exist) some SEC configuration files executing: ...,sys,root ...,sys,root ...,sys,root ...,sys,root ...,sys,root ...,sys,root # cd # rm # rm # cd # rm # rm /usr/Systems/1354RM_1-7.4.9/SEC repository/.users.defined repository/.initiators.defined /usr/Systems/1354RM_1-7.4.9 maintenance/tmp/.users.defined maintenance/tmp/.initiators.defined
10. Check the files in /usr/Systems/1354RM_1-7.4.9/env directory executing: ...,sys,root # cd /usr/Systems/1354RM_1-7.4.9/env ...,sys,root # ls -l The list of the files looks like: -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx 1 snml 1 snml 1 snml dba dba dba 3628 Jul 451 Jul 3999 Jul 7 15:00 acnsd_env 7 14:57 prd_env 7 15:00 smf_env
Verify that only the three files acnsd_env, prd_env, and smf_env are here present. If there are some other files (e.g.: acnsd_env.old), delete it.
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
145/157
17 APPENDIX J: CUSTOM WARNING AND ERROR

This appendix shows the useless error and warning message types issued by customize script. Ignore these messages when are issued in the customize log window. NMS 1353NM Useless Error and Warning Messages to be ignored. NOTE: Importing EmlUsmSH5MW_SECPLUG.import definitions ...
Importing from file:/usr/Systems/1353NM_1/SEC/repository/secimimports/EmlUsmSH5MW_SECPLUG.import ERROR: , line #494: Name Already Used. ERROR: , line #499: Name Already Used. ERROR: , line #577: Name Already Used. ERROR: , line #582: Name Already Used. ERROR: , line #1069: Name Already Used. ERROR: , line #1074: Name Already Used. ERROR: , line #1578: Name Already Used. ERROR: , line #1583: Name Already Used. Import problem: Name Already Used. ... Importing from file:/usr/Systems/1353NM_1/SEC/repository/secimimports/EmlUsmSH5WDM_SECPLUG.import ERROR:, line #284: Name Already Used. ERROR: , line #289: Name Already Used. ERROR: , line #421: Name Already Used. ERROR: , line #426: Name Already Used. ERROR: , line #715: Name Already Used. ERROR: , line #720: Name Already Used. ERROR: , line #1014: Name Already Used. ERROR: , line #1019: Name Already Used. Import problem: Name Already Used. ... WARNING: Instance: 1353NM_3 Component: NMS Menu: ID Not Defined. Skip Action WARNING: Duplicate Id : Instance 1353NM_3 Number: 3 WARNING: Instance: 1353NM_3 Component: NMS Menu: ID Not Defined. Skip Action WARNING: Duplicate Id : Action_1 Instance: 1353NM_3 Number: 3 Table 35. 1353NM Useless Custom Error and Warning messages
ED
RELEASED
Optics
146/157
1AA 00014 0004 (9711) A4
NMS
Useless Error and Warning Messages to be ignored. NOTE: Importing AsCurrentUsm.import definitions ...
1354RM
Importing from file:/usr/Systems/1354RM_6/SEC/repository/secimimports/AsCurrentUsm.import ERROR: , line #12: Name Already Used. ERROR: , line #17: Name Already Used. ERROR: , line #34: Name Already Used. ERROR: , line #39: Name Already Used. ERROR: , line #56: Name Already Used. ERROR: , line #61: Name Already Used. ERROR: , line #82: Name Already Used. ERROR: , line #87: Name Already Used. Import problem: Name Already Used. Table 36. 1354RM Useless Custom Error and Warning messages
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
147/157
18 APPENDIX K: NEW DISK REQUEST

When the volume group free disk space is not enough for creating or extending file system or/and swap areas, the script issues a list like the following one, to require you to configure one or more disks in the volume group configuration: ___________________________________________________________________________ Disks Selection ___________________________________________________________________________ Device MByte Hardware Path Usage Type VolGroup ___________________________________________________________________________ c1t2d0 8672 0/0/1/1.2.0 Pri_Boot _Main_ vg00 c2t2d0 8672 0/0/2/0.2.0 Alt_Boot Mirror vg00 D c4t8d0 8672 0/4/0/0.8.0 _(free)_ ______ ________ D c4t9d0 8672 0/4/0/0.9.0 _(free)_ ______ ________ c6t12d0 8672 0/7/0/0.12.0 _(free)_ ______ ________ c6t13d0 8672 0/7/0/0.13.0 _(free)_ ______ ________ ___________________________________________________________________________ Select Data Area (Main instance) dev name or [q] to quit: You have to provide the device that has to be added to the volume group. The disk request list will be issued until the requested amount of disk space need will be not reached. Note: If you have the mirror disk protection before proceed read carefully the Disk Mirror Configuration Policy

Supprim : Disk Mirror Configuration Policy
Disk Mirror Configuration Policy

The disk mirror capability is used for two main purposes: 1. Allow system to survive in case of a single disk failure. 2. Allow system to survive in case of a single disk controller failure. It is possible to obtain better high availability only with a correct configuration of the disk resources available on the system. HP-UX. Mirror Disk/UX allows reaching the first target without specific configuration, but to be able to reach the second one you must have an appropriate system configuration in terms of hardware and software. The hardware suggested by Alcatel are design to allow mirror configuration that allow system to survive to disk controller failure, but the software configuration has to be done as shown in this paragraph to do not loose this capability. First of all you have to be able to identify the hard disk present in the configuration, them are usually identified by their file name. In particular the file name can be very helpful to identify the disk - controller relationship. Any disk in the configuration is identified by the following name: c#t#d# c[0-15] SCSI of Fibre Channel card instance of disk controller to which the disk is attached to. t[0-15] SCSI of Fibre channel address of the device on the interface. d[0-15] Is the device unit number, useful for disk array only, such as VA7110. Using the c# of disk file name is possible to identify the relationship between disks and controllers. HP-UX allows to connect a single disk to two different controller (Dual-Access), in this case the system command can show two device file for the same disk units, but the installation script manage this configuration by showing just one device with a D on the first column of the related line.
ED
RELEASED
Optics
148/157
1AA 00014 0004 (9711) A4
Now you have to define two disk group (physical volume group) with the following characteristics: 1. The sum of disk space amount of the two group have to be the same.
2. The Dual-Access disks can be assigned to any group. 3. The non Dual-Access disks connected to the same controller MUST belong to the same group. The following picture is a schematic example of disk configuration that can produce the output shown before. This is not a typical system, but provided all the case that can occur in field.
c1t2d0 c2t2d0
c4t8d0
c4t9d0
c6t12d0
Figure 19 - Disks configuration Example
c6t13d0
With this configuration the best one are: group 1 with c1t2d0, c4t8d0 and c4t9d0, group 2 with c2t2d0, c6t12d0 and c6t13d0. group 1 with c2t2d0, c4t8d0 and c4t9d0, group 2 with c1t2d0, c6t12d0 and c6t13d0. Because the I/O channel are balanced. Allowed configuration can be: group 1 with c4t8d0, c1t2d0, and c2t2d0, group c4t9d0, c6t12d0 and c6t13d0. Wrong configuration: group 1 with c1t2d0, c4t8d0 and c6t12d0, group 2 with c2t2d0, c4t9d0 and c6t13d0. Because the two non dual-access disks have been assigned to the two groups, and the controller failure gets the system in failure too.
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
149/157
19 APPENDIX L: RETRIEVE HP-UX SYSTEM INFORMATION Overview

This appendix show how retrieve installation relevant information from the a running hp-ux system. This section requires the root access for each command.
Retrieve IP Network Information

Retrieve the hostname and lan0 IP address useful for HP-UX installation entering: ,sys,root # hostname ,sys,root # ifconfig lan0 Print the /etc/host file contents by entering: ,sys,root # lp /etc/hosts To retrieve all LAN IP Address configured on the system enter the command: ,sys,root # netstat -in
Write down the IP Address of each LAN card. Check if the dynamic routing is enabled looking at the GATED variable into /etc/rc.config.d/netconf file, if it is set to 0, the dynamic routine is disable in this case enter the following command to retrieve the static routing setup: ,sys,root # grep ROUTE /etc/rc.config.d/netconf The command output will show you the current routing configuration. Otherwise, if GATED variable is not set to 0, that means the dynamic routing is enable, in this case the relevant file is /etc/gated.conf print it out by entrering: ,sys,root # lp /etc/gated.conf If the file /etc/resolv.conf exist print it out by entring: ,sys,root # lp /etc/resolv.conf
Retrieve User Information

Print out the user and group defined by entering the command: ,sys,root # lp /etc/passwd /etc/group
Retrieve Time Zone

Print time zone defined by entering the command: ,sys,root # lp /etc/TIMEZONE
ED
RELEASED
Optics
150/157
20 APPENDIX M: 1354RM PRE-OTN TO OTN MIGRATION Overview

This appendix shows how to migrate 1354RM WDM TP chain from pre-OTN to OTN. The preOtnToOtn procedure, available in 1354RM-NRMIG.R7.4.3 conversion tool, is composed by two phases: d. In the first phase, it retrieves 1626LM nodes and, starting from these nodes, the OPS physical connections, the OCH trails, and the WDM client paths. It creates in /tmp/preOTNtoOTN the .pdl files containing commands useful to remove paths, trails and physical connections and to recreate them. e. In the second phase the operator is requested to execute the .pdl files previously created in order to re-create all the objects needed to restore the network with WDM OTN TP chain. Warning! The procedure described in this appendix has to be applied only in case of 1354RM migration from NR7.1 or NR7.3, and only if the network contains 1626LM 2.0 or 2.0A NEs.
preOtnToOtn procedure
Login on the 1354RM target machine as user snml. 1. Launch preOtnToOtn tool performing the following commands: $ . /usr/snml/.snmlrc $ unset NLPMAUTOMATICAFTERPATHDISCOVERY $ $ $ $ export NAV_PORT_NUMBER=1 export ApplicationTraceFile=/tmp/batch_trace.txt cd /usr/Systems/1354RM_1-7.4.9/NRMIG/sql ./preOtnToOtn.pl
2. In order to remove WDM client paths and trails crossing the 1626LM NEs, answer yes to the following question: Remove path and trail in all physical OPS startup the batch file removePathTrail.pdl Do you want to start ? yes(started) or next step ... If the procedure ends with the following message: rmBatchUtil.exe exit code = <0> go to the next point, else verify the trace file /tmp/preOTNtoOTN/log/removePathTrail.pdl.log and go to Error during procedure paragraph. 3. In order to remove OPS physical connections starting from 1626LM NEs, answer yes to the following question: Remove all physical OPS startup the batch file removePhy.pdl Do you want to start ? yes(started) or next step ... If the procedure ends with the following message: rmBatchUtil.exe exit code = <0>
1AA 00014 0004 (9711) A4

Supprim : Error during procedure
go to the next point, else verify the trace file /tmp/preOTNtoOTN/log/removePhy.pdl.log and go to
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
151/157
Error during procedure paragraph. 4. In order to re-create OPS physical connections starting from 1626LM NEs and to start the discovery of WDM trails and client paths, perform the following steps: a. Stop pmMng process from 1354RM Process Monitor b. When pmMng process is stopped, answer yes to the following question: Continue tool preOtnToOtn when pmMng is down? yes(started) c. Answer yes to the following question: Create all physical OPS startup the batch file createPhy.pdl Do you want to start ? yes(started) or next step ... If the procedure ends with the following message: rmBatchUtil.exe exit code = <0> go to the next point, else verify the trace file /tmp/preOTNtoOTN/log/createPhy.pdl.log and go to Error during procedure paragraph. 5. In order to restore client path userlabels as they were before migration, answer yes to the following question: Modify label path startup query in Database Do you want to start ? yes(started) or next step ... 6. In order to correlate WDM client paths to PM measure, perform the following steps: 1. Start pmMng process from 1354RM Process Monitor 2. When pmMng process is started, answer yes to the following question: Continue tool preOtnToOtn when pmMng is running? yes(started) 3. Answer yes to the following question: Create all PM startup the batch file createPm.pdl Do you want to start ? yes(started) or next step ... If the procedure ends with the following message: rmBatchUtil.exe exit code = <0> go to the next point, else verify the trace file /tmp/preOTNtoOTN/log/createPm.pdl.log and go to Error during procedure paragraph. 7. At the end of the procedure, restore the original value of NLPMAUTOMATICAFTERPATHDISCOVERY variable,: 7. Stop pmMng process from 1354RM Process Monitor 8. Execute the following command: $ export NLPMAUTOMATICAFTERPATHDISCOVERY='ACTIVAT' 9. Start pmMng process from 1354RM Process Monitor
1AA 00014 0004 (9711) A4

All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel Supprim : Error during procedure

ED
RELEASED
Optics
152/157
Error during procedure

By default, preOtnToOtn procedure launches rmBatchUtil with stop option, i.e. rmBatchUtil stops on first error and returns an error code different from <0>. In case of error during the execution, the operator has to manually recover the situation (ex: if a physical connection isnt deimplemented, he has to deimplement it from RM browser) and restart the procedure from the point where it was interrupted, executing the following steps: 1. Skip all the remaining steps of preOtnToOtn procedure by pressing [Enter] to all questions. 2. Save the .pdl file in which the error was located. Ex. if the error was during physical connection creation, execute: $ cd /tmp/preOtnToOtn $ cp createPhy.pdl createPhy.pdl.orig 3. Edit the .pdl file removing all the commands successfully executed. 4. Launch preOtnToOtn procedure with an option that doesnt create again the .pdl files: $ cd /usr/Systems/1354RM_1-7.4.9/NRMIG/sql $ ./preOtnToOtn.pl noPdl 5. Skip all the steps of preOtnToOtn procedure successfully executed by pressing [Enter] to all questions, except the following where have always to answer yes Continue tool preOtnToOtn when pmMng is down? yes(started) and Continue tool preOtnToOtn when pmMng is running? yes(started) 6. Continue the procedure as described in the previous paragraph from the point where it was interrupted.
Note: Its also possible to start preOtnToOtn procedure with noStop option: in this case rmBatchUtil doesnt stop on error. Using this option the operator can execute the whole .pdl file also if some errors occur during execution. The steps of preOtnToOtn procedure end with error code <0>, so the operator has always to check log files to verify that the step was correctly executed. In case of error the operator has to manually recover the situation from RM browser, before continuing the procedure from the point where the error was detected.
1AA 00014 0004 (9711) A4
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
153/157
21 APPENDIX N: TROUBLESHOOTING
Error during scmanageswp resume procedure

If scmanageswp resume procedure fails and the following (or similar) error appears in /SCINSTALL/scinstall.log: ERROR: "ipb082:/": The software dependencies for 1 products or filesets cannot be resolved. * The analysis phase failed for "ipb082:/". * Analysis had errors. the problem looks related to a HP Software Distributor bug that is fixed by a patch included in a patch bundle provided for NR8.1 PL2. To workaround this problem execute the following procedure, as root: 1. Install the patch: From DVD: ...,sys,root # ...,sys,root # ...,sys,root # From depot: ...,sys,root # swinstall -s <depot server>:<depot directory> PHCO_35587 2. If the file /SCINSTALL/execution/41001SC.SCinst_reboot.env exists, modify its last line from: SCI_PRD_SWOPT="" ; export SCI_PRD_SWOPT to: SCI_PRD_SWOPT="-x autoselect_dependencies=false" ; export SCI_PRD_SWOPT 3. Rename the file /SCINSTALL/execution/*.in_progress removing ".in_progress" from file name. 4. Restart the installation process: ...,sys,root # /SCINSTALL/SCINSTALL start scmountcd /dev/dsk/<dvd special file> /SD_CDROM swinstall -s /SD_CDROM PHCO_35587 umount /SD_CDROM
Error during System Configuration

If RM or BMETH System Configuration fails creating Oracle DB and the file /usr/Systems/<NMS>_<NMS_Id>_<NMS_vers>/ORACLE/databases/dbnml/admin/create/crdb_phase1.log contains the following errors: SQL> startup nomount pfile=/usr/Systems/1354BMETH_1_8.1.5_Master/ORACLE/database s/dbnml/admin/pfile/init0.ora ORA-27154: post/wait create failed ORA-27300: OS system dependent operation:semget failed with status: 28 ORA-27301: OS failure message: No space left on device ORA-27302: failure occurred at: sskgpbitsper the problem looks related to target release Apache startup failure and retries that allocates many semaphores (probably w/a at point 7 page 25 wasnt executed immediately after KernelCustomize completion). To workaround this problem execute the following procedure, as root: 1. Verify the existence of many semaphores allocated by www owner:
ED
RELEASED
Optics
154/157
...,sys,root # ipcs s | grep www An output like the following will be displayed (where the third coloumn contains 0x00000000): s 1 s 1 s 1 s 1 s 1 s 1 s 1 s 1 s 1 s 1 30 0x00000000 8:17:39 31 0x00000000 8:17:52 8:17:39 160 0x00000000 no-entry 8:18:40 34 0x00000000 no-entry 8:18:44 35 0x00000000 8:19:14 8:18:44 164 0x00000000 no-entry 8:19:46 38 0x00000000 no-entry 8:19:50 39 0x00000000 8:19:54 8:19:50 168 0x00000000 no-entry 8:20:49 42 0x00000000 no-entry 8:20:54 no-entry
--ra--------ra--------ra--------ra--------ra--------ra--------ra--------ra--------ra--------ra-------
www www www www www www www www www www
other other other other other other other other other other
root root root root root root root root root root
root root root root root root root root root root
2. Remove semaphores using the command: ...,sys,root # ipcs -s | grep 0x00000000 | while read uno id foo do ipcrm -s $id done 3. Restart System Configuration procedure.
Database extension
Oracle uses pre-allocated and not extendible tablespaces, so it could happen that db import fails and in import_db.log you can find one of this messages:
ORA-01650: unable to extend rollback segment <xxx> by xxx in tablespace <ts_name> ORA-01652: unable to extend temp segment by <xxx> in tablespace <ts_name> ORA-01659: unable to allocate MINEXTENTS beyond <xxx> in tablespace <ts_name>
To solve the problem the tablespace must be extended using the following procedure: For 1354RM db: Login on the spare machine as user snml. If necessary startup 1354RM database: ... ... ... ...
1AA 00014 0004 (9711) A4
$ $ $ $
cd /usr/Systems/1354RM_1 . ./.snmlrc cd ORACLE/databases/dbnml/etc start_db
Execute: ... $ sqlplus /nolog
ED
RELEASED
Optics
8DG 31466 AAAATCZZA
155/157
SQL> connect / as sysdba

SQL> alter tablespace <ts_name> add datafile '/usr/Systems/1354RM_1/databases/dbsnml/data/<datafile>02.dbf' size <xxx> M; Stop 1354RM database: ... $ cd /usr/Systems/1354RM_1 ... $ cd ORACLE/databases/dbnml/etc ... $ stop_db For 1354BMETH db: Login on the spare machine as user bmml. If necessay startup 1354BMETH database: ... ... ... ... $ $ $ $ cd /usr/Systems/1354BMETH_1 . ./.bmmlrc cd ORACLE/databases/dbnml/etc start_db
Execute: ... $ sqlplus /nolog SQL> connect / as sysdba SQL> alter tablespace <ts_name> add datafile '/usr/Systems/1354BMETH_1/databases/dbbmml/data/<datafile>02.dbf' size <xxx> M; Stop 1354BMETH database: ... $ cd /usr/Systems/1354BMETH_1 ... $ cd ORACLE/databases/dbnml/etc ... $ stop_db In the previous sqlplus session a new datafile <datafile>02.dbf for the tablespace <ts_name> is created. It is recommended to create the new datafile with the same size of the previous one.
ED
RELEASED
Optics
156/157
1AA 00014 0004 (9711) A4
ED
Optics
RELEASED
END OF DOCUMENT
8DG 31466 AAAATCZZA
157/157

Copie de Nr81pl2 1350 Mig Ed06

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Copie de Nr81pl2 1350 Mig Ed06

Hochgeladen von

Copyright:

Verfügbare Formate

All rights reserved.

1350 Management Suite Migration Guide NR8.1PL2

8DG 31466 AAAA TCZZA

8DG 31466 AAAA TCZZA

PLATFORM UPGRADE ......................................................................................................... 93

7.1 UPGRADE PLATFORM TO THE LATEST OS-CONF PATCH ...................................................................... 93

8DG 31466 AAAATCZZA

APPENDIX A: SUMMARY TABLES ...................................................................................... 95

8DG 31466 AAAA TCZZA

1AA 00014 0004 (9711) A4

8DG 31466 AAAATCZZA

8DG 31466 AAAA TCZZA

Date Oct 2008 Nov 2008 Nov 2008

Notes Third Edition internal use only (R&D) Forth Edition

Ed06 = internal ed10

1AA 00014 0004 (9711) A4

8DG 31466 AAAATCZZA

INTRODUCTION General Information

NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

8DG 31466 AAAA TCZZA

1.3.1 Handbooks related to the specific software application

1350 Rel8.1 Installation Guide 1350 Rel8.1 Administration Guide

1.3.2 NR 8.1 Related Handbooks

3AL 88851 AAAA

3AL 88127 BAAA

[5] [6] [7] [8] [9] [10] [11] [12]

1AA 00014 0004 (9711) A4

8DG 31466 AAAATCZZA

8DG 31466 AAAA TCZZA

OS-Kernel 7.1.1 OS-Kernel 7.1.2

OS-Kernel 7.1.2 OS-Kernel 7.1.2

1AA 00014 0004 (9711) A4

8DG 31466 AAAATCZZA

Whats in this document

8DG 31466 AAAA TCZZA

1AA 00014 0004 (9711) A4

MIGRATION PROJECT AND PRODUCT INFORMATION

Restrictions and Preconditions

2.1.1 Mandatory Patches

2.1.2 RM and BM-ETH DB schema check on the starting NR

... $ cd /usr/Systems/1354RM_1 ... $ cd ORACLE/databases/dbnml/etc ... $ stop_db

8DG 31466 AAAATCZZA

If you are checking 1354BMETH db schema:

If you are checking 1354BMETH db schema:

8DG 31466 AAAA TCZZA

1AA 00014 0004 (9711) A4

8DG 31466 AAAATCZZA

MIGRATION IN A COMPLEX NETWORK

3.1.1 One Shot ISE Migration

3.1.2 Stepped ISE Migration

8DG 31466 AAAA TCZZA

Customize each NM 7.0 Client in the target NR.

g. Execute the integration.

3.1.3 One Shot Migration with Spare

3.1.4 Stepped Migration with Spare

8DG 31466 AAAATCZZA

Execute the integration.

Start the system.

Mise en forme : Puces et numros

8DG 31466 AAAA TCZZA

1AA 00014 0004 (9711) A4

BM-ETH 7.3 Master ID 1 RM 7.1 Master ID 1 NM 7.0 Client ID 1 NM 7.0 Client ID 2

Figure 1 - Migration Starting configuration