You are on page 1of 157

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

6

RELEASED

8DG 31466 AAAA TCZZA

1/15715715 7157

SUMMARY
1 INTRODUCTION ....................................................................................................................... 8 1.1 GENERAL INFORMATION....................................................................................................................... 8 1.2 HANDBOOK APPLICABILITY ................................................................................................................... 8 1.3 PRODUCT–RELEASE 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 WHAT’S 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

6

RELEASED

Optics

8DG 31466 AAAA TCZZA

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

6

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 ............. 102 APPENDIX D: NMS SWPDESC............................................................................................................................ 106 APPENDIX F: 1353NM DATA CONVERSION...... 151 APPENDIX N: TROUBLESHOOTING................................................................... 146 APPENDIX K: NEW DISK REQUEST........................................................................ not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 APPENDIX B: SW PACKAGES ............................................................................................................ 113 APPENDIX G: 1354RM DATA CONVERSION ....................... 150 APPENDIX M: 1354RM PRE-OTN TO OTN MIGRATION............. 154 ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 4/157 . 99 APPENDIX C: REQUIRED DISK SPACE ......................................... 138 APPENDIX I: 1354RM SEC (SECURITY) DATABASE ADAPTATION ...................................................... 114 APPENDIX H: 1354BM-ETH DATA CONVERSION..... 148 APPENDIX L: RETRIEVE HP-UX SYSTEM INFORMATION ......................................... Passing on and copying of this document........... 104 APPENDIX E: DATA EXPORT/IMPORT............................................ use and communication of its contents...................... 143 APPENDIX J: CUSTOM WARNING AND ERROR................................... 95 All rights reserved................................................................................................................................................................................... OS-CONF AND INSTALL WIZARD UPGRADE .........

...........................97 1354RM Process Configuration.........140 1353NM Useless Custom Error and Warning messages ................ Passing on and copying of this document........4 .......... Table 9........................................101 Disk requirements for NMS Software for NR8.............................. Table 3........................................................97 1353NM Process Configuration............................ Processes for 1354RM Database..........................................................................NMS Instance Information ............146 1354RM Useless Custom Error and Warning messages ........................................................95 Upgrade/ISE ........................103 Oracle Not Relevant Errors In Database Conversion....................................................................................................................100 NMS Version from NR 7......102 Disk requirements for NMS Software for NR8.............1 PL2 .........4 NMS version for Install_Wizard ........36 Upgrade/ISE ..99 NMS Versions from NR7.........................1...4 . Table 10.................................... Table 15...................................... Table 6.................................................................... Table 17........... Table 7...........................................................................................101 NMS Specific Administration Users ............................................100 NMS Version from NR7..147 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 5/157 .................................2 to NR 7.96 NR7...............................................................4 ....................98 Upgradeable NMS software...3 to NR7......................1 to NR 7.................................................... not permitted without written authorization from Alcatel Table 1................. use and communication of its contents..................................................1 PL2 ............................................. TABLE All rights reserved... Table 13........... Table 4................ Table 12.......Software Packages and Data Instances........................................100 NMC keys .........1D/7................ Table 8.................................................................................. Table 14............. Table 16........................................ Table 11................................ Table 2.................................. Table 5................

...............A................... 107 Figure 15 ........................................................ 143 Figure 17 ................... List window ................................ List window ..........................“Operator profile” list................................................................................................... not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 6/157 ......... 30 Figure 5 ...................................Export GUI window................................................................................................... 76 Figure 11 ...................... ................................ ........................................................................ List window ..............................................................Upgrade Custom log window........... 31 Figure 6 ...................... ....................................................... 87 Figure 14 .............................................“Operator” in SEC graphical interface ........ Instance..................Upgrade Custom log window.......... 65 Figure 10 .....................Disks configuration Example ......Upgrade System.... 144 Figure 18 ................................................................................................................................................................................Migration Starting configuration... 77 Figure 13 ....Upgrade System.............................. 63 Figure 8 ............................................................................................................................................................................................... 19 Figure 2 .........Upgrade System...................................................................Import GUI window .. 64 Figure 9 ............Prerequisite System Instances List Window ............................................... 149 All rights reserved....................ISE Customize Parameter Definition window............Customize Parameter Definition window................................. List window ............................................................... 49 Figure 7 ........................................... FIGURES Figure 1 ..... Instance................... 144 Figure 19 .....Upgrade Custom log window........................Migration Target configuration................................................... 76 Figure 12 ...Upgrade System.. 19 Figure 3 ........................... 29 Figure 4 ................. Instance.. Passing on and copying of this document......................................................Customize Parameter Definition window.................... 108 Figure 16 ................ use and communication of its contents....................Remove of the profile with the same name of “Operator” ............... Instance............................................

HISTORY All rights reserved. Ed06 = internal ed10 September 2009 Sixth edition 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 7/157 . Passing on and copying of this document. use and communication of its contents. not permitted without written authorization from Alcatel 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.

2 Handbook applicability This handbook applies to the following product–releases: PRODUCT 1350 PRODUCT 1350 N.B. COPYRIGHT NOTIFICATION The technical information of this manual is the property of ALCATEL and must not be copied. 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. use and communication of its contents. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 8/157 . 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. whether direct. consequential.1 INTRODUCTION General Information WARNING All rights reserved. Passing on and copying of this document. in connection with the furnishing. indirect. should the screen prints included in the handbook contain the product–release’s ”version” marking. 1.1 VERSION (N.) 8. reproduced or disclosed to a third party without written consent.1 1.1 ANV P/N ANV P/N NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS Handbooks relevant to software applications (typically the Operator’s 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. incidental.: RELEASE 8. they are not replaced in the handbooks related to a subsequent version. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 ALCATEL makes no warranty of any kind with regards to this manual. if the screen contents are unchanged.B. They do not represent any obligation on the part of ALCATEL. or special. Moreover.

Some of the handbooks listed here below may not be available on the issue date of this Handbook.1D/7.5 Administration Guide 1354BMETH R7. not permitted without written authorization from Alcatel Product–release 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.3. use and communication of its contents.3.4/8.3.2/7.3 Operator’s Handbook 1353NM 7.1.3/7.1 Installation Guide 1350 Rel8.1 Administration Guide 1. 7.3 Administration Guide 1354RM 7.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 6 RELEASED Optics 8DG 31466 AAAATCZZA 9/157 .1 Installation and Administration Guide 1354BMETH 7.1.1 OND Network Management Configuration Guide 1359HA OS-Cluster 7.1 Related Handbooks REF HANDBOOK ANV Part No.0 Administration Guide 1359IOO 5.1. The standard Customer Documentation in the English language for the equipment whose product–release– version is stated in para. THIS HANDBOOK [1] [2] 1350 Rel8.2 Administration Guide 1359ISN 5.3 All rights reserved. Passing on and copying of this document.1 Administration Guide 1355VPN 5.4 Administration Guide 1359HA OS-Resilience 7.1 Handbooks related to the specific software application REF HANDBOOK ANV Part No. THIS HAND BOOK [3] 1350 Rel.2 on page 7 consists of the following handbooks: 1.0.2 NR 8.

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. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 10/157 . Courier indicates system prompts. and other countries. 4. ORACLE® is a registered trademark of Oracle Corporation. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 1. throughtout the guide “1” will be used as instance id. HP® is a registered trademark of Hewlett-Packard Corporation. use and communication of its contents. Arial shown between angle brackets means that these data depending by the particular instance of the system. 5. All rights reserved. For semplicity. Double quotation Arial italic means a cross reference. 2.4 1. HP9000® and HP-UX® are trademarks of Hewlett-Packard Corporation. Passing on and copying of this document. OSF/Motif® is a trademark of the Open Software Foundation.1. Bold courier indicates information that you must enter from the keyboard. Registered Trademarks UNIX® is a registered trademark of UNIX System Laboratories in the U. 3. It must be substituted with the correct data.S. Obviously substitute it with the real instance id.A. Courier font included in a grey box is uses to indicate the output produced by the system or data that you can find.

1 P14 1353NM …. Scope The document contains the technical description of the steps needed to successfully update a TMN application: 1. Alcatel Field Engineers 4.2 The upgrade is supported only the version specified in Upgradeable NMS software table.1. 1354BMETH 7. during this phase the application can be up and running.4 1 Alcatel Software Components. 1354BMETH 7.0. not permitted without written authorization from Alcatel Overview Audience This document describes the technical process to migrate some1 OND Network Management application running on HP platform to Network Release 8. Alcatel employees who have to plan or to execute migration tasks This document was written with the customer in mind but anyhow.3 P1 1353NM 7. 1354RM 7.1D/7. It is not allowed to use this guideline as your customer specific handbook.3.13. Note: this document does not describe your particular migration. 1354RM 7.1.1.2 PL1.1PL2 network release: Network Release Mandatory NR7. 1.1D/7.3 NR7.0.1.2 OS-Kernel 7. Alcatel Project Leaders 3.0. The 1354BM ETH is supported only starting with NR7. Alcatel Product Managers 2.13. In System Evolution (ISE): this approach allows updating the running application installing on a separate “installation tree” the target SW. use and communication of its contents.1T PL1 NR7.80. The intended readers are: 1.2 OS-Kernel 7.14. 1AA 00014 0004 (9711) A4 2 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 11/157 .1.42 1353NM 7. 1354BMETH 7. Passing on and copying of this document. it contains Alcatel proprietary information and shall not be released to customers without prior adaptation to customer needs and skills.2 PL2 NR7. Any combination of IM or USM or both 1353NM 7.1.1.1. 1354BMETH … OS-Kernel 7.1 OS-Kernel 7. 1354RM ….1.1. without needed customizations.6 All rights reserved.7 Document Overview This document provides the guidelines to upgrade an Alcatel TMN system installed with one of the following configurations to NR8. but should only serve as a guideline for writing your customized handbook. 1354RM 7.1 P14 2.

Chapter 1 “Introduction” Document introduction with convention and short chapter descriptions. Chapter 2 “Migration project and product information” 3. and switch over to new software when ready. Chapter 7 “Platform Upgrade” It describes how upgrade HP-UX™ and third party software on the system. Passing on and copying of this document. use and communication of its contents. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 12/157 1AA 00014 0004 (9711) A4 All rights reserved. Appendixes The appendixes include some common procedure in migration.Any software configuration not included in this table cannot be object of upgrade or migration with this document. and the involved hardware resource. Chapter 5 “Migration With Spare System” 6. It has been design to reduce the downtime and the system freeze time. not permitted without written authorization from Alcatel . 1. Chapter 4 “In System Evolution (ISE)” It provides the guidelines to upgrade the software on the running system. 2.8 What’s in this document This document includes the following topics: 1. 5. 7. 8. Chapter 3 “Migration In A Complex Network” 4. Chapter 6 “Verify Pre-conditions” This chapter describes how to identify the installed software and verify if the migration precondition are met.

1 Create DB schema reference files After creating new databases on the spare machine execute the following procedure. $ $ $ $ cd /usr/Systems/1354RM_1 . $ cd ORACLE/databases/dbnml/etc .1 Mandatory Patches NR8.5....The procedure can be executed anytime before the migration. . If relevant differences are discovered please ask for support before starting the migration.1. ...1./MIB_Contents get /alcatel/DEPOT/NR<source NR>_RM_DB_Ref 4.1..1PL2 DR4 composition + 1354RM 7. $ cd /usr/Systems/1354RM_1/ORACLE/script/ .. as root: chmod 777 /alcatel/DEPOT e repeat the command) .2 All rights reserved. .2... OS-KERNEL 7.0. Stop 1354RM database: 1AA 00014 0004 (9711) A4 .5....1. using the procedure detailed hereafter.1-P15.6 and 1354RM 7. not permitted without written authorization from Alcatel 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.5. Login on the spare machine as user snml 2. NR8.snmlrc cd ORACLE/databases/dbnml/etc start_db 3. 2.0.. Get a snapshot of the database: .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. If necessary startup 1354RM database: ...1 Restrictions and Preconditions Hereafter the list of restrictions and precondition to be fulfilled before the migration can start. The procedure must be executed on a spare machine installed with the same software/patch of the customer machine...2-RP19.3-P6RP1 must be installed on the target system in order to run the migration. in addition to the SW delivered via DVD also two additional patches.1 PL2 DR4 composition foresees.1.. Passing on and copying of this document. If you are checking 1354RM db schema: 1. $ cd /usr/Systems/1354RM_1 . $ chmod 777 /alcatel/DEPOT/NR<source NR>_RM_DB_Ref . Do not use customer machines! 2./.. use and communication of its contents. $ stop_db ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 13/157 .1-P16 + 1354BMETH 8. $ . .... 2. $ mkdir /alcatel/DEPOT/NR<source NR>_RM_DB_Ref (if you get an error execute.

$ cd /usr/Systems/1354RM_1/ORACLE/script/ . use and communication of its contents.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../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. $ stop_db 2. not permitted without written authorization from Alcatel 1... $ .If you are checking 1354BMETH db schema: All rights reserved. .snmlrc sqlplus $NXNL_DATABASE mkdir /alcatel/DEPOT/NR<source NR>_RM_DB_Cust chmod 777 /alcatel/DEPOT/NR<source NR>_RM_DB_Cust 2. Login on the spare machine as user bmml 2. Compare the current DB schema with the expected one (one only line): .. $ $ $ $ cd /usr/Systems/1354BMETH_1 . $ mkdir /alcatel/DEPOT/NR<source NR>_BMETH_DB_Ref (if you get an error execute..... 2. ..bmmlrc cd ORACLE/databases/dbnml/etc start_db 3. . 1AA 00014 0004 (9711) A4 If you are checking 1354BMETH db schema: ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 14/157 ./MIB_Contents get /alcatel/DEPOT/NR<source NR>_BMETH_DB_Ref 4. $ cd /usr/Systems/1354BMETH_1/ORACLE/script/ ...1.. Get a snapshot of the database: . $ . $ cd ORACLE/databases/dbnml/etc . . .2. .log If you find any significant difference please contact TEC Italy before starting the migration../. as root: chmod 777 /alcatel/DEPOT e repeat the command) ..../. .1.. Stop 1354BMETH database: . $ .2. If necessay startup 1354BMETH database: . $ chmod 777 /alcatel/DEPOT/NR<source NR>_BMETH_DB_Ref ........ Login on the spare machine as user snml .. Passing on and copying of this document. .. Check the log file just created: . $ $ $ $ $ cd /usr/Systems/1354RM_1 ....log 4......3 Check DB schema If you are checking 1354RM db schema: 1. $ cd /usr/Systems/1354BMETH_1 .... . $ vi /alcatel/DEPOT/NR<source NR>_RM_DB_Diff.. Get a snapshot of the database: ./MIB_Contents get /alcatel/DEPOT/NR<source NR>_RM_DB_Cust 3...

.. Get a snapshot of the database: . $ ../... Compare the current DB schema with the expected one (one only line): .. $ ...bmmlrc sqlplus $NXNL_DATABASE mkdir /alcatel/DEPOT/NR<source NR>_BMETH_DB chmod 777 /alcatel/DEPOT/NR<source NR>_BMETH_DB All rights reserved.log 4.1. $ $ $ $ $ cd /usr/Systems/1354BMETH_1 .. $ cd /usr/Systems/1354BMETH_1/ORACLE/script/ . Passing on and copying of this document. Check the log file just created: ../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. ... use and communication of its contents. .. not permitted without written authorization from Alcatel 2. Login on the spare machine as user bmml ..log If you find any significant difference please contact TEC Italy before starting the migration. $ vi /alcatel/DEPOT/NR<source NR>_BMETH_DB_Diff. . 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 15/157 .... . ./MIB_Contents get /alcatel/DEPOT/NR<source NR>_BMETH_DB 3..

3. Start with BM-ETH/RM server. 3. e. where many systems can operate together to perform their job. use and communication of its contents. data export/import and conversion.1. 4. This approach is mandatory for cohosted Master NMSs.1. Install the foreseen software.9 and BM-ETH 8. 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. Passing on and copying of this document. 5.to the one shown in Figure 2 . Predispose the system for the target configuration (new software and new NMS instances) b.9 and NM 7. d.2 Stepped ISE Migration If you have to upgrade from the configuration shown in Figure 1 . A way to achieve it is. Not doing so can have disruptive effects on the system! 3. When more than one system is involved in migration.4.5 Master instances. Execute the integration. Start the system. 8. Install the entire software requested (BM-ETH 8. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 The 1350 Management Suite is a hierarchical architecture.4. data export/import and conversion.5). Start the migration on all system at once. Customize the RM 7. 6. Remove old instances and software. Warning! During stepped migrations (with Spare or ISE) always migrate remote client instances after their respective master instance. One Shot: all NMSs are migrated at the same time. not to start the mediator. Apply a migration procedure in this environment requires to have a clear picture of the machine relationship. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 16/157 . 2. Perform Master instances “System configuration”. it can be performed in two ways: 1.3 MIGRATION IN A COMPLEX NETWORK All rights reserved. Perform Master instances “System configuration”. for example. 2. 9. Stepped: first 1354RM and 1354BMETH are migrated. a. Deactivate the source NR and activate the target one. Predispose for the final configuration.you have to proceed this way: 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 .1.1.you have to proceed this way: 1. and how proceed in the upgrade on different machine.5. c.4. Deactivate the source NR and activate the target one. Customize the off line Master and Client instances of the new software version. 7. RM 7.

Perform Master instances “System configuration”.5 Client on RM 7. Predispose the system for the target configuration (new software and new NMS instances) g. Customize each NM 7. g.0 software.4.0 Client in the target NR. 1AA 00014 0004 (9711) A4 Perform Master instances “System configuration”. data export/import and conversion. Install old SWPDESC and Install_Wizard. a. Start the system. use and communication of its contents.4. j. Passing on and copying of this document.9 and BM-ETH 8.4.1.you have to proceed this way: ˆ Install the spare machines.0 SWP and Client Instance. 3.1. Start the system. Customize the RM 7.0 Client instance on RM 7. ˆ Start the system. e. Install the entire software requested (NM 7. For each 1353NM Master: a.4. c.4.5 Master instance.5 Master instances.f. b. not permitted without written authorization from Alcatel h.9/BM-ETH 8.to the one shown in Figure 2 . Only when all the NM 7. Decustom NM 7.2 i.1.to the one shown in Figure 2 .2 f.5. data export/import and conversion. Execute the integration.4.4. Upgrade to target SWPDESC and Install_Wizard. Predispose for NM 7. Remove integration of NM 7. 3. Execute the integration. 2. Deactivate the source NR and activate the target one. Start with BM-ETH/RM server. Customize the NM 7.0 Master from RM 7.1. ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 17/157 . g.4.3 One Shot Migration with Spare If you have to upgrade from the configuration shown in Figure 1 .1.1.9 and NM 7.4.you have to proceed this way: a.4. j. 3. Install the entire software requested (BM-ETH 8.1.0 Clients have been upgraded to 7. ˆ Perform data export/import and conversion. i.0 Client in the target NR.9/BM-ETH 8. Custom NM 7. h. Install NM 7. Customize each NM 7.9/BM-ETH 8.5). d. c.5 you can remove old instances and software on all the machines. e.5). ˆ Swap the system. Predispose the system for the target configuration (New software and new NMS instances) b.4 Stepped Migration with Spare If you have to upgrade from the configuration shown in Figure 1 . RM 7. Install target Os-Conf.2 h. All rights reserved. f. d.

1. Predispose the system for the target configuration (New software and new NMS instances) 3. For each 1353NM Master: 1. Execute the integration. Switch over to NM 7.0 Clients have been upgraded to 7.5 Master.9/BMETH 8.4. Execute the integration. Custom NM 7.0 Client instance on RM 7.5). Customize the NM 7. l. Install the entire software requested (NM 7. 4.1. Passing on and copying of this document.1. Remove integration of NM 7.k.2 9. data export/import and conversion. 2. 8.4. 1. Decustom NM 7.4.4. Install the spare machine. use and communication of its contents.5 Master instance. Mise en forme : Puces et numéros ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 18/157 1AA 00014 0004 (9711) A4 . Perform Master instances “System configuration”.4. 5. 6. 2.2 7. All rights reserved.9/BMETH 8. Start the system. Only when all the NM 7.5 Client on RM 7. not permitted without written authorization from Alcatel Start the system. 11.4.2 10.9/BM-ETH 8.4.5 you can remove old instances and software on all the machines.0 Master from RM 7.4.

5 Master ID 2 Figure 2 . use and communication of its contents.4.4.1.0 Master ID 1 NM 7. not permitted without written authorization from Alcatel Starting scenario BM-ETH 7.All rights reserved.4.5 Client ID 1 NM 7.Migration Target configuration 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 19/157 .5 Master ID 1 RM 7.0 Client ID 2 NM 7.5 Client ID 2 NM 7.3 Master ID 1 RM 7.0 Client ID 1 NM 7.1 Master ID 1 NM 7.5 Master ID 1 NM 7.4.Migration Starting configuration Target scenario BM-ETH 8.9 Master ID 1 NM 7.0 Master ID 2 Figure 1 . Passing on and copying of this document.4.

The approach is based on the creation of a new instance as “data repository” and a new installation tree. One Shot is mandatory for Master NMS cohosted on the same machine.4 IN SYSTEM EVOLUTION (ISE) Overview All rights reserved. ISE migration can be performed with both One Shot and Stepped approach. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 This chapter describes the In System Evolution (ISE) procedure to upgrade an Alcatel NMS reducing as much as possible.alcatel.ond. the second one is specific to the chosen approach. the system down time period. Note: This document does not provide information for upgrading NMS installed with 1359HA OS-Cluster protections. These notes have to be intended as preparation’s steps for the ISE described in this chapter. use and communication of its contents.it). if there are some additional notes concerning the installation (select NR8 Æ NR8. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 20/157 . This allows to perform a big portion of the migration leaving the current system up and running. Passing on and copying of this document.1PL2 Æ “Installation_notes”).1 Installation and Administration Guide” [4] Important Recommendations Before proceeding with the ISE as described hereafter please verify on TEC WEB site (http://tec. refer “1359HA OS-Cluster 7. 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.

it is mandatory to have a full system backup. Copy OS-CONF 8.sys..2 package into /alcatel/DEPOT directory: OS-Conf812P01_2...root # cd / . you have to do it now by follow the instruction shown at “Full Backup/Restore” chapter of “1350 NM Administration Guide” [1].2 P01.sys. Supprimé : Verify Preconditions 4... 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: . If you do not have one.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. 4. refer to “Verify Pre-conditions” chapter for details. Note: With disk mirror configuration..sys. not permitted without written authorization from Alcatel Preparation Guide Lines 4.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 .. Passing on and copying of this document. OS-Conf and Install Wizard Upgrade 1. Only In case of HP ITANIUM system execute step 3: 3.2 Perform the System Backup Even if ISE procedure foresees a reverting procedure.sys.root # swinstall –s /alcatel/DEPOT/OS-Conf812P01_2.1.3 NMS SWPDESC.1. OS-CONF AND INSTALL WIZARD UPGRADE 4.depot \* (cksum & size: 403368502 51200) Mis en forme : Police :Gras.1 All rights reserved.1. OS-CONF AND INSTALL WIZARD UPGRADE” for the details related to this upgrade procedure.4. 2.root # EvalExportSize <NMS>_<NMS Id>-<NMS Ver> ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 21/157 ...depot and execute .1 Evaluate the ISE prerequisites Before to start the migration you have to verify that all requested pre-conditions have been correctly fulfilled. backup can be performed on line.1. Login as user root. Anglais (Royaume-Uni) Supprimé : APPENDIX D: NMS SWPDESC. Refer to chapter “APPENDIX D: NMS SWPDESC. and that you have retrieved all data requested during the upgrade.. use and communication of its contents.. Italique..

sys root # scmanageswp noreboot cmdfile <file name> Where: <file name> is the file previously created with “scautopredispose” tool.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.sys.5 Predispose the system for the NR8.. 1..sys root # scautopredispose -o <file name> Where: <file name> is the file previously created with “scautopredispose” tool.sys ..sys .5" descriptor file.1PL2 /usr/Systems/ Global_Instance-7. If you are migrating 1354RM or 1354BMETH execute the following command: . The final value will be the greater.. predispose manually all the instances with the command .. Login into the system as user root.. to avoid future machine reboot predispose all NMSs now. quit the procedure! Note: The installation from Network Depot can be performed only after the depot set-up..1PL2 Installation Guide” [1].root # /usr/local/bin/adjust_ora_group 4. Start “scmanageswp” tool entering: .. use and communication of its contents...7_Master 3. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 <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.... remove the symbolic links: .1.1. Warning! If you need to predispose a NM 7. Note: Do not forget “noreboot” option! If it’s the case.1.7 Global_Instance_7. 2.. Neglect warnings like the following: Warning: maxdsiz has a new ADD declaration in the same 1354BM_code_kp section on the "1354BMETH 8.. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 22/157 . for more information refer to “1350 Rel8.....sys . 4.3 Master instance to manage QB3* NEs.sys root root root root root # # # # # cd rm cd rm rm /alcatel/ 8..Where: All rights reserved. If present.... Passing on and copying of this document. Warning! If you prefer manual predisposition.1..... Start “scautopredispose” tool entering: .1PL2 NMS and instances.1PL2 software.sys .

1.. on the screen you should have a list of items selected for the configuration. 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. Press: [T] = Try again (but after you have attempt to close all pid(s) ) [A] = Abort (DANGEROUS ..--- 1 1 1 OSKERNEL 1354RM_IM_Small 1353NM_IM_Small Enter 'a' to Apply.4l_p7 /opt/tao_1.4 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 23/157 .4 does not point to /opt/tao1. In order to preceed in the configuration. like to the following: All rights reserved.operation is aborted) Mis en forme : Police :Italique Supprimé : APPENDIX K: New Disk Request [R] = Reboot (RECOMMENDED . 'c' to Cancel or 'd' to Display again: 6..4. check process with PID(s): …………………….root # mv /SCINSTALL/execution_parking/* /SCINSTALL/execution/ If the symbolic link /opt/tao_1.5 INSTANCE Number INSTANCE Dimension Opt --------------.4l_p7 execute: . procedure will ask for new disks.5 7. Passing on and copying of this document.operation will be completed after next reboot) then press [Enter] At the end of software upgrade. You can choose between CD-ROM/DVD or network depot.7 7.-------------------.root # ln -sf /opt/tao1.4. At the end.1PL2 new requested areas.. The list of software to be installed will be displayed.7 7.9 7.5. If the directory /SCINSTALL/execution_parking/ contains some files execute: . See “APPENDIX K: New Disk Request” for more info.1. If you choose depot. use and communication of its contents. Reply “R” to the following question to execute file system extension at the next reboot: File System:"/dev/vg00/lvol4" is busy.sys. not permitted without written authorization from Alcatel 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.4. 7.4. The procedure will ask where to find the software.9 7. you have to refer to /alcatel/SCDEPOT on the depot system.. If free space currently available on configured disks is not enough for NR8. enter “a”.sys..

. use and communication of its contents. 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.1PL2 software during the ISE procedure. for more information refer to “1350 Rel8.root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM . 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. 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....6 Install NR8.sys. Replace the CD_ROM with the new one when (and if) requested. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Overview Hereafter it is explained how to install NR8.sys./Install.sys.1..1PL2 software All rights reserved.. If DEPOT installation: Start the OS-KERNEL installation by entering the following command (one only line).. Start the OS-KERNEL installation by entering the following command sequence. . or type e different CD device file name if the default one is not ok. Passing on and copying of this document.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. .sh –install –force OS-KERNEL <depot host> <depot directory> ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 24/157 ...root # cd /alcatel/Install_Wizard If CD-ROM installation: Insert “SWP-NR81_ADD01” volume 1/1 medium in the CD drive.1PL2 Installation Guide” [1].4.root # ./Install...root # ..

..1PL2/Kernel.. Execute this procedure for each NMS you have predisposed the system for. Passing on and copying of this document.1PL2 NMS software from CD-Rom or from network depot..root # umount /SD_CDROM Mis en forme : Police :Gras. Start the NMS installation by entering the following command sequence.root # .root # cd /alcatel/Install_Wizard If CD-ROM installation: Insert “SWP-NR81_ADD01” volume 1/2 medium in the CD drive....sys. Verify the correct installation checking the file: /alcatel/Install_Wizard/log/Installation_OS–KERNEL_#. The procedure asks you to select the version to be installed by issuing: All rights reserved./Install. Login into the system as user root.1.sys.01PL2) 2) OS-KERNEL <Version> (<NR version>) E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed . ... not permitted without written authorization from Alcatel ====================================================================== Installation OS-KERNEL package ====================================================================== ---------------------------------------------------------------------1) OS-KERNEL 7..sys.In both cases: The installation script starts.sys. Italique Supprimé : Appendix A: Summary tables NMS Software Installation This paragraph describes how to install NR8.root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM .. use and communication of its contents.sh -install –force <NMS> -cdrom 1AA 00014 0004 (9711) A4 Where the key <NMS> has to be replaced with the NMS name ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 25/157 . Enter the following command sequence: . skipping it . Don’t worry about it.. 1. 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....2 (08.. 2..2-19..log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: . Neclect the following message: NOTE: Preparing to install .

Replace the CD_ROM with the new one when (and if) requested.1PL2 NMC (Components) software from CD-ROM or Alcatel Depot..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. 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.. If DEPOT installation: Install each NMS subject to ISE Migration entering the following command: ..01PL2) 2) <NMS> <Version> () E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed . Italique Supprimé : Appendix A: Summary tables NMC Software Installation (ETH_MEDIATOR / ISN / IOO / etc) This paragraph describes how to install NR8.root # . Passing on and copying of this document. skipping it .On the screen will appear the following question related to the CD drive: All rights reserved. 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... the 1353NM can require up to 2h and 30 minutes. Repeat steps for each NMS subject to ISE Migration Verify the correct installation checking the file: /alcatel/Install_Wizard/log/Installation_<NMS>_#..sys. The procedure asks you to select the version to be installed by issuing: ====================================================================== Installation <NMS> package ====================================================================== 1) <NMS> <Version> (08. 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”.1PL2/Kernel. or type e different CD device file name if the default one is not ok...log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: . 1AA 00014 0004 (9711) A4 Enter the following command sequence: ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 26/157 . Login into the system as user root. The time requested by activity depends by the installing NMS./Install.. Don’t worry about them.sys..root # umount /SD_CDROM Mis en forme : Police :Gras.

sys.. Verify the correct installation checking the file: /alcatel/Install_Wizard/log/Installation_<NMC>_#.root # ..sys.....sys.sys. 4..root # umount /SD_CDROM Supprimé : Table 11 Supprimé : Table 11 4.root # cd /alcatel/Install_Wizard If CD-ROM installation: All rights reserved.7 Customize OS-Kernel 1./Install. not permitted without written authorization from Alcatel Insert “SWP-NR81_ADD01” volume 1/2 medium in the CD drive..sys./Install..log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: .2-RP15 () 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 27/157 . The procedure asks you to select the version to be customized by issuing: ====================================================================== Customization OS-KERNEL package ====================================================================== ---------------------------------------------------------------------1) OS-KERNEL 7.1.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.. .1PL2/Kernel. Start the NMC installation by entering the following command sequence. Repeat step for each NMC subject to ISE Migration. Login as root user..root # .. use and communication of its contents.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.sys.. Replace the CD_ROM with the new one when (and if) requested...root # . .1. Passing on and copying of this document. Enter the following command sequence. The installation script starts. Don’t worry about it. skipping it . If DEPOT installation: Install each NMC subject to ISE Migration entering the following command: .root # cd /alcatel/Install_Wizard .. or type e different CD device file name if the default one is not ok...sys.... 2. 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./Install..root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM . 5...sh –custom OS-KERNEL 3.

. If you are migrating 1354RM execute: ..sys.sys. to my $MIN_SEMAPHORE_NUM=8182.. If GENOS is installed remove from /etc/services all the lines related to almcpa entries (ports 20001 / 20002 / 20003 / 20004 / 20005)...root # . Supprimé : Table 8 Supprimé : Table 9 Supprimé : Table 10 ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 28/157 .1PL2/Kernel/maintenance/log/KernelCustomize./apache_stop.sys.sys. What must be absolutely avoided is to customize the new client instance before its master. Passing on and copying of this document..log Do you want to execute OS-KERNEL Custom? [y|n|q] Supprimé : Table 4 Mis en forme : Police :Gras..5/classes a.pm and change the line 61 from my $MIN_SEMAPHORE_NUM=7182.sh .1PL2/Kernel/lib/lib_perl/Semaphores. “ Table 28” and “ Table 29” where “New Instance” column contains "YES”)..1.2) OS-KERNEL <Version> () All rights reserved. ...7_Master/APACHE/script/ ..root # mkdir –p /opt/JacORB2..3./tomcat_stop. Italique Supprimé : Appendix A: Summary tables 4. Not doing so can have disruptive effects on the system! You can now customize the local NMS master.root # /alcatel/8. use and communication of its contents..8 Customize Instances Subjected to ISE Warning! Always migrate any client instance in the topology after its respective master instance. Enter “ 1 [Enter]”.sys.1PL2/Kernel/script/KernelCustomize Immediately after KernelCustomize completion execute the following commands: .root # cd /usr/Systems/Global_Instance_7. 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.sh Neglect the possible message: “httpd (no pid file) not running” Verify the correct customization checking the file: /alcatel/Install_Wizard/log/Customization_OS–KERNEL_#.. subject to ISE Migration (“ Table 27”.1..1.root # ... Login into the system with graphical interface as user root (execute this procedure via GoGlobal-UX). not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed .log /alcatel/8.

d. Passing on and copying of this document. use and communication of its contents. g.. Italique Supprimé : Appendix A: Summary tables The Customize script will issues a sequence of windows depending by the specific NMS./Install.List” Figure 3 ...sys root # cd /alcatel/Install_Wizard . Select “New instance” and release the button.. with “System. Move the cursor on [Choose_One] button and press on “mouse selection button” to open the list.Instances. Start the custom process by entering: .b..Upgrade System..root # .sys. Instance. Pull down the Action menu and select “Apply & Exit”. f.. A window similar to the following should appear: 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 29/157 . not permitted without written authorization from Alcatel 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 .. List window e. 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 Mis en forme : Police :Gras.sh -custom <NMS> All rights reserved.

Note: i. use and communication of its contents. Passing on and copying of this document. Some customization procedure can issue specific sub-configuration window. Pull down the Action menu and select “Apply & Exit” The customization process takes up to 2 hours.ISE Customize Parameter Definition window. h. The log of the activity will be shown in a window like this: ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 30/157 1AA 00014 0004 (9711) A4 All rights reserved. not permitted without written authorization from Alcatel Supprimé : Table 3 Mis en forme : Police :Italique Supprimé : Appendix A: Summary tables . 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.Figure 4 . refer to specific administration guide for more info. depending by the NMS and the system performances.

2.sys root # chmod –R 777 /usr/Systems/1354RM_1-7. The custom can issue warning and error messages that have to be ignored. Login into the system as root user.4.cfg setting the “processes” keyword to 100 (3 occurrences).sh –custom <NMS> l... 4.. if finished continue with the next paragraph: .4.sys root # cd databases/dbsnml/admin/pfile .....9 ..log /alcatel/Kernel/maintenance/trace/Custom.sys. Edit db_params.sys root # cp –p db_params..1. 4.trace /alcatel/Kernel/maintenance/log/Custom..root # .4. Launch the following command if you need to customize another “new instance” or. Save database parameter file (db_params. not permitted without written authorization from Alcatel Figure 5 .log k.9/FWK/poller .sys root # chmod –R 777 /usr/Systems/1354RM_1-7.. refer to “Appendix J: Custom Warning and Error”.1. Note: j. Passing on and copying of this document.cfg.All rights reserved..orig 4..10 Export and Import of System Configuration 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 31/157 . Mis en forme : Police :Italique Supprimé : Appendix J: Custom Warning and Error Verify the correct customization of the NMS checking in the files: /alcatel/Install_Wizard/log/Customization_<NMS>_#. use and communication of its contents.9_: Nor owner WARNING: chmod: can’t change stop_poller: Nor owner 3..Upgrade Custom log window. Follow points 3 to 9 for each instance to customize.cfg) entering the following commands: ./Install.9/trcLevel Ignore warning like the following: WARNING: chmod: can’t change comet2pollingmgr_1354RM_5-7..sys root # cd /usr/Systems/1354RM_1-7...9 Preparing for 1354RM Instance Configuration If the NMS is a 1354RM: 1. Change the following files permission: .4.cfg db_params..

Perform system config import as described in section “System Configuration Import” of “APPENDIX E: DATA Export/Import”. Anglais (États-Unis) Supprimé : APPENDIX E: DATA Export/Import Mis en forme : Police :Italique Mis en forme : Police :Italique. Anglais (États-Unis) Supprimé : System Configuration Import Supprimé : APPENDIX E: DATA Export/Import Mis en forme : Police :Italique ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 32/157 . 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”. Passing on and copying of this document. use and communication of its contents.For each NMS installed and subjected to ISE migration. All rights reserved. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Supprimé : System Configuration Export Mis en forme : Police :Italique.

is the NMS instance identification number. . execute the following commands to create RM DB schema reference files: 1.9 . Remember to add new mandatory subsystems. In case of 1354BM-ETH select “New” for the TAO_Interface Repository. Repeat the procedure for each new NMS Master instance created and subjected to ISE Migration. Startup 1354RM database: . Stop 1354RM database: . Start the “System Configuration” tool by entering: $ . $ cd /usr/Systems/1354RM_1-7. not permitted without written authorization from Alcatel Perform the “System Configuration” of the new Master instances customized in “Customize Instances Subjected to ISE” 3.9/ORACLE/script/ .1PL2/Kernel/etc/SystemConfig 1354RM 1-7.. $ chmod 777 /alcatel/DEPOT/NR81PL2_RM_DB_Ref . It’s mandatory to reconfigure all processes with the mouse right button. .4. All the subsystems present in the source NMS will be automatically selected.g. Login into the system with a graphical Interface as alcatel user. Passing on and copying of this document. 6. Add EMLIM_Proxy e NMLIM_Proxy subsystems. 4.snmlrc cd ORACLE/databases/dbnml/etc start_db 3.1PL2/Kernel/etc/SystemConfig <NMS> <NMS Id>-<NMS Version> Where: <NMS> <NMS Id> <NMS Version> is the NMS product.1.... Mis en forme : Police :Italique Supprimé : Customize Instances Subjected to ISE (e. Pull down “Main” menu and select “Update Config” to start the “System Configuration”. $ $ $ $ cd /usr/Systems/1354RM_1-7. “ Table 25” in “Appendix A: Summary tables”. Verify the correct System Configuration of the NMS checking in the files: /alcatel/8.11 Configure Instances Subjected to ISE All rights reserved../. Supprimé : Table 5 Supprimé : Table 6 Mis en forme : Police :Italique Supprimé : Appendix A: Summary tables 4.4. .1PL2/Kernel/maintenance/log/SystemConfiguration_<NMS>*..9 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 33/157 . /alcatel/8.4.... is the NMS target version. $ mkdir /alcatel/DEPOT/NR81PL2_RM_DB_Ref (if you get an error execute.4.9) 5.. Login into the system as user snml 2. use and communication of its contents. insert correct values in NECOM... . In case of 1353NM first of all add Supervision_Area_# Subsystem.12 Create DB schema reference files If you are migrating a 1354RM. Get a snapshot of the database: . $ ../MIB_Contents get /alcatel/DEPOT/NR81PL2_RM_DB_Ref 1AA 00014 0004 (9711) A4 4.. as root: chmod 777 /alcatel/DEPOT and repeat the command) ... creating new databases and updating the parameters that refer to the old Network Release.log 8.4. Also verify their configuration according to the information stored in the “ Table 24”..1PL2/Kernel/env/Kernel $ /alcatel/8.1.: /alcatel/8. 7. $ cd /usr/Systems/1354RM_1-7..

1.. import. $ cd ORACLE/databases/dbnml/etc . $ mkdir /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref (if you get an error execute.. Stop 1354BMETH database: . $ chmod 777 /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref .1. Get a snapshot of the database: ... $ . the import and the conversion of the data... Anglais (États-Unis) Mis en forme : Police :Italique ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 34/157 . Login into the system as user bmml 2./MIB_Contents get /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref 4. $ stop_db If you are migrating a 1354BMETH...... as root: chmod 777 /alcatel/DEPOT and repeat the command) .sh vi UserConfiguration insert the following 2 lines: #!/bin/sh /alcatel/Kernel/bin/UserConfiguration. Passing on and copying of this document.. AS.1. .1PL2/Kernel/bin mv UserConfiguration UserConfiguration.14 Export. 4.sh $* > /dev/null & 1AA 00014 0004 (9711) A4 Mis en forme : Police :Italique.1. 3. conversion executing the following steps: 1..5 . Perform the export.. This will allow restoring the data machine by machine. $ $ $ $ cd /usr/Systems/1354BMETH_1-8.bmmlrc cd ORACLE/databases/dbnml/etc start_db All rights reserved. Import.. .. Login into the system as root user 2. If you are going to import many operators (> 50) execute this wa to save time: cd /alcatel/8.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.. Execute data export as described in section “Data Export” of “APPENDIX E: DATA Export/Import”. not permitted without written authorization from Alcatel Supprimé : Data Export Supprimé : APPENDIX E: DATA Export/Import 3.. $ stop_db 4..5 .. ...1.. and Conversion of Instances Subjected to ISE Migration Hereafter are described the steps to follow in order to execute the export. Operator and SEC on each NMS system. $ cd /usr/Systems/1354BMETH_1-8. use and communication of its contents.5/ORACLE/script/ . Startup 1354BMETH database: ... ./.. PM. execute the following commands to create BMETH DB schema reference files: 1. $ cd ORACLE/databases/dbnml/etc .. $ cd /usr/Systems/1354BMETH_1-8.

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, Anglais (États-Unis)
Supprimé : APPENDIX E: DATA Export/Import

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

6

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

Processes for 1354RM Database

ED

6

RELEASED

Optics

8DG 31466 AAAA TCZZA

36/157

4.2
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel

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.
Mis en forme : Police :Italique
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

6

RELEASED

Optics

8DG 31466 AAAATCZZA

37/157

.” if referred to a client instance.9_Master drwxrwxr-x 52 snml dba 34 Mar 21 15:41 1354RM_1 -> 34 Mar 20 09:12 1354RM_1-7.7_Master lrwxr-xr-x 1 root sys 41 Mar 19 17:30 Global_Instance-7.1. use and communication of its contents.sys.. • Kill “connnection manager” processes executing: ..1.2.7 -> /usr/Systems/Global_Instance_7..9 -> 2048 Mar 28 12:35 1354RM_1_7....4.root # scmanageswp resume “scmanageswp” require you to confirm the request with the following message: You request to resume the pending migration. Login into the system as user root without using GoGlobal-UX and start “scmanageswp” entering: ..1PL2/Kernel/bin/ActivateKernel. • Verify the correct activation of new release by entering: .root 5001 8219 1 0 Nov 20 ? 0:40 /alcatel/7.4. 1.1.7_Master 1024 Mar 22 09:22 4.sys.sys.4..1D/Kernel/bin/conmgr.9_Master lrwxr-xr-x 1 root sys /usr/Systems/1354RM_1_7.. not permitted without written authorization from Alcatel Get “conmgr. Passing on and copying of this document.sys.root # kill –9 <PIDs> • Enter the following command to activate the new kernel: ..4. Are you ready to RESUME the migration ? (y/n) ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 38/157 1AA 00014 0004 (9711) A4 .exe All rights reserved.root # /alcatel/8.9_Master lrwxr-xr-x 1 root sys 41 Mar 21 15:41 Global_Instance -> /usr/Systems/Global_Instance_7..root # ls -l /usr/Systems lrwxr-xr-x 1 root sys /usr/Systems/1354RM_1_7. Now you have to resume the scmanageswp procedure to complete the platform upgrade.4 Resume Predispose.7_Master drwxrwxrwx 21 root root Global_Instance_7.exe” and “run_conmgr” PIDs (8148 and 8219 in the example).pl Neglect the message: “ERROR: lss not running ..1..

In such a case execute: . The system will be reboot. The following message appears: Executing Shutdown-Reboot to complete the configuration.root # . before return the prompt.dat must be updated.7 Customize GoGlobal-UX Note: 1AA 00014 0004 (9711) A4 Do not execute this commands using GoGlobal-UX interface. Note: If CD installation has been specified the predispose procedure will ask to provide the CDROMs where the software is stored..sys. Passing on and copying of this document.dat 4. IMPORTANT DO NOT FORGET ! Note: The upgrade execution can take up to three hours depending by the installation method and by the server model. please wait ***** The procedure will rebuild the HP-UX™ 11i kernel. /alcatel/8.5 Upgrade the platform software according to chapter “Platform Upgrade”.1. Answer “y [Enter]” to resume the previously suspended predispose. get a valid license file and install it on /opt/Poseidon/etc/license. * The analysis phase failed for "ipb082:/". Press [Enter] to proceed. 4.2. It can also require some system reboot! Mis en forme : Police :Italique Supprimé : Platform Upgrade 4. Customize GoGlobal-UX software: …. Press [Enter] to continue.2. The following message will be shown: All rights reserved.3.1.3.6 Upgrade Software Platform Before starting the upgrade verify if the path /opt/JacORB2.1PL2 NMS.2.. ATTENTION: now to complete the configuration Shutdown-Reboot will be executed.1PL2/Kernel/env/Kernel ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 39/157 . not permitted without written authorization from Alcatel scmanageswp resume SESSION was successful. use and communication of its contents. ***** The System reboots automatically.root # rm -r /opt/JacORB2. 3. If “scmanageswp resume” procedure fails and the following (or similar) error appears in /SCINSTALL/scinstall.2. and it will install 3PP software requested by NR8. * Analysis had errors. check “Appendix N” for a possible workaround.log: ERROR: "ipb082:/": The software dependencies for 1 products or filesets cannot be resolved..5 is a normal directory (not a mount point) and has two subdirectories.5 Update Poseidon License Remember that Poseidon license.sys.

sys. when requested to confirm for PLT and SMF integration of 1354BMETH instance "under" 1354RM instance. All rights reserved.root # /alcatel/Kernel/script/UpdateNetworkConnections. not permitted without written authorization from Alcatel 4.root # SMF/tools/scheduler/script/addPlan.2..sys. sys. Choose “Actions” -> “Synchronize” -> “Synchronize NE” 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 40/157 ..9 Startup NMS applications & verify behaviour Start the NMS instances and check the system behaviour.. for any listed command name.pl -cmd PurgeAS Integrate the NMS executing: . Passing on and copying of this document....8 NMS Integration For each NMS in NR8.root # SMF/tools/br/script/addExternalOs.sys.pl –b -d . .…. e.pl –c and...root # /alcatel/8. Highlight the 1354RM instance clicking on the related icon shown in the “OSs” object area 4.g. Do you want continue ? (yes/no.root # SMF/tools/scheduler/script/addSchedJob.10 1354RM NE and alarm synchronization Perform the following steps: 1.1PL2 execute: .1PL2/Kernel/script/XTEmulatorConfigure. default=no) Enter “yes [Enter]” to proceed...sys.2. Start the TMN-OS application 3.root # cd /usr/Systems/<NMS>_<NMS Id> .root # SMF/tools/scheduler/script/addPlan. Select the nodes that you want to synchronize: Table 1. answer always no.2.. Start 1354RM user interface (browser) clicking on the related button 5.pl \ [Enter] KernelCustomize The script asks you the authorization to stop GoGlobal-UX issuing: GoGlobal 2 server will be stopped.sys... 4.sys. with the exception of 1354RM Master and 1354BMETH Master configuration.pl –b If you want to rebuild the old scheduled jobs: .. Login into the system with a graphical interface as alcatel user 2. 4...pl Answer yes to all the integration confirmations requested by the procedure. use and communication of its contents.. "PurgeAS"..

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 If 1354RM manages QB3* NEs. Highlight the 1354BM instance clicking on the related icon shown in the “OSs” object area ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 41/157 . in order to define the action to perform for 1354RM realignment. change 1354RM Run Level to 0 – Full Functionality In case of misalignment on 1354RM objects (expecially if traffic impacting) contact TEC. This procedure is mainly used as a post-migration step and has to be executed after an Audit procedure.2. use and communication of its contents. taking care of real attributes value read from NE. otherwise on selected nodes perform “Actions” -> “Configure Download” -> “Enable” 4. From RM browser select the nodes on which you want to perform the audit 5. Perform the following steps: 1.2. Login into the system with a graphical interface as alcatel user 2.12 1354BMETH align up The Align Up procedure allows to realign 1354BMETH taking care of real attributes value read from NE. Choose “Actions” -> “Consistency Audit” -> “Notify Audit” 3. Start the TMN-OS application 1AA 00014 0004 (9711) A4 3.Table 2.11 1354RM audit The Audit procedure allows to verify 1354RM alignment. Choose “Actions” -> “Configure Download” -> “Disable” 6. Open PMC and change 1354RM Run Level to 4 – Network Consistency 1. Passing on and copying of this document. 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. From PMC. Choose “Actions” -> “Synchronize” -> “Synchronize Alarm” All rights reserved. Choose “Actions” -> “Configure Download” -> “Disable” 2. 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. not permitted without written authorization from Alcatel 4. perform the following actions: 4.

3. 4. 4. Passing on and copying of this document. The selected item will be shown for confirmation.2. Repeat steps from 8 to 10 for each SWP Instances you have to remove. check you choice and confirm only if it’s correct. 6. Start 1354BMETH Construction graphical user interface clicking on the related button All rights reserved. Repeat steps from 3 to 5 for each SWP Instances you have to remove. check you choice and confirm only if it’s correct. Enter “ 3 [Enter]” for “Remove SWP” 9. Enter “6 [Enter]” to “Remove SWP Instance” 4..root # scmanageswp 3. Remove also OS-KERNEL instance. Remove also OS-KERNEL. entering “q [Enter]”. 10. The list of available instances will be shown. execute the procedure described in “APPENDIX M: 1354RM pre-OTN to OTN migration” 4. enter the instance item number you have to remove. 8. Start 1354BMETH Ethernet Management graphical user interface clicking on the related button 7. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 5.1 or NR7. 7..14 1354RM pre-OTN to OTN migration Only in case of 1354RM migration from NR7. enter the instance item number you have to remove. Login into the system as user root 2.0 or 2. then it must be re-configured after migration completion. and only if the network contains 1626LM 2. Double check it before proceeding! ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 42/157 . 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.4.2.sys.15 Remove Obsolete Data and Software 1..2.0A NEs. 12. 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. Run “scmanageswp” by entering: . use and communication of its contents. The selected item will be shown for confirmation. Go back to the main menu. The procedure will show the selection you made. The list of available SWP will be shown.13 Alarm Federation configuration If Alarm Federation was previously configured on the system. 6. 5. Enter “ a [Enter]” for “Apply” the selected choices. 11.

1D 5. remove manually the old mount point executing: 4.root# scdeletefs /alcatel/8..sys..4 7.root# scdeletefs /alcatel/7. If (and only if) you are upgrading from NR8...sys.. /alcatel/MirrorArea/ 17. /usr/Systems/ b. If (and only if) you are upgrading from NR7.4: . /home directory won’t be removed In case the running processes have some files opened on the file system you are removing.root# scdeletefs /alcatel/7...1: .sys.sys..root# scdeletefs /alcatel/7. 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 43/157 ..2_Master” is not an empty directory Do you want to kill all processes are unsing Mount Point: “/usr/Systems/Global_Instance_7. use and communication of its contents... If (and only if) you are upgrading from NR7..sys.3 6.root # scdeletefs –g swap 16.2_Master” NOTE: Mount Point: “/usr/Systems/Global_Instance_7... a message similar to the following appears on the screen: Delete Mount Point: “/usr/Systems/Global_Instance_7. Important Note: when the procedure asks for mount points removal as here indicated: All rights reserved. /alcatel/BackupArea/ c.sys.1D Do you confirm the removal ? (y/n) Reply “y [Enter]”.1.root # /alcatel/INSTALLER/etc/sw_target_removal <SNR> Where: [Enter]” to kill all of them...1. Release the exceeding swap space executing: ….2_Master” ? Press [y] for yes or [n] for no..1PL1 Remove old software references entering the following command: .1D PL2: .root# scdeletefs /alcatel/8.1.3: .0_Master /usr/Systems/1354RM_1_7. Cleanup the link structure by removing symbolic links to old instances under: a. not permitted without written authorization from Alcatel ATTENTION: the next action is NOT REVERSIBLE! If you confirm the following mount points will be removed from system: /usr/Systems/1353NM_1_7.1: .sys.1_Master /home /alcatel/7. 14. Passing on and copying of this document. In case. then press [Enter] Enter “y Reply “y” 15.13.. If (and only if) you are upgrading from NR7. Execute the removal entering “ a [Enter]” again. If (and only if) you are upgrading from NR8.1 8.

...3 ....2...3 ..root# mkdir /opt/oracle10g/old .....sys...1PL1 All rights reserved.root# swremove Oracle10g ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 44/157 .sys.3 7.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 .. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Mise en forme : Puces et numéros In case.sys.root# scdeletefs <mount point> e..2..root# mountall .sys.root# mkdir -p /opt/oracle10g/10..g.root# umount /opt/oracle10g .sys.. use and communication of its contents.0.root# cd .root# umount /opt/oracle10g/10.1 for NR8.1D PL2 and all NR7.root# bdf .7-beta-hpux11..1. Passing on and copying of this document.1D PL1.sys..11-hppa2..bck Modify the suitable line in /etc/fstab from: /dev/vg00/lvolxx /opt/oracle10g .. NR7.4 for NR7..<SNR> has to be replaced with the old Network Release installation sub-directory.1D...1PL1 for NR8.0. that has to be: 7.sys..sys.root# scdeletefs /opt/oracle10g/old .sys.. remove manually old mount points not removed by deinstallation procedures: .sys.sys.: . to: /dev/vg00/lvolxx /opt/oracle10g/old . .sys..root# cp -p /etc/fstab /etc/fstab.......2.4 8.1D for NR7.. NR7..1 8.0..0w-64bit If bdf command returns both the lines /opt/oracle10g/ /opt/oracle10g/10.root# scdeletefs /usr/local/mysql-5.3 for NR7..2 7....

7.sys root # .. 6.. Mis en forme : Police :Italique Supprimé : Appendix B: SW Packages Supprimé : Table 8 Supprimé : Table 8 Supprimé : Table 9 4. Start TMN-OS application.pl –b –d 4..sys root # /alcatel/Kernel/script/deintegration.3 All rights reserved. Repeat steps 4-6 for each NMS Master subjected to ISE migration. 4. not permitted without written authorization from Alcatel Stepped ISE Guide Lines 4. where “New Instance” column contains "YES.3 De-Activate previous OS-Kernel De-activate previous OS-Kernel executing as user root: ...3. Highlight NMS master instance by clicking on the related icon shown in the “OSs” object area.pl 1AA 00014 0004 (9711) A4 Neglect the following message: ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 45/157 .root # cd /usr/Systems/<NMS>_<NMS Id> . use and communication of its contents.3.3. Passing on and copying of this document.4.2 De-integration If the system you are upgrading is integrated by a higher level one. 8. login as root on the machine hosting the higher level system and execute: . then on “Stop System”. Logout from all user sesssions.sys..1 Shutdown running application subjected to ISE Migration. Shutdown any running application by: 1. Click on “OS” pull down on TMN-OS menu-bar.. Confirm stop command by clicking on “OK” button of “Confirm” popup window. by clicking on icon: 3. 2.. “ Table 27”. Note: It is suggested to inform all users in advance that the system will be shutdown..sys.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 . Login into the system in graphical mode as user alcatel.root # /alcatel/Kernel/bin/DeactivateKernel.. “ Table 27” and “ Table 28” (depending on your starting NR).../SMF/tools/br/script/addExternalOs. 5. Identify local NMS Master instances subjected to ISE migration referring to “Appendix B: SW Packages”.

root # ls -l /usr/Systems lrwxr-xr-x 1 root sys /usr/Systems/1354RM_1_7.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.7_Master 1024 Mar 22 09:22 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 46/157 .9 -> 2048 Mar 28 12:35 1354RM_1_7. not permitted without written authorization from Alcatel 4. use and communication of its contents. 4. Kill “connnection manager” processes executing: .7 -> /usr/Systems/Global_Instance_7. Change from KCM:4:respawn:/alcatel/<source_NR>/Kernel/etc/run_conmgr to KCM:4:respawn:/alcatel/8.exe Get “conmgr.7_Master lrwxr-xr-x 1 root sys 41 Mar 19 17:30 Global_Instance-7.Warning: DocumentRoot [<NMS_INSTANCE_DIR>/web/java/] does not exist All rights reserved.. Get “connnection manager” processes PID executing: .1D/Kernel/etc/run 0:40 /alcatel/7.pl Neglect the message: “ERROR: lss not running .sys.. Modify the line related with the “connection manager”.4..exe” and “run_conmgr” PIDs (8148 and 8219 in the example)...4 Activate NR8.9_Master drwxrwxr-x 52 snml dba 34 Mar 21 15:41 1354RM_1 -> 34 Mar 20 09:12 1354RM_1-7. Adjust the “connection manager” reference in the “/etc/inittab” file executing: c. 6.1.1PL2/Kernel/bin/ActivateKernel. Login as user root 2.1PL2/Kernel/etc/run_conmgr 3. Verify the correct activation of new release by entering: .. Passing on and copying of this document.root # /alcatel/8. Enter the following command to activate the new kernel: .1D/Kernel/bin/conmgr..” if referred to a client instance.9_Master lrwxr-xr-x 1 root sys 41 Mar 21 15:41 Global_Instance -> /usr/Systems/Global_Instance_7.sys.4. Edit the “/etc/inittab” file d.1PL2 OS-Kernel You have now to activate the new OS-kernel: 1.3.sys...root # kill –9 <PIDs> 5.1..7_Master drwxrwxrwx 21 root root Global_Instance_7.sys.4.1...1..4.9_Master lrwxr-xr-x 1 root sys /usr/Systems/1354RM_5_7..

3. In such a case execute: .3.3.5 1AA 00014 0004 (9711) A4 Upgrade the platform software according to chapter “Platform Upgrade”.dat 4. ***** The System reboots automatically. * The analysis phase failed for "ipb082:/". and it will install 3PP software requested by NR8. * Analysis had errors.. Press [Enter] to continue.4..3. Passing on and copying of this document. The following message appears: Executing Shutdown-Reboot to complete the configuration. please wait ***** The procedure will rebuild the HP-UX™ 11i kernel.root # rm -r /opt/JacORB2. All rights reserved.1PL2 NMS.. Press [Enter] to proceed.dat must be updated. The following message will be shown: scmanageswp resume SESSION was successful. If “scmanageswp resume” procedure fails and the following (or similar) error appears in /SCINSTALL/scinstall. not permitted without written authorization from Alcatel Now you have to resume the scmanageswp procedure to complete the platform upgrade.. use and communication of its contents.5 is a normal directory (not a mount point) and has two subdirectories.7 Upgrade Software Platform Before starting the upgrade verify if the path /opt/JacORB2. before return the prompt. get a valid license file and install it on /opt/Poseidon/etc/license. Login into the system as user root without using GoGlobal-UX and start “scmanageswp” entering: .1.log: ERROR: "ipb082:/": The software dependencies for 1 products or filesets cannot be resolved.root # scmanageswp resume “scmanageswp” require you to confirm the request with the following message: You request to resume the pending migration. ATTENTION: now to complete the configuration Shutdown-Reboot will be executed. Are you ready to RESUME the migration ? (y/n) 4.3.. Mis en forme : Police :Italique Supprimé : Platform Upgrade ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 47/157 . 3. 5.6 Update Poseidon License Remember that Poseidon license.sys.. check “Appendix N” for a possible workaround. 4. Note: If CD installation has been specified the predispose procedure will ask to provide the CDROMs where the software is stored.1.5 Resume Predispose. Answer “ y ” to resume the previously suspended predispose.sys. The system will be reboot.

IMPORTANT DO NOT FORGET ! All rights reserved.2 7.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.1PL2/Kernel/script/XTEmulatorConfigure.. NR7.1PL1 for NR8.sys.Instances.root # /alcatel/8..List” ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 48/157 . .1D PL1. It can also require some system reboot! 4.sys..3. Adjust software references for old client instances entering the following command as root user: .8 Customize GoGlobal-UX Note: Do not execute this commands using GoGlobal-UX interface. use and communication of its contents.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. default=no) Enter “ yes” to proceed. Customize GoGlobal-UX software: ….sys. you have now to customize these presentation instance with the new OS-Kernel./Install.root # cd /alcatel/Install_Wizard ..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). with “System.root # .root # .3 7. 4.1PL2 Where: <SNR> has to be replaced with the old Network Release installation sub-directory. NR7.3 for NR7.1D PL2 and all NR7..root # /alcatel/INSTALLER/etc/sw_nr_adjuster <SNR> 8.1 8.sys.1D..pl \ KernelCustomize The script asks you the authorization to stop GoGlobal-UX issuing: GoGlobal 2 server will be stopped.1 for NR8.. Passing on and copying of this document.sys.4 for NR7. that has to be: 7. /alcatel/8.4 8. If you have to keep old client instances to allow the communication with the machine not yet upgraded. Do you want continue ? (yes/no.1D for NR7.1PL2/Kernel/env/Kernel …..3. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Note: The upgrade execution can take up to three hours depending by the installation method and by the server model..

1 8..4 8. Instance.root # cd /usr/Systems/ . NR7. use and communication of its contents.1PL1 for NR8.1D PL1.. 2.. Then pull down the Action menu and select “Apply & Exit” 3..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..0 client instance edit the file /usr/Systems/1353NM_1_7.1D PL2 and all NR7.root # ln -s /usr/Systems/Global_Instance_7.. still in old Network Release: . and select “New instance” and release the button.1. sys..4 for NR7... then recustomize old client instances following the Release Notes of the last installed (raw-)patch.log /alcatel/Kernel/maintenance/trace/Custom. Fill in “Parameter Definition: window with the data related to the presentation of previous version.1D.3 7..root # ln -s Global_Instance_<Ver>_Master \ Global_Instance_7. sys..1D for NR7. List window 1.2 7. as specified in the “ Table 22” (see “Appendix A: Summary tables”) according the NMS you are customizing..7_Master .root # ln –s <SNR> 8.7 Supprimé : Table 3 Mis en forme : Police :Italique Supprimé : Appendix A: Summary tables 1AA 00014 0004 (9711) A4 Where: ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 49/157 . NR7.7_Master \ Global_Instance-7.1.1 for NR8. sys.3 for NR7. that has to be: 7. Login as root on remote lower level machines hosting master instances not yet upgraded. sys.1PL1 .trace /alcatel/Kernel/maintenance/log/Custom. Pull down the Action menu and select “Apply & Exit”.log After customizing NM 7..1. Verify the correct customization of the NMS checking in the files: /alcatel/Install_Wizard/log/Customization_<NMS>_#. sys.1PL2 Where <SNR> has to be replaced with the old Network Release installation sub-directory. not permitted without written authorization from Alcatel Figure 6 .Upgrade System.root # cd /alcatel/ ... Move the cursor on [Choose One] button and press on “mouse selection button” to open the list.All rights reserved. Passing on and copying of this document.

/Install. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 4.2 for NR7..6 for NR8.1 7. Login into the remote higher level system with graphical interface as user root (execute this procedure via GoGlobal-UX).3 for NR7.1PL2 execute: .1D PL1.2 7.pl –b If you want to rebuild the old scheduled jobs: .1D PL2 and all NR7. Passing on and copying of this document..1D.1.11 NMS Integration For each NMS in NR8......root # cd /usr/Systems/<NMS>_<NMS Id> .1.pl –c ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 50/157 ....root # SMF/tools/scheduler/script/addPlan..4 for NR7.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..sys. that has to be: 7..sys.sys. re-execute the System Configuration updating EML_PROXY and NML_PROXY configuration and re-integrate it! 4.1PL1 All rights reserved.pl –b -d .3..1.sys. NR7.1.. Decustom old presentation instance: .sys.. /usr/Systems/ . use and communication of its contents. NR7..3..root # SMF/tools/br/script/addExternalOs.5 for NR8.4 7. upgrade also its related client instances hosted by remote higher level systems.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.root # SMF/tools/scheduler/script/addSchedJob.sys..1.<Ver> has to be replaced with the old Network Release Global Instance version.root # ..root # cd /alcatel/Install_Wizard .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.3 7..sys.

pl -cmd PurgeAS All rights reserved. use and communication of its contents..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... 4.pl –force Then integrate the NMS executing: .sys. execute: . not permitted without written authorization from Alcatel If client instances are installed on the machine.pl Answer yes to all the integration confirmations requested by the procedure.. 4..3. start the NMS instances and check the system behaviour.14 1354RM Audit The Audit procedure allows to verify 1354RM alignment.3. with the exception of 1354RM Master and 1354BMETH Master configuration. "PurgeAS". taking care of real attributes value read from NE. Table 6. for any listed command name. Choose “Actions” -> “Synchronize” -> “Synchronize NE” Choose “Actions” -> “Synchronize” -> “Synchronize Alarm” 4...12 Startup NMS applications & Verify Behaviour Do a logout/login.and..root # /alcatel/Kernel/script/UpdateNetworkConnections. 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 4. e. sys. when requested to confirm for PLT and SMF integration of 1354BMETH instance "under" 1354RM instance.3. 1AA 00014 0004 (9711) A4 Choose “Actions” -> “Configure Download” -> “Disable” Choose “Actions” -> “Consistency Audit” -> “Notify Audit” ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 51/157 .root # /alcatel/Kernel/bin/UpdatePresentation. Passing on and copying of this document.root # SMF/tools/scheduler/script/addPlan.g.. . sys. answer always no.

ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 52/157 . perform the following actions: Table 8. change 1354RM Run Level to 0 – Full Functionality In case of misalignment on 1354RM objects (expecially if traffic impacting) contact TEC. 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. From PMC. 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.Table 7. Table 9. 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. then it must be re-configured after migration completion.16 Alarm Federation configuration If Alarm Federation was previously configured on the system. Highlight the 1354BM instance clicking on the related icon shown in the “OSs” object area 4. Open PMC and change 1354RM Run Level to 4 – Network Consistency 1. otherwise on selected nodes perform “Actions” -> “Configure Download” -> “Enable” 4. Perform the following steps: 1. From RM browser select the nodes on which you want to perform the audit Choose “Actions” -> “Configure Download” -> “Disable” All rights reserved. Select one node a time and choose “Actions” -> “Consistency Audit” -> “Global” Table 11.3. 4. use and communication of its contents. 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.3. Start 1354BMETH Ethernet Management graphical user interface clicking on the related button 7. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Table 10.15 1354BMETH align up The Align Up procedure allows to realign 1354BMETH taking care of real attributes value read from NE. Start 1354BMETH Construction graphical user interface clicking on the related button 5. Login into the system with a graphical interface as alcatel user 2. 6. Start the TMN-OS application 3. in order to define the action to perform for 1354RM realignment. This procedure is mainly used as a post-migration step and has to be executed after an Audit procedure. Passing on and copying of this document.

. /home directory won’t be removed ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 53/157 . Passing on and copying of this document. Enter “ 3 [Enter]” for “Remove SWP” The list of available SWP will be shown. not permitted without written authorization from Alcatel Only in case of 1354RM migration from NR7.0_Master /usr/Systems/1354RM_1_7. execute the procedure described in “APPENDIX M: 1354RM pre-OTN to OTN migration” 4. and only if the network contains 1626LM 2. Login into the system as user root Run “scmanageswp” by entering: .0A NEs.1_Master /home /alcatel/7. Enter “ a [Enter]” for “Apply” the selected choices.4. Repeat steps from 3 to 5 for each SWP Instances you have to remove. enter the instance item number you have to remove... The procedure will show the selection you made. use and communication of its contents. 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. entering “q [Enter]”.3. The selected item will be shown for confirmation. Remove also OS-KERNEL instance.3.root # scmanageswp Enter “6 [Enter]” to “Remove SWP Instance” The list of available instances will be shown. Remove also OS-KERNEL.1D Do you confirm the removal ? (y/n) 1AA 00014 0004 (9711) A4 Reply “y [Enter]”. check you choice and confirm only if it’s correct. check you choice and confirm only if it’s correct.sys.18 Remove Obsolete Data and Software Warning! In case of stepped ISE the old software is still necessary for the system to work properly.1 or NR7. The selected item will be shown for confirmation. Repeat steps from 8 to 10 for each SWP Instances you have to remove. 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.17 1354RM pre-OTN to OTN migration All rights reserved.0 or 2. to free the disk space no more useful. Go back to the main menu. Double check it before proceeding! Execute the removal entering “ a [Enter]” again.3. enter the instance item number you have to remove.

.2_Master” is not an empty directory Do you want to kill all processes are unsing Mount Point: “/usr/Systems/Global_Instance_7...1 for NR8....1PL1 for NR8.1D PL1... that has to be: 7..3 If (and only if) you are upgrading from NR7. Mise en forme : Puces et numéros ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 54/157 . then press [Enter] Enter “y Reply “y” Release the exceeding swap space executing: ….root# scdeletefs /alcatel/8.1D PL2: .sys. a message similar to the following appears on the screen: Delete Mount Point: “/usr/Systems/Global_Instance_7.: .root # scdeletefs –g swap Cleanup the link structure by removing symbolic links to old instances under: /usr/Systems/ /alcatel/BackupArea/ /alcatel/MirrorArea/ 3.root# scdeletefs /alcatel/7.root# scdeletefs /alcatel/7.root# scdeletefs /alcatel/8..2_Master” NOTE: Mount Point: “/usr/Systems/Global_Instance_7.1D for NR7.3 7.sys. remove manually the old mount point executing: If (and only if) you are upgrading from NR7.1: ....3 for NR7...sys.1PL1 Remove old software references entering the following command: ..root# scdeletefs /usr/local/mysql-5.1.4: .1. Passing on and copying of this document..1D PL2 and all NR7.sys.7-beta-hpux11. not permitted without written authorization from Alcatel [Enter]” to kill all of them.2_Master” ? Press [y] for yes or [n] for no.sys. use and communication of its contents. remove manually old mount points not removed by deinstallation procedures: . In case.sys.root# scdeletefs /alcatel/7.4 for NR7.In case the running processes have some files opened on the file system you are removing.0w-64bit 1AA 00014 0004 (9711) A4 All rights reserved.1PL1 In case.1 8.root# scdeletefs <mount point> e..root # /alcatel/INSTALLER/etc/sw_target_removal <SNR> Where: <SNR> has to be replaced with the old Network Release installation sub-directory.1 If (and only if) you are upgrading from NR8.3: .sys..1D If (and only if) you are upgrading from NR7..4 If (and only if) you are upgrading from NR8.2 7. NR7.1: ..4 8.sys.1.g.1D.1.sys. NR7...11-hppa2..

If bdf command returns both the lines /opt/oracle10g/
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel

/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

6

RELEASED

Optics

8DG 31466 AAAATCZZA

55/157

5

MIGRATION WITH SPARE SYSTEM Overview
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

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 preparation’s steps for the ISE described in this chapter.

ED

6

RELEASED

Optics

8DG 31466 AAAA TCZZA

56/157

5.1
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel

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”.
Mis en forme : Police :Italique
Supprimé : APPENDIX L: Retrieve HP-UX System Information Supprimé : Identify the current software

5.1.2 Install hp-ux on target system

Mis en forme : Police :Italique, Anglais (États-Unis) Mis en forme : Police :Italique
Supprimé : Appendix A: Summary tables

NOTE:

Because the target system must have the same network configuration of source one, the target system can’t 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

6

RELEASED

Optics

8DG 31466 AAAATCZZA

57/157

4. Enter “1” at “SWP MAIN MENU” in order to choose “Predispose new SWP” 4. Start “scmanageswp” tool entering: . Predispose for: OS-Kernel 7. Refer to paragraph “Install NMS SWPDESC. Login into the system as user root. the item corresponding to the target version of the SWP you want to upgrade. Enter. and for all the NMS SWP involved in the migration. Enter “4” at the “SWP MAIN MENU” to get in “Create a new INSTANCE” section menu Create NMS instance. for more information refer to “1350 Rel8. Login as user root. 7. for each choice. Anglais (États-Unis) Supprimé : Install NMS SWPDESC. b. 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. Warning! To avoid future machine reboot predispose all NMSs now. Mis en forme : Police :Italique.7. the “item ID” correspondent to the choice previously done. in particular 1353NM 7. 5. Now it will appear the list of the software packages (with related version) that can be installed.5 SWP and instances. 2.g. use and communication of its contents. Enter “2” at “Predispose new SWP” menu in order to use the installed NMS description. It is not allowed to perform this activity in multiple steps. Passing on and copying of this document.sys root # scmanageswp 3. To predispose the system for the new NMS software you have to: 1. Enter “q” twice to get back to “SWP MAIN MENU” 8.1PL2 SWPDESC and Install Wizard Upgrade a.. 1.1PL2 software.3 Install & Predispose the system for the NR8. hereafter): Create new INSTANCE Item SWP Name SWP Version ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 58/157 . Choose from the list.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. It’s now requested to create the instance for SWP above predispose. You have now to predispose for Alcatel NMS SW of target machine.1PL2 Installation Guide” [1].5. and Install Wizard” in the APPENDIX D for the details related to this upgrade procedure. All rights reserved. 6. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 NR8. Note: The installation from Network Depot can be performed only after the depot set-up.1. and Install Wizard Predispose the NR8.1... Note: It is mandatory that the predispose and the creation of the new instance is performed in one shot for the entire system.

7 Enter 'q' to Quit.sys. Insert the instance number as described in the column “instance number” shown in the table” Table 21 “ 5./Install.5 7. use and communication of its contents. The procedure will ask where to find the software. b. Insert “SWP-NR81_ADD01” volume 1/1 medium in the CD drive.sys.All rights reserved. Passing on and copying of this document..1PL2.root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM .1PL2 new requested areas. See “APPENDIX K: New Disk Request” for more info... you have to refer to /alcatel/SCDEPOT on the depot system.4. 6. procedure will ask for new disks. but with the software version foreseen for NR8. or type e different CD device file name if the default one is not ok.1. Predispose for: OS-KERNEL 7.root # cd /alcatel/Install_Wizard If CD-ROM installation: a. . In this activity you have to keep the same instance ID of source system. Enter “q” twice to get back to “SWP MAIN MENU” and there enter “a” twice to execute.sys. Select the “Item ID” that has the value “Instance dimension” equal to the one present in the table“ Table 21”.. If you choose depot.. Mis en forme : Police :Italique Supprimé : 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..1.1. Login as root user with a Unix shell (without graphical interface: do not execute this procedure via GoGlobal-UX) 2. Start the OS-KERNEL installation by entering the following command sequence. At the end of software installation. ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 59/157 . Enter “n” for “multi-volume group”. the shutdown-reboot will be automatically executed.. 'd' to Display again or the Item Number : 2. column “Instance Size/Type”.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. Enter the following command: .4. Supprimé : APPENDIX K: New Disk Request Supprimé : Table 2 Supprimé : Table 2 Mis en forme : Police :Italique 5. 3. not permitted without written authorization from Alcatel ---1 2 3 4 --------------1353NM 1353NM 1354RM OS_KERNEL ----------7.0 7...9 7. If free space currently available on configured disks is not enough for NR8. You can choose between CD-ROM/DVD or network depot.4 Install the application software on target system Install the same Alcatel NMS present on the source hp server.root # .7 and all NMS Master instances and for all needed NMS client instances. 4. previously written into “Appendix A: Summary tables”.

Replace the CD_ROM with the new one when (and if) requested. Don’t worry about it./Install. e.1PL2/Kernel...root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM . 1.sys...root # .sys..root # cd /alcatel/Install_Wizard If CD-ROM installation: d...log /alcatel/Install_Wizard/log/Customization_OS–KERNEL_#... Login into the system as user root. Execute this procedure for each NMS.sh OS-KERNEL <depot host> <depot directory> In both cases: 1.1PL2 NMS software from CD-Rom or from network depot. All rights reserved. . Passing on and copying of this document.. The installation script starts. 2. Insert “SWP-NR81_ADD01” volume 1/2 medium in the CD drive.root # . Enter “yes” to the following question in order to start Go-Global UX customization (if requested): GoGlobal 2 server will be stopped. .root # umount /SD_CDROM NMS Software Installation This paragraph describes how to install NR8...sys. 2.. Start the NMS installation by entering the following command sequence.sys. 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. Start the OS-KERNEL installation by entering the following command..sys..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 6 RELEASED Optics 8DG 31466 AAAA TCZZA 60/157 ./Install. Do you want continue ? (yes/no. not permitted without written authorization from Alcatel If DEPOT installation: c.log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: .. skipping it . Enter the following command sequence: . use and communication of its contents... default=no) 4. Verify the correct installation and customization checking the files: /alcatel/Install_Wizard/log/Installation_OS–KERNEL_#. 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.

Login into the system as user root. use and communication of its contents. g.4 application.. Passing on and copying of this document. 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. or type e different CD device file name if the default one is not ok.4… () E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed .Please enter the Device Name of source media [c0t0d0]: Reply [Enter] to confirm. Verify the correct installation checking the file: /alcatel/Install_Wizard/log/Installation_<NMS>_#. 2.sys. If DEPOT installation: 1...1PL2 NMC (Components) software from CD-ROM or Alcatel Depot. skipping it . The time requested by activity depends by the installing NMS. Insert “SWP-NR81_ADD01” volume 1/2 medium in the CD drive. Select the item ID according the 1353NM 7.sys.root # umount /SD_CDROM NMC Software Installation (ETH_MEDIATOR / ISN / IOO / etc) This paragraph describes how to install NR8... Enter the following command sequence: .root # cd /alcatel/Install_Wizard If CD-ROM installation: 1AA 00014 0004 (9711) A4 f.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.. 1.sys../Install. not permitted without written authorization from Alcatel Replace the CD_ROM with the new one when (and if) requested. Don’t worry about them.0... All rights reserved...log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: . Install each NMS subject to ISE Migration entering the following command: . ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 61/157 ..root # . approximately 15 minutes for 1354RM.15-P09 () 2) 1353NM 7.1PL2/Kernel. Start the NMC installation by entering the following command sequence.

/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 6 RELEASED Optics 8DG 31466 AAAA TCZZA 62/157 All rights reserved. 8....1..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.... skipping it .. 2.root # .root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM .. Login into the system with graphical interface as user root (execute this procedure via GoGlobal-UX). use and communication of its contents. Replace the CD_ROM with the new one when (and if) requested. The installation script starts.5 Customize the application software on target system Warning! Always migrate any client instance in the tolology after its respective master instance.root # . Verify the correct installation checking the file: /alcatel/Install_Wizard/log/Installation_<NMC>_#. Don’t worry about it. not permitted without written authorization from Alcatel .root # .. 7..sys. 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..sys.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..log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: .sys root # cd /alcatel/Install_Wizard . Repeat step for each NMC subject to ISE Migration. Install each NMC subject to ISE Migration entering the following command: .. 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.sys..sh -install <NMC> -cdrom Supprimé : Table 11 Supprimé : Table 11 ...sys. Passing on and copying of this document.1PL2/Kernel./Install./Install. or type e different CD device file name if the default one is not ok...sys. Start the custom process by entering: .root # umount /SD_CDROM 5. What must be absolutely avoided is to customize the new client instance before its master. If DEPOT installation: 2.

Move the cursor on [Choose_One] button and press on “mouse selection button” to open the list. 1. Instance.0. List window 2. 1. Select the item ID according to the related Master instance version. 2..====================================================================== 1) 1353NM 7. Passing on and copying of this document. A window similar to the following should appear: 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 63/157 .4… () All rights reserved.Upgrade System. Pull down the Action menu and select “Apply & Exit”. Reply “y” to the following question to execute the <NMS> customization: NOTE: Do you want to execute <NMS> Custom? [y|n|q] The Customize script will issues a sequence of windows depending by the specific NMS.15-P09 () 2) 1353NM 7. Select “New instance” and release the button..Instances. with “System.List”” Figure 7 . not permitted without written authorization from Alcatel E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed . use and communication of its contents.

not permitted without written authorization from Alcatel Supprimé : Table 3 Mis en forme : Police :Italique Supprimé : Appendix A: Summary tables .Customize Parameter Definition window. refer to specific administration guide for more info. Note: Some customization procedure can issue specific sub-configuration window. The log of the activity will be shown in a window like this: ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 64/157 1AA 00014 0004 (9711) A4 All rights reserved. depending by the NMS and the system performances. Passing on and copying of this document. Pull down the Action menu and select “Apply & Exit” The customization process takes up to 2 hours. 4. 3.Figure 8 . 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. use and communication of its contents.

Note: The custom can issue warning and error messages that have to be ignored. not permitted without written authorization from Alcatel Figure 9 ..All rights reserved..trace /alcatel/Kernel/maintenance/log/Custom.log /alcatel/Kernel/maintenance/trace/Custom. Passing on and copying of this document. Follow points 2 to 9 for each instance to customize. Mis en forme : Police :Italique Supprimé : Appendix J: Custom Warning and Error 5. refer to “Appendix J: Custom Warning and Error”. Verify the correct customization of the NMS checking in the files: /alcatel/Install_Wizard/log/Customization_<NMS>_#.root # .Upgrade Custom log window. 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 65/157 .sh –custom <NMS> 7. if finished continue with the next paragraph: ./Install.. use and communication of its contents. Launch the following command if you need to customize another “new instance” or.log 6.sys.

Passing on and copying of this document.1PL2 software 10. Customize the application software on target system At this point continue the migration applying the Migration with Spare System Common Procedure. the procedure has to be repeated starting from this step. Install & predispose the system for the NR8. 2. The things that will be done are: 6. 7. Install the application software on target system 11. use and communication of its contents. HP-UX™ operating system information. Alcatel NMS information. It allows preparing the target system ready in advance. 5. Anglais (États-Unis) 5. it suggested to connect it to a stand alone LAN HUB.2 Install hp-ux on target system Mis en forme : Police :Italique Supprimé : Appendix A: Summary tables Warning! Do not install old Os-Conf and upgrade to the latest one. There are two kind of information: 1. To be able to properly install the target system. Install straight the latest OsConf. retrieve them following “APPENDIX L: Retrieve HP-UX System Information”. HP-UX® operating system has to be installed on the target system using the same configuration provided for the source one. in terms of NMS type and instance present on the source system. 1AA 00014 0004 (9711) A4 Detailed instruction for HP-UX® installation are available on 1350 Rel8.1 and fill in the table in “Appendix A: Summary tables”.1 Obtain source system variables. NOTE: From this point and onwards.2.1PL2 Installation Guide [1]. Install & predispose for old presentation instance 9.5. not permitted without written authorization from Alcatel This section describes the first phase specific to Stepped Migration with spare system. NOTE: Because the target system must have the same network configuration of source one. Obtain source system variables.2. both these data have to be provided at installation time. Install hp-ux on target system 8. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 66/157 . The most important are: hostname and IP address of lan0. no changes to hp-ux configuration are allowed the entire system has been completely migrated to the target machine. it can be done weeks before the migration. In case any modification have to be performed on hp-ux. Mis en forme : Police :Italique Supprimé : APPENDIX L: Retrieve HP-UX System Information Supprimé : Identify the current software Mis en forme : Police :Italique.2 Stepped Migration with Spare System Overview All rights reserved. the target system can’t be connected to the LAN where the source is connected to. you must retrieve some information for the source one.1. to retrieve them follow the “Identify the current software” paragraph 6.

root # rcp –p <depot host>:<directory>/Install_Wizard_CMD-Rx.. Therefore..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.x.x. ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 67/157 ..sys. 1AA 00014 0004 (9711) A4 1.x-Px sh ..sys.root .When the installation is completed. recover the routing configuration: 4...root If DEPOT installation: Retrieve the software from depot machine: ....2.root ../Install_Wizard_CMD-Rx. If CD-ROM installation: Insert the SWP–NRxxx volume 1/x in the CD or DVD driver and mount it: . . IP configuration for LAB card different than LAN0. use and communication of its contents.....sdpkg .sys..x. Passing on and copying of this document....sys.. Install previous NR version SWPDESC & Install_Wizard Note: Install_Wizard uses /alcatel/DEPOT as a temporary area to store temporary files needed for installation.x. All rights reserved.x-Px ..sys.root # mkdir –p /alcatel/DEPOT ..sys..root .root # cd /alcatel/DEPOT .x-Px ..... . Gated configuration 5.root # swinstall –s /alcatel/DEPOT/SWPDESCVxxxx... 6....x-Px Predispose the system for previous version software Predispose for previous version 1353NM SWP Master and for all needed 1353NM client SWP instances../Install_Wizard-Rx. not permitted without written authorization from Alcatel 5..sys./Install_Wizard_CMD-Rx.sdpkg \* .sys.x./Install_Wizard-Rx.. 1.sys.root .root # rcp –p <depot host>:<directory>/SWPDESCVxxxx..sdpkg \ * cd /SD_CDROM sh .root . you have now to install and predispose them.sys.root # rcp –p <depot host>:<directory>/Install_Wizard-Rx. 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. Routing configuration.sys. # # # # # # # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM swinstall –s /SD_CDROM/SWPDESCVxxxx....root .x-Px cd / umount /SD_CDROM Install software description by entering hereafter command sequence: ...sys.x..root # sh ...sys..sys.. Login into the system as user root.sys.x-Px .root # sh . Login into the system as user root.

------1 1353NM 7. 1. You will get as output the list of the “instance” dimension. Highlight in the table “ Table 21” belonging to “Appendix A: Summary tables” all previous version packages that must be manage in NR8. Start “scmanageswp” tool entering: All rights reserved. Choose from the list. 7.. 5. Repeat steps 2-5 for all needed previous version Client SWP instaces. Enter “n” for “multi-volume group”. and enter the “item ID” corresponding to the previous version SWP. Item ---1 2 3 4 5 6 7 8 List of available INSTANCE dimension for SWP: 1353NM 7. Enter “q” to go back to “Create a new INSTANCE” menu.--------------. 6.----------. Enter “q” twice to get back to “SWP MAIN MENU” 7.sys root # scmanageswp 3. Insert the instance number as described in the column “NMS instance number” shown in the table” Table 21 “ 6. highlighted at point 1. 'd' to Display again or the Item Number : 2.1PL2. Enter “1” at “Create a new INSTANCE” according to one of the items highlighted at point 3. Passing on and copying of this document. On the screen you should have the “Create a new INSTANCE” section menu that shows you the previous version item (e.0 INSTANCE Dimension INSTANCE Description -------------------. Enter “4” at the “SWP MAIN MENU” to get in “Create a new INSTANCE” section menu Predispose old client instances It’s now requested to create an instance for all needed old client instances. Italique Supprimé : Appendix A: Summary tables Enter 'q' to Quit. Now it will appear the list of the software packages (with related version) that can be installed. column “Instance Size/Type”. 'd' to Display again or the Item Number : 4. 1AA 00014 0004 (9711) A4 Supprimé : Table 2 Supprimé : Table 2 8..g.. hereafter): Create new INSTANCE Item SWP Name SWP Version Session ---.-------------------------------------------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 Mis en forme : Police :Gras.2. use and communication of its contents. not permitted without written authorization from Alcatel Supprimé : Table 2 .0 NEW Enter 'q' to Quit. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 68/157 . 5. Enter “1” at “SWP MAIN MENU” in order to choose “Predispose new SWP” 4. Select from the list the “Item ID” that has the value “Instance dimension” equal to the one present in the table“ Table 21”. Enter “2” at “Predispose new SWP” menu in order to use the installed NMS description.

/Install. All rights reserved.. or type e different CD device file name if the default one is not ok. The time requested by install activity can require up to 2h and 30 minutes. Passing on and copying of this document. i. not permitted without written authorization from Alcatel The procedure will ask where to find the software.. by executing: 1. Mis en forme : Police :Italique Supprimé : APPENDIX K: New Disk Request Install previous version software...log If CD-ROM installation: 1AA 00014 0004 (9711) A4 Dismount the CD-ROM and remove the medium from the drive: ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 69/157 . You can choose between CD-ROM/DVD or network depot.root # . Start the previous version software installation by entering the following command sequence: . Replace the CD_ROM with the new one when (and if) requested. procedure will ask for new disks.9.. you have to refer to /alcatel/SCDEPOT on the depot system. Reply “R” to the following question to execute file system extension at the next reboot: File System:”/dev/vg00/lvol5” is busy. Verify the correct installation checking the file: /alcatel/Install_Wizard/log/Installation_<NMS>_#. [A] for Abort.sys. The installation script starts. Insert ““SWP-NRxxx” volume 1/x medium in the CD drive. 2.sh – install <NMS> <depot host> <depot directory> In both cases: 1. Start the previous version software installation by entering the following command sequence..then press [Enter] At the end of software installation. . Then procedure start executing the requested predispositions. use and communication of its contents.. Install only previous version software without customizing any instance. Login into the system as user root.sys.sys. If free space currently available on configured disks is not enough for NR7. If you choose depot.root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM .root # .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.root # cd /alcatel/Install_Wizard If CD-ROM installation: h.4 new requested areas. the shutdown-reboot will be automatically executed. Sometime messages like the following will be issued: 2. [R] for Reboot. Press: [T] for Try again. check process with pid(s): …………./Install.. See “APPENDIX K: New Disk Request” for more info...sys. If DEPOT installation: 3.. 10.. Enter “q” twice to get back to “SWP MAIN MENU” and there enter “a” twice to execute. Enter the following command sequence: .

...,sys,root # umount /SD_CDROM
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel

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.
Mis en forme : Police :Italique, Anglais (États-Unis)
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

6

RELEASED

Optics

8DG 31466 AAAA TCZZA

70/157

...,sys root # scmanageswp •
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization from Alcatel

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.
It’s 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

Mis en forme : Police :Italique

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

Mis en forme : Police :Italique
Supprimé : Appendix A: Summary tables

ED

6

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

...,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 ... Don’t 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_OS–KERNEL_#.log /alcatel/Install_Wizard/log/Customization_OS–KERNEL_#.log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive:

ED

6

RELEASED

Optics

8DG 31466 AAAA TCZZA

72/157

. Install each NMS subject to ISE Migration entering the following command: ..sys.... use and communication of its contents.root # umount /SD_CDROM All rights reserved..root # cd /alcatel/Install_Wizard If CD-ROM installation: m. Execute this procedure for each NMS.. Insert “SWP-NR81_ADD01” volume 1/2 medium in the CD drive... hereafter): ====================================================================== Installation <NMS> package ====================================================================== 1) 1353NM 7. The time requested by activity depends by the installing NMS..1PL2 NMS software from CD-Rom or from network depot.root # . Enter the following command sequence: . Login into the system as user root...g. skipping it ...sys. 3./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.sys. 1AA 00014 0004 (9711) A4 Don’t worry about them.root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM .sys.sys.4… () E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed .root # . approximately 15 minutes for 1354RM.. approximately 75 minutes for 1353NM. Passing on and copying of this document.0. . not permitted without written authorization from Alcatel NMS Software Installation This paragraph describes how to install NR8.1PL2 application.. ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 73/157 .. or type e different CD device file name if the default one is not ok. n... If DEPOT installation: 4. Start the NMS installation by entering the following command sequence.1PL2/Kernel. Select the item ID according to NR8. Replace the CD_ROM with the new one when (and if) requested./Install. 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..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.15-P09 () 2) 1353NM 7.

..root # .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./Install. not permitted without written authorization from Alcatel Supprimé : Table 11 Supprimé : Table 11 1AA 00014 0004 (9711) A4 /alcatel/Install_Wizard/log/Installation_<NMS>_#.sys..1PL2/Kernel. or type e different CD device file name if the default one is not ok...sys. use and communication of its contents.. skipping it .4..... Repeat step for each NMC subject to ISE Migration.sys.sys.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. Insert “SWP-NR81_ADD01” volume 1/2 medium in the CD drive..root # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM . Don’t worry about it... ... Verify the correct installation checking the file: All rights reserved.. Start the NMC installation by entering the following command sequence. 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.root # .sys. If DEPOT installation: 5./Install. Install each NMC subject to ISE Migration entering the following command: .1PL2 NMC (Components) software from CD-ROM or Alcatel Depot. p..log If CD-ROM installation: Dismount the CD-ROM and remove the medium from the drive: ..root # umount /SD_CDROM NMC Software Installation (ETH_MEDIATOR / ISN / IOO / etc) This paragraph describes how to install NR8.. Replace the CD_ROM with the new one when (and if) requested. Enter the following command sequence: . Login into the system as user root.root # umount /SD_CDROM ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 74/157 ..sys. 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: . Passing on and copying of this document.root # cd /alcatel/Install_Wizard If CD-ROM installation: o.

9.1D PL2 and all NR7..1PL2 Where: <SNR> has to be replaced with the Network Release installation sub-directory..Instances...15-P09 () 2) 1353NM 7. Select the item ID according to the related old master instance version. Passing on and copying of this document.sh -custom <NMS> The procedure could asks you to select the version to be installed by issuing (e.1D.g.1PL1 8.2.4 8.6 Customize the application software on target system All rights reserved...3 7.. hereafter): ====================================================================== Installation <NMS> package ====================================================================== 1) 1353NM 7..1PL1 for NR7. use and communication of its contents. Reply “y” to the following question to execute the <NMS> customization: NOTE: Do you want to execute <NMS> Custom? [y|n|q] The Customize script will issues a sequence of windows depending by the specific NMS. Not doing so can have disruptive effects on the system! Now you have to customize all the NMS Master instances..sys root # cd /alcatel/Install_Wizard .sys. What must be absolutely avoided is to customize the new client instance before its master. and all necessary old client instances. with “System. NR7./Install. that has to be: 7.1 8.4… () E) Exit ---------------------------------------------------------------------NOTE: Select the product version to be managed .2 for NR7.3 for NR7. not permitted without written authorization from Alcatel Warning! Always migrate any client instance in the tolology after its respective master instance.root # .sys.. Adjust software references for old client instances entering the following command as root user: Login into the system as user root and execute: .0. Login into the system with graphical interface as user root (execute this procedure via GoGlobal-UX). Start the custom process by entering: . NR7.4 for NR8..root # /alcatel/Install_Wizard/etc/sw_nr_adjuster <SNR> 8.5. 1.1D 7.1 for NR8.1D PL1.List”” 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 75/157 .

Pull down the Action menu and select “Apply & Exit”. not permitted without written authorization from Alcatel Supprimé : Table 3 Mis en forme : Police :Italique Supprimé : Appendix A: Summary tables . ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 76/157 All rights reserved. Passing on and copying of this document. Instance. use and communication of its contents.Figure 10 .Customize Parameter Definition window. 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. List window 2. 4. 1AA 00014 0004 (9711) A4 5. A window similar to the following should appear: Figure 11 . 3. Select “New instance” and release the button. Move the cursor on [Choose_One] button and press on “mouse selection button” to open the list.Upgrade System.

log After customizing NM 7. use and communication of its contents.log /alcatel/Kernel/maintenance/trace/Custom. refer to “Appendix J: Custom Warning and Error”. Mis en forme : Police :Italique Supprimé : Appendix J: Custom Warning and Error 7. Note: The custom can issue warning and error messages that have to be ignored. Verify the correct customization of the NMS checking in the files: /alcatel/Install_Wizard/log/Customization_<NMS>_#.0_Presentation/eml/usmshdata/script/run_atmusm and change the line 11 from $CORBAPORT="5013" to $CORBAPORT="5012" 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 77/157 . refer to specific administration guide for more info.0 client instance edit the file /usr/Systems/1353NM_1_7. 6.Note: Some customization procedure can issue specific sub-configuration window. Passing on and copying of this document.Upgrade Custom log window. depending by the NMS and the system performances. not permitted without written authorization from Alcatel The customization process takes up to 2 hours. The log of the activity will be shown in a window like this: Figure 12 . Pull down the Action menu and select “Apply & Exit” All rights reserved.trace /alcatel/Kernel/maintenance/log/Custom.

Passing on and copying of this document. It allows exporting/importing configuration and data and swap to target systems.. execute the following commands to create RM DB schema reference files: Login into the system as user snml Startup 1354RM database: ... use and communication of its contents. 2. $ cd /usr/Systems/1354RM_1/ORACLE/script/ . .3.. $ $ $ $ cd /usr/Systems/1354RM_1-7. $ ...5. ./MIB_Contents get /alcatel/DEPOT/NR81PL2_RM_DB_Ref Stop 1354RM database: 1AA 00014 0004 (9711) A4 . Verify the correct System Configuration of the NMS checking in the files: /alcatel/8.9 . The things that will be done are: 8. System Swap 5.. Create DB schema reference files 10.1PL2/Kernel/maintenance/log/SystemConfiguration_<NMS>*.snmlrc cd ORACLE/databases/dbnml/etc start_db Get a snapshot of the database: . $ chmod 777 /alcatel/DEPOT/NR81PL2_RM_DB_Ref . Start the “System Configuration” tool from TMN-OSs window.. Install migration tools 11. Mis en forme : Police :Italique Supprimé : Customize the application software on target system 5. NMS Master System Configuration 9./.log 4. Repeat the procedure for each new NMS Master instance created and subjected to Migration. $ mkdir /alcatel/DEPOT/NR81PL2_RM_DB_Ref (if you get an error execute. 3..2 Create DB schema reference files If you are migrating a 1354RM.3 Migration with Spare System Common Procedure All rights reserved.4. $ cd ORACLE/databases/dbnml/etc ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 78/157 . not permitted without written authorization from Alcatel This section describes the phase common to both One Shot and Stepped Migration with Spare System. Login into the system with a graphical Interface as alcatel user.. ... Data Export from Source and Import to Target System 12..4. $ cd /usr/Systems/1354RM_1-7..1 NMS Master System Configuration Perform the “System Configuration” of the Master instances customized in “Customize the application software on target system” 1..3.9 . Data Conversion 13.. as root: chmod 777 /alcatel/DEPOT e repeat the command) .... ..

Supprimé : Install Migration Tools Supprimé : APPENDIX E: DATA Export/Import 5... ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 79/157 .. $ stop_db If you are upgrading a 1354BMETH.. . $ cd /usr/Systems/1354BMETH_1-8. not permitted without written authorization from Alcatel Login into the system as user bmml Startup 1354BMETH database: ...3....sys.3 Install migration tools In order to export System Configuration and data from source machine and import then on target machine.1. In case any modification have to be performed on the network configuration.. . the procedure has to be repeated starting from this step. no changes to the network are allowed the entire system has been completely migrated to the target machine.. $ stop_db 5. execute the following commands to create BMETH DB schema reference files: All rights reserved.3... $ .1.. Passing on and copying of this document. $ chmod 777 /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref ......5 .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.5/ORACLE/script/ .root # cd / ../MIB_Contents get /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref Stop 1354BMETH database: ..sys. $ mkdir /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref (if you get an error execute...sys.5 .... perform the export and import of Data executing the following steps: ˆ On both machines.. $ cd /usr/Systems/1354BMETH_1-8... $ cd ORACLE/databases/dbnml/etc ... $ $ $ $ cd /usr/Systems/1354BMETH_1-8.root # scextendfs /alcatel/ExpTmp <size> Note: to check in advance the needed disk space perform the following command: . Mis en forme : Police :Italique For each NMS installed and subjected to migration.. .. source and target./.1.4 Data Export from Source and Import to Target System Mis en forme : Police :Italique. . predispose a temporary file system for Data Export: . you have to install migration tools on both machines. following instructions of paragraph “Install Migration Tools” in “APPENDIX E: DATA Export/Import". Anglais (États-Unis) NOTE: From this point and onwards. as root: chmod 777 /alcatel/DEPOT e repeat the command) . use and communication of its contents.bmmlrc cd ORACLE/databases/dbnml/etc start_db Get a snapshot of the database: ..

.sys. copy data from tape..1PL2 5. 1AA 00014 0004 (9711) A4 7. Swap source system with the target NR8. Supprimé : Data Export Mis en forme : Police :Italique..root # cd /alcatel .root # tar tvf /dev/rmt/0m ˆ On target machine: b..1PL2 master systems..3. We are going to do the following things in this order: 3.root # tar xf /dev/rmt/0m c.... Perform data import as described in section “Data Import” of “APPENDIX E: DATA Export/Import”.sys. a.root # tar cf /dev/rmt/0m . Anglais (États-Unis) Supprimé : Data Import Mis en forme : Police :Italique 5.sys. copy the entire contents of /alcatel/ExpTmp file system on to tape device. Mis en forme : Police :Italique Supprimé : APPENDIX F: 1353NM Data Conversion Mis en forme : Police :Italique Supprimé : APPENDIX G: 1354RM Data Conversion Mis en forme : Police :Italique Supprimé : APPENDIX H: 1354BMETH Data Conversion 5.sys.. by entering the following commands: . ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 80/157 .. Register all NMS with the other ones. use and communication of its contents.ˆ On source machine: All rights reserved.. not permitted without written authorization from Alcatel a..1PL2 correctly works. Check the tape contents entering: . 4.root # cd /alcatel . During this chapter we will have a period of no surveillance while the target system is starting. Passing on and copying of this document. switching off the source system and replacing it with the target one..5 Data Conversion Supprimé : APPENDIX E: DATA Export/Import If the NMS is a 1353NM: Perform data conversion has described in “APPENDIX F: 1353NM Data Conversion”. If the NMS is a 1354BM-ETH: Perform data conversion has described in “APPENDIX H: 1354BM-ETH Data Conversion”.. execute data export as described in section “Data Export of “APPENDIX E: DATA Export/Import”.3. Swap preparation. Verify that the target NR8..sys.6 System Swap In this phase we swap the network management systems. by entering the following commands: . If the NMS is a 1354RM: Perform data conversion has described in “APPENDIX G: 1354RM Data Conversion”. Start NR8. Anglais (États-Unis) Mis en forme : Police :Italique Supprimé : APPENDIX E: DATA Export/Import Mis en forme : Police :Italique. 6./ExpTmp a.

. otherwise proceed with next point./Install./SMF/tools/br/script/addExternalOs...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.root # cd /alcatel/Install_Wizard .. 2. Shutdown Alcatel NMS on target system..1PL2 The NMS system swap consists of replacing the two servers: 5.sys.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 .. Review the license files for Poseidon and GOGlobal-UX.sys..root # cd /usr/Systems/<NMS>_<NMS Id> . not permitted without written authorization from Alcatel Before proceed with swap you have to be sure that all system setups are correct for the operating environment.sys.Swap preparation All rights reserved.root # .sys.. use and communication of its contents.. 1. the most relevant data that has to be recover now are related to the DNS and license. 6.. If the system you are going to swap is integrated by a higher level one..sys.conf if it was present on source. Restore the DNS configuration file resolv. reexecute the System Configuration updating EML_PROXY and NML_PROXY configuration and ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 81/157 . login as root on the machine hosting the higher level system and execute: .. 3. Swap source system with the target NR8. Passing on and copying of this document.root # /alcatel/Kernel/script/deintegration.root # ..sys... Ask all operators to disconnect from the source system... If you are doing a one-shot migration jump directly to point 4.pl –b –d Decustom old presentation instance: .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: ..

Verify the connectivity with the DNS server (when it is present).sys.1 8.7_Master \ Global_Instance-7.. execute: .3 7.7_Master . that has to be: 7. d.2 for NR7. If the system you are going to swap integrates a lower level one still in old Network Release.4 for NR7.root # ln -s /usr/Systems/Global_Instance_7.root # cd /alcatel/ ..1D PL1.3 for NR7.1...1D PL2 and all NR7. Verify the connectivity pinging all the other NMS servers (if any).. Verify the LAN connectivity: a.1 for NR8.1PL1 8.. Verify the connectivity with the license servers (if there is other ones).3 for NR7. sys.1D. that has to be: 7.. sys.1.pl ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 82/157 .5 for NR8.6 for NR8. sys..root # /alcatel/Kernel/script/UpdateNetworkConnections. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 7.1...1..7 Where: <Ver> has to be replaced with the old Network Release Global Instance version.3 7. c.2 7.1 7.. NMS Integration If client instances are installed on the machine. login as root on the machine hosting the lower level system not yet upgraded and execute: .sys.1D for NR7.. 10.2 7. NR7.root # /alcatel/Kernel/bin/UpdatePresentation.. 9. Passing on and copying of this document. NR7..1D PL1.1.1PL2 Where <SNR> has to be replaced with the old Network Release installation sub-directory.root # cd /usr/Systems/ . use and communication of its contents.1...1PL1 for NR8.1D.4 7. NR7. sys.1D PL2 and all NR7.root # ln –s <SNR> 8. NR7. Verify the connectivity with the default gateway.re-integrate it! All rights reserved. sys..4 8..1. b. Connect all LAN connection of target system.1.. Disconnect all LAN connection of source system..pl –force Then integrate the NMS executing: .root # ln -s Global_Instance_<Ver>_Master \ Global_Instance_7.4 for NR7.1PL1 .

Choose “Actions” -> “Synchronize” -> “Synchronize NE” Table 13. with the exception of 1354RM Master and 1354BMETH Master configuration. Select one node a time and choose “Actions” -> “Consistency Audit” -> “Global” 1AA 00014 0004 (9711) A4 Table 20. Open PMC and change 1354RM Run Level to 4 – Network Consistency 3. Passing on and copying of this document. 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. Choose “Actions” -> “Configure Download” -> “Disable” Table 15. perform the following actions: Table 17. when requested to confirm for PLT and SMF integration of 1354BMETH instance "under" 1354RM instance.Answer yes to all the integration confirmations requested by the procedure.1PL2 NMS applications & Verify Do a logout/login. Choose “Actions” -> “Synchronize” -> “Synchronize Alarm” 1354RM Audit The Audit procedure allows to verify 1354RM alignment. From RM browser select the nodes on which you want to perform the audit Table 18. not permitted without written authorization from Alcatel Startup NR 8. Choose “Actions” -> “Configure Download” -> “Disable” Table 19. 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. Select the related NEs and search for “Not aligned objects” and “Not aligned objects (traffic impacting)” ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 83/157 . 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” -> “Consistency Audit” -> “Notify Audit” Table 16. answer always no. taking care of real attributes value read from NE. All rights reserved. use and communication of its contents. start the NMS instances and check the system behaviour.

change 1354RM Run Level to 0 – Full Functionality In case of misalignment on 1354RM objects (expecially if traffic impacting) contact TEC. This procedure is mainly used as a post-migration step and has to be executed after an Audit procedure.0 or 2. Perform the following steps: 1.The panels show the objects whose value is not aligned between NEs and 1354RM All rights reserved. From PMC.3. then it must be re-configured after migration completion. execute the procedure described in “APPENDIX M: 1354RM pre-OTN to OTN migration” ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 84/157 . 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. Highlight the 1354BM instance clicking on the related icon shown in the “OSs” object area 4. 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. use and communication of its contents. Alarm Federation configuration If Alarm Federation was previously configured on the system. Start the TMN-OS application 3. Login into the system with a graphical interface as alcatel user 2. 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. Passing on and copying of this document. Start 1354BMETH Ethernet Management graphical user interface clicking on the related button 7. 6. and only if the network contains 1626LM 2. Start 1354BMETH Construction graphical user interface clicking on the related button 5. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 4.0A NEs. 1354RM pre-OTN to OTN migration Only in case of 1354RM migration from NR7.1 or NR7.

use and communication of its contents.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. 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. Passing on and copying of this document. 6.6 All rights reserved. not permitted without written authorization from Alcatel 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. Identify the current software 2. Identify the target software 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 85/157 .

Software Packages and Data Instances Mis en forme : Police :Gras. 5. Lunch “scmanageswp” tool by entering: .1 7.0 7.2 Total number of SWP on this system is: 3 [Enter] to continue. All rights reserved.6.1.sys.1. 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 86/157 . Italique Supprimé : Appendix A: Summary tables Total number of INSTANCE on this system is: 3 [Enter] to continue.root # scmanageswp 3. To do that you have to: 1. an output like the following will be provided: SWP predisposed on system SWP Name --------------1353NM 1354RM OS_KERNEL SWP Version Session ----------. 3.1.1 7. Press “2” in order to show “View predisposed SWP”. Fill the table “Upgrade/ISE .------7.1 Identify the current software Overview The first important point is to clearly identify the software installed. Identify application software level.. View created SWP INSTANCE. Do the following: 1.. INSTANCE created on system SWP Name --------------1353NM 1354RM OS_KERNEL SWP Version ----------7. Italique. 4.---1353NM_IM_Medium 1354RM_IM_Medium OSKERNEL Mis en forme : Police :Gras... columns “SWP Name” and “SWP Version” with the values displayed. Italique.2 INSTANCE Number --------------7 2 1 INSTANCE Dimension Ses. Passing on and copying of this document. Login the system as user root and open a terminal. An output similar to the following will appear. Anglais (États-Unis) Mis en forme : Police :Gras. Anglais (États-Unis) Supprimé : Upgrade/ISE . use and communication of its contents. 2. Select [5]. Note: the information shown depends from the specific configuration installed on your machine.0 7. 2.. 4. Check the 1359HA Configuration. 6.Software Packages and Data Instances” you can find in the “Appendix A: Summary tables”. Retrieve NMS configuration data for each instance. Identify the NMS predisposed. ------------------. Press [Enter]. not permitted without written authorization from Alcatel Identify the NMS predisposed You need first to check for which NMS the machine has been predisposed. then “SWP MAIN MENU” appears again.

. Italique Supprimé : Appendix A: Summary tables Check the 1359HA Configuration Alcatel TMN foreseen two High Availability product: 1359HA OS-Resilience and 1359HA OS-Cluster. Here after the procedure to retrieve the relevant data: 1. Italique Supprimé : Appendix A: Summary tables Figure 13 . select “Apply & Exit” to activate your choice.Note: the information shown depends from the specific configuration installed on your machine. to go back to “SWP MAIN MENU” and “e” to exit the procedure. to close the window without start any action. 2. section “configuration tables”. press the mouse selection button.Prerequisite System Instances List Window 3. Move the pointer on “Choose_one” button.sys. The upgrade procedure depends by this software. use and communication of its contents. Italique Supprimé : Appendix A: Summary tables 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 87/157 . 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.NMS Instance Information” you can find in the “Appendix A: Summary tables”. 8.. 7. Mis en forme : Police :Gras. Login the system as root with graphical interface. please refer to the specific administration guide. Anglais (États-Unis) Mis en forme : Police :Gras. Italique. Anglais (États-Unis) Mis en forme : Police :Gras. Italique.Software Packages and Data Instances” you can find in the “Appendix A: Summary tables”. from the “Action” pull down menu. with the corresponding information displayed. Start Kernel customize script by entering . 4. Italique. Click on “Action” pull down menu. Ignore the error message shown on the terminal window. Passing on and copying of this document. Anglais (États-Unis) Supprimé : Upgrade/ISE NMS Instance Information Mis en forme : Police :Gras. not permitted without written authorization from Alcatel Mis en forme : Police :Gras. Anglais (États-Unis) Supprimé : Upgrade/ISE Software Packages and Data Instances 8. Retrieve NMS instance configuration data It is now requested to save the NMS instance configurations since the migration/upgrade process does not keep them. Italique. Italique.root # /alcatel/Kernel/script/Custom The following window will be shown on the screen: Mis en forme : Police :Gras. columns “Instance Number” and “Instance Size”. Press [Enter]. Mis en forme : Police :Gras.. if one of them is present. Anglais (États-Unis) Supprimé : Upgrade/ISE Software Packages and Data Instances Mis en forme : Police :Gras.Software Packages and Data Instances” of “Appendix A: Summary tables”. 6. Select “Close”. All rights reserved. 7. Fill the table “Upgrade/ISE . Repeat actions from 2 to 7 for each instance registered in “Upgrade/ISE . Fill the table “Upgrade/ISE .

Italique ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 88/157 . not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Login the system with a graphical interface as user “alcatel”. Start the TMN-OS application. Hereafter it is explained how to identify any NMS component version and verify when the NMS upgrade prerequisite are met. use and communication of its contents. Italique. 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”. Anglais (États-Unis) Supprimé : Upgradeable NMS software Supprimé : Appendix B: SW Packages Mis en forme : Police :Gras..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. Passing on and copying of this document. Mis en forme : Police :Gras. by clicking on icon: Highlight interesting NMS instance by clicking on the related icon shown in the “OSs” object area. ‰ ‰ ‰ ‰ ‰ All rights reserved.

Bill of material To correctly identify the distribution kits needed to perform the upgrade/migration please refer to the table …. use and communication of its contents. 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 89/157 .2 Identify the target software All rights reserved. Passing on and copying of this document.1.6. not permitted without written authorization from Alcatel Overview Hereafter are described the steps necessary to correctly identify the software to be installed.

Hereafter the instruction to perform these checks: Compute the required space. If the free space is higher please skip the next section. you have to verify the amount of “free” space available the disks. Check left available space on in use disks. Check if the amount of “free” physical extends is higher than the required one you computed in the previous section of this chapter. Launch the following command: . To compute the amount of space requested to carry out this activity please refer to “APPENDIX C: Required Disk Space”. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 90/157 1AA 00014 0004 (9711) A4 . To know the free space currently available do the following: Login the system as user root.2 Check Hardware requirements All rights reserved.6.. Check unused disks. This value corresponds to the amount of free Physical Extents (PE). Passing on and copying of this document. the upgrade method chosen. To be sure to be able complete the upgrade.. Disk Requirements The target software uses more space on disk with respect the current one.sys.root # scextendfs -i Do not “Press [Enter} to continue…” and take note of the value of FreePE. use and communication of its contents. Compute the Required Space The “free” disk space required depends on the software currently installed.. not permitted without written authorization from Alcatel Overview The upgrade/migration requires some hardware requirements are met to be able to carry out the entire process. moreover the upgrade process requires an extra temporary space requirement. Italique 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. This paragraph describes the checks that have to be performed. Mis en forme : Police :Gras. the NMS installed.

Check Available Unused Disk Units All rights reserved. and also the SCSI disk chain can be relevant (see “1350 Installation guide” [1] paragraph “OPERATING SYSTEM Installation” paragraph)..2... the upgrade requires adding a double hard disk amount to the configuration.0 _(free)_ ______ ________ c5t8d0 8680 0/6/0/0.9.2. 4. not permitted without written authorization from Alcatel If you don’t have enough space on disks (see previous section) to perform the requested update activities you should verify if some unused disks are available: 1. 3. Note: If you have mirror protection.0.0 __Data__ _Copy_ vg00 c5t9d0 8680 0/6/0/0. 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.0 Alt_Boot _Copy_ vg00 c4t0d0 8680 0/4/0/0. 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 91/157 ..0 __Data__ _Main_ vg00 c4t1d0 8680 0/4/0/0...1.0 _(free)_ ______ ________ ______________________________________________________________________ Press [Enter] to continue.root # scextendfs -i Press [Enter} to continue. Login the system as user root. Add the Mega bytes of the disk to the space left on the current volume group configuration. You should get an output similar to the following: Disks Selection ______________________________________________________________________ Device MByte Hardware Path Usage Type VolGroup ______________________________________________________________________ c1t2d0 8680 0/0/1/1. use and communication of its contents. Passing on and copying of this document. 2.0 Pri_Boot _Main_ vg00 c2t2d0 8680 0/0/2/0.sys. and look at the “Mbyte” column to know the disk size (bold underlined in the output example).8. Launch the following command: .

Passing on and copying of this document.6. use and communication of its contents. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Poseidon License Configuration for ISE purposes Please note that there is significant difference between NR7.1PL2 . Therefore when using ISE Migration approach it’s necessary to generate and adapt license.dat file accordingly. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 92/157 .2 PL2 license to compare with NR8.3 Check Software requirements All rights reserved.1D/7.

the following question will be issued: File System:”/dev/vg00/lvol5” is busy. then press[Enter] Reply “R” to execute file system extension at the next reboot: ---- 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 93/157 . use and communication of its contents. and enlarge them when needed.sys.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. Press: [T] for Try again. the proposed default is usually correct. Passing on and copying of this document.root # /SCINSTALL/etc/scupgrade 4. check process with pid(s): …………. 3.. Enter ’q’ to Quit or the CD device [def=/dev/dsk/c2t2d0]: b.DVD/CDRom 2 – DEPOT q .Depot selection for LAYERED Products installation Enter 'q' to Quit or the Depot absolute path name: 6. If any enlarged file system is in use.. not permitted without written authorization from Alcatel 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. [A] for Abort. The procedure will check the file systems free space.1PL2 software. [R] for Reboot.quit Insert choice and press [Enter]: 5. Note: The installation from Network Depot can be performed only after the depot set-up...LAYERED PRODUCTS Repository ------------1 . 7..7 All rights reserved. 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: --.1. Note: The OS-Conf upgrade must be executed without using GoGlobal-UX. Enter “1” to choose the CDROM or “2” to choose the DEPOT and consequently follow the related section: --------------------------------------------------------OS-Conf 7. For CD/DVD you have to provide driver file name.1 P08 Upgrade Procedure --------------.root # cd / .. for more information refer the “1350 Rel8.sys. Start the upgrade procedure by entering: . Next question depends by chosen repository: a.1PL2 Installation Guide” [1].

log ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 94/157 1AA 00014 0004 (9711) A4 All rights reserved. and installation will start automatically. Check for any error during the installation’s process: .. Login as user root 8. After the reboot the file system will be enlarged.. Resilience ec.sys.) Do you want continue ? .root # more /SCINSTALL/scinstall.ATTENTION -----------------------------Upgrade OS-Conf install product(s) and/or Patch(es) System could automaticaly reboot All Application must be stopped (example: RM. Passing on and copying of this document..Press [y] for yes or [n] for no. then press [Enter] In this case you must stop all the activities and reply with “y”. NM... 7. not permitted without written authorization from Alcatel ----------------------. use and communication of its contents.

Software Packages and Data Instances Use this table to insert the information concerning the “instance configuration”. not permitted without written authorization from Alcatel APPENDIX A: SUMMARY TABLES Overview This appendix summarises all table that must be useful to store the information requested during the migration/upgrade process. Configuration tables Use this table to insert the information about the software packages for which the machine has been predisposed. use and communication of its contents. Passing on and copying of this document.8 All rights reserved. You should print this appendix and use it when requested inside the document. “scmanageswp” Information SWP Name OS-KERNEL SWP Version NMS Instance Number Instance Size/Type 1 OSKERNEL Table 21. Upgrade/ISE . 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 95/157 . for each instance to be upgrade/migrated.

use and communication of its contents.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. Passing on and copying of this document. Upgrade/ISE . not permitted without written authorization from Alcatel NMS Instance NMS Instance .NMS Instance Information ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 96/157 1AA 00014 0004 (9711) A4 All rights reserved.

4. use and communication of its contents.3.6-P09 1354RM 7. not permitted without written authorization from Alcatel Install Wizard Version for NR7.3-2-P9 1354BM 7.3.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. Passing on and copying of this document.1. NR7.0.Network Management Subsystem All rights reserved.5-P2RP4 OS-KERNEL 1353NM 1354RM 1354BMETH Table 23.4 OS-KERNEL 7.2-P13 1353NM 7. 1354RM Process Configuration 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 97/157 .

not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Optics 6 RELEASED 8DG 31466 AAAA TCZZA 98/157 . Passing on and copying of this document.ED 1353NM Process Configuration Table 25. use and communication of its contents. 1353NM Process Configuration All rights reserved.

1.1.5 OSK-ENGINE 7. Table 26. Upgradeable NMS software 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 99/157 .1 RP2.6 OSK-ENGINE 7.80 7.1.1.1.2 PL2 OS-Kernel 7.2 Patch RP08.1.7 OSK-ENGINE 7. Software Component Network Release 7.2 Patch P08 OSK-ENGINE 7.13 7.1 OSK-ENGINE 7.42 N.1 Patch RP02.2 Patch P08 OSK-ENGINE 7.1.1 RP2.1.0.1 RP2. 7. Upgradeable NMS The table hereafter summarises the versions of Alcatel NMS that are supported.1 Patch P01 OSK-ENGINE 7.1T PL1 OS-Kernel 7.1 Patch RP02.1.3 Network Release 7.3.A.1 Patch P02 OSK-ENGINE 7.2 Patch RP09.1D/7.1 OSK-ENGINE 7.1.2 Patch RP09.A.A.2 OSK-ENGINE 7.8 Network Release 7.9 All rights reserved.1.1 OSK-ENGINE 7.3 OS-Kernel 7.14 7.2 OS-Kernel 1353NM 1354RM 1354BMETH 1355VPN? 1354BMPR 7.1 RP2.1.4 OSK-ENGINE 7.2 OSK-ENGINE 7.1.1.15 7.1.1.0.5 7. Passing on and copying of this document.1.1.2 Patch P01 OSK-ENGINE 7. use and communication of its contents.1.1 P14 7.2 OSK-ENGINE 7.1.1 RP2.1 P14 N.1.1 OSK-ENGINE 7.0.2 OSK-ENGINE 7.2 Patch RP08. not permitted without written authorization from Alcatel APPENDIX B: SW PACKAGES Overview This appendix provides an overview on the SW configuration needed to perform the upgrade/migration.1.2 Patch RP09.1.3.1.0.1 7.1 RP2.1.1.3 OSK-ENGINE 7. N.2 Patch P09 OSK-ENGINE 7.

1 (7.5 P2) Conversion N.3.2 P13) 7.1 .2 (7.3-2) 7.1.4 NMS Versions All rights reserved.0 (7.0.3 (7.1. Version between brackets is the real product version. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 The versions shown in the following table must be read this way: 1. YES YES YES New Instance YES YES YES YES Table 29.4 Versions Data Conversion N.4(7.3 (7. 2.1.0.3-2) YES YES YES Table 27.1.0.1 any P) 7.3 (7.4 Versions Data Conversion N.4 (7.0.4.3.2 P13) 7.1 .1D/7.3.1.3.2 Versions 7.A.5 P1) NR7.A.0 (7.4 Software Component NR7.1 (7.0 (7.1.3 Versions 7.1T Versions NR7.2 any P) 7.6 P9) 7.4.5 P2) YES YES YES YES NO Table 28.80) 7.1.3-2) 7.4 ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 100/157 .1 (7.3.3.3. NMS Versions from NR7.1 P12) 7.3 (7.4 (7.0.3 (7.4.4 Versions 7. NMS Version from NR 7.1 (7. NMS Version from NR7.3 (7.3 (7.NR7. YES YES YES NO New Instance OS-Kernel 1353NM 1354RM 1354BMETH 7.4 Software Component OS-Kernel 1353NM 1354RM 1354BMETH NR7.1.12 any P ) 7.2 P13) 7. Passing on and copying of this document.3 to NR7.4(7.15 any P) 7.3 (7.2 any P) 7.A.6 P9) 7.6 P9) 7.2 to NR 7.1 (7.1.3 (7.4 (7.1 to NR 7.42) 7. Version out of brackets is the one that have to be provided for predisposal.5 P2) 7.3.1 any P) 7.1 P14) NR7.14 any P) 7.0.0.1.1.1D/7. use and communication of its contents.1.1 (7. YES YES New Instance OS-Kernel 1353NM 1354RM 7. Software Component NR 7.

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. Passing on and copying of this document.NMC keys list All rights reserved. use and communication of its contents. NMS Specific Administration Users 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 101/157 . not permitted without written authorization from Alcatel 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.

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.1 PL2 ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 102/157 . N. Passing on and copying of this document.A. N. Depot Package Size 1390 3210 100 285 41 1250 105 3 15 42 Table 32.A. use and communication of its contents. and depot packages.10 APPENDIX C: REQUIRED DISK SPACE All rights reserved. Software Size 3600 7500 1120 1120 100 1320 1000 10 N.A.A.A. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 The following table shows the disk space requested for swap. The value are specified in M bytes. Disk requirements for NMS Software for NR8. N. program installation.

A.A. use and communication of its contents.A. 9000 9000 9000 6000 9000 5000 9000 3000 Presentation Swap N. 2000 3500 3500 3500 12500 1500 3500 200 Data N.All rights reserved.A. Passing on and copying of this document. not permitted without written authorization from Alcatel NMS Master Small Swap Data 200 3000 3000 3000 2700 3500 1000 3000 600 Master Medium Swap N.A. Disk requirements for NMS Software for NR8. 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. 250 2000 2000 3000 2000 300 2000 400(*) Data N.1 PL2 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 103/157 . 3000 7500 7500 3500 21000 2500 7500 500 Data N. 5000 5000 5000 4000 5000 2000 5000 1500 Master Large Swap N.A.

sys.root # mount –o rr /dev/dsk/<cdrom device file> /SD_CDROM In case of HP9000 PA-RISC system: .. OSC-3PP and SWPDESC Login into the system as user root and remove the installed software description and OS-Conf. All rights reserved...sys... the OS-Conf engine and the Install Wizard tool..root # swinstall –s /SD_CDROM/OS-ConfUX<version>.. and Install Wizard Note: Install_Wizard uses /alcatel/DEPOT as a temporary area to store temporary files needed for installation..sd OS-CONF OSC-3PP-UXIA Dismount the CD by entering the following command: .sys.root # swinstall –s /SD_CDROM/OS-Conf<version>.sd OS-CONF OSC-3PP In case of HP ITANIUM system: . use and communication of its contents. ......sys. OS-Conf and Install Wizard Upgrade Overview This appendix explains the procedure to upgrade NMS Software Description (SWPDESC).sys..sys.root # swinstall –s <depot host>:<depot dir> OS-CONF OSC-3PP In case of HP Integrity ITANIUM system: ... 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 6 RELEASED Optics 8DG 31466 AAAA TCZZA 104/157 .11 APPENDIX D: NMS SWPDESC.root # swinstall –s <depot host>:<depot dir> OS-CONF OSC-3PP-UXIA Install NMS SWPDESC.root # swremove OS-CONF OSC-3PP SWPDESC In case of HP ITANIUM system: ...root # umount /SD_CDROM If DEPOT installation: Install OS-Conf by entering: In case of HP9000 PA-RISC system: . Passing on and copying of this document.. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Remove Current OS-Conf....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... In case of HP9000 PA-RISC system: .sys.

./Install_Wizard-R<version> ..sys.root ..If CD-ROM installation: Replace the CD in the drive and install new software description by entering hereafter command sequence: All rights reserved...sys.sdpkg \* cd /SD_CDROM sh .. the last command will terminate with error..root # scupdate_swpdesc all all replace Note: in case of installation from scratch....root # swinstall –s /alcatel/DEPOT/SWPDESC_V<version>./Install_Wizard-R<version> sh .sys.root .sys..root ....sys...root .sys.sys.sys. and similar.sys...root .sys..4 ERROR: Not installed descriptor file for 1353NM 7...sys.root . not permitted without written authorization from Alcatel .sys. ERROR: Not installed descriptor file for OS_KERNEL 7.sdpkg .sys....root .root If DEPOT installation: # # # # # # # scmountcd /dev/dsk/<cdrom device file> /SD_CDROM swinstall –s /SD_CDROM/SWPDESCV<version>.. Note: neglect the following errors..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>/SWPDESCV<version>...sys.sys. ignore the error and continue the installation.root .sdpkg \* ./Install_Wizard_CMD-R<version> cd / umount /SD_CDROM Retrieve the software from depot machine: ..sys..1. use and communication of its contents.root ./Install_Wizard_CMD-R<version> In both cases execute: . Install new software description by entering hereafter command sequence: .0 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 105/157 .... Passing on and copying of this document..... rcp –p <depot host>:<directory>/Install_Wizard_CMD-R<version> ..root # sh ........root # sh . if present.root .....root .

. Export data from then leaving version instance workspace.sys... Importing data into the coming version instance workspace All rights reserved. 3.root # /tmp/migration_tools/Install Don’t worry of the following message: rm: /alcatel/MGT/* non-existent ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 106/157 . Hereafter the steps described in this appendix: 1..root # swinstall -s /alcatel/DEPOT/MGT_R3036. Install Migration tools 2.gz –x allow_incompatible=true –x reinstall=true \* . Export system configuration of the leaving version instance. Passing on and copying of this document. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Install Migration Tools Retrieve the Migration Tools MGT_R3036. 5.sys..sdpkg. use and communication of its contents. 4.gz (cksum & size: 3672562568 122880) and install them executing: Login into the system as user root Install the MGT tools (one only line): .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. Import system configuration into the coming version instance.sdpkg..

1D.. NR7.1.. Passing on and copying of this document. Enter /alcatel/ExpTmp/<NMS>_<NMS Id> into WORK_AREA parameter.root # mkdir /alcatel/ExpTmp/<NMS>_<NMS Id> . Then choose Actions -> Apply & Exit 1AA 00014 0004 (9711) A4 4..sys. NR7.log ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 107/157 . 7.root # G_ExpMigData The following window is displayed: Figure 14 ...sys. Define the source Network Release entering: .3. Launch the Export GUI: .root # export KERNEL_RELEASE=<NR Version> Where: < NR Version > is the Network Release Source version: 7. Select the NMS instance from INST_ID list. Verify that the Export of the system config has been correctly executed checking the log file /tmp/ExpMigData....2. 8. Select “ON” value for KEEP_SYSCONF parameter.sys.. Select “none” value for GROUPS parameter.1D PL1. Select “OFF” value for MIGR_CFG parameter..1PL1 2.sys.System Configuration Export All rights reserved.4.1 for NR8.root # cd / .4 for NR7. use and communication of its contents.1D PL2 and all NR7.Export GUI window 3. 8.1D for NR7.1PL1 for NR8.3 for NR7. not permitted without written authorization from Alcatel This paragraph describes how to export the system configuration of a NMS Master in an archive file: 1.. 7..

root # export KERNEL_RELEASE=8...gz that has to be used during import procedure.sys.... Verify that /alcatel/ExpTmp/<NMS>_<NMS Id> directory contains an archive file in the format: <NMS>_<NMS Id>-<NMS Version>_expdata-<data_type>..sys. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 108/157 . not permitted without written authorization from Alcatel 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 # G_ImpMigData The following window is displayed: Figure 15 .tar.. 1AA 00014 0004 (9711) A4 Mis en forme : Police :Italique. use and communication of its contents.root # cd / .. All rights reserved.sys.Import GUI window Select the target NMS instance from INST_ID list...root # mkdir /alcatel/ExpTmp/<NMS>_<NMS Id> . Enter /alcatel/ExpTmp/<NMS>_<NMS Id> into WORK_AREA parameter... Passing on and copying of this document.5.1PL2 Launch the Import GUI: . Anglais (États-Unis) Supprimé : System Configuration Export Select “none” value for GROUPS parameter. Enter the full path name of the archive created with Export procedure in ARCHIVE_NAME parameter (point 5 of System Configuration Export).

root # export KERNEL_RELEASE=<NR Version> Where: < NR Version > is the Network Release Source version: 7.1PL1 Only if you are going to export RM data from NR7..3 7.. Select “ON” value for KEEP_SYSCONF parameter.. NR7. “Network”: can be used for NM. use and communication of its contents.4 or NR8.root # cd / ..3 for NR7.. Passing on and copying of this document.1D. All rights reserved. is the NMS source version. to # use mysql .1PL1 for NR8. Data Export Note: Before execute the data export procedure.sys.root # update_DG <NMS>_<NMS Id>-<NMS Version> Where: <NMS Version> <NMS Id> <NMS Version> Launch the Export GUI: . For GROUPS parameter select one of the following values: 1AA 00014 0004 (9711) A4 is the NMS product. NR7..log and files in /alcatel/ExpTmp/<NMS>_<NMS Id>/MigrDataRestoring/Log directory.. is the NMS instance identification number.. RM and BMETH and exports NEs data for NM.Export GUI window).1D PL2 and all NR7. Oracle database for RM and BMETH ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 109/157 . archive the AS current alarms.2 7. Select the NMS instance from INST_ID list.1 execute the following W/A: edit the file /usr/Systems/1354RM_1/PMDS_DB/script/backupDB. not permitted without written authorization from Alcatel Then choose Actions -> Apply & Exit Verify that the Import of the system config has been correctly executed checking the log file /tmp/ImpMigData.root # G_ExpMigData The Export GUI window is displayed (see Figure 17 ..pl and change the line 29 from use mysql . Update DataGroups.1 8...1D PL1.4 for NR7..sys.root # mkdir /alcatel/ExpTmp/<NMS>_<NMS Id> .sys. This paragraph describes how to export the data of a NMS Master in an archive file: Define the source Network Release entering: .1D for NR7.Select “OFF” value for MIGR_CFG parameter.sys.sys.1 for NR8.4 8. Enter /alcatel/ExpTmp/<NMS>_<NMS Id> into WORK_AREA parameter....cfg file: .

Then choose Actions -> Apply & Exit Neglect the following messages.root # chmod a-s /opt/oracle10g/10.log /usr/Systems/1353NM_1-7..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.log: EXP-00091: Exporting questionable statistics.sys. like in this example: -rwsr-s--x 1 oracle oinstall 78336 Apr 7 2008 sqlplus unset it with the command: .3/bin/sqlplus./PMDS_DB/Kernel/conf/MIGR.0.. if present: in file NE_DB_backup./RM_DB/Kernel/conf/MIGR.log and files in /alcatel/ExpTmp/<NMS>_<NMS Id>/MigrDataRepository/Log directory. If the UID bit is set.2..sys.1354RM_17.0.4 file!! WARNING: restore invoked on a not-existing .“PM”: can be used only for NM and exports MySQL database and PM data All rights reserved. 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.0/SMF/script/axdbread[45]: axremsh: not found in export_db.3/bin/sqlplus ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 110/157 . 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.gz that has to be used during import procedure. Restore DataGroups files: .cfg. Select “OFF” value for KEEP_SYSCONF parameter. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 “Network_and_PM”: can be used only for NM and exports NEs data.1354RM_1-7. RM and BMETH and exports current and archived alarms “any” : can be used for NM.. MySQL database and PM data “Alarms”: can be used for NM. use and communication of its contents.2.root # update_DG <NMS>_<NMS Id>-<NMS Version> –restore Ignore warnings like the following: WARNING: restore invoked on a not-existing .cfg... Neglect the following messages. Passing on and copying of this document.tar. Verify that /alcatel/ExpTmp/<NMS>_<NMS Id> directory contains a file in the format: <NMS>_<NMS Id>-<NMS Version>_expdata-<data_type>.

not permitted without written authorization from Alcatel oinstall 78336 Apr 7 2008 sqlplus Define the target Network Release entering: . use and communication of its contents.: for 1354RM is 7.sys.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 .. Then choose Actions -> Apply & Exit Neglect the following messages..root # G_ImpMigData The Import GUI window is displayed (see Figure 15 .sys. Select the target NMS instance from INST_ID list..root # update_DG <NMS>_<NMS Id>-<NMS Version> Where: <NMS> <NMS Id> <NMS Version> Launch the Import GUI: ...root # mkdir /alcatel/ExpTmp/<NMS>_<NMS Id> . Enter the full path name of the archive created with Export procedure in ARCHIVE_NAME parameter (point 0 of Data Export). is the NMS instance identification number... Anglais (États-Unis) 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.1PL2 Update DataGroups.. Select “ON” value for MIGR_CFG parameter.Import GUI window). Mis en forme : Police :Italique. Passing on and copying of this document... (e..cfg file: . Enter /alcatel/ExpTmp/<NMS>_<NMS Id> into WORK_AREA parameter.9). is the NMS target version. Select “OFF” value for KEEP_SYSCONF parameter..so that you have: -rwxr-x--x 1 oracle All rights reserved.root # cd / ..sys...log and files in /alcatel/ExpTmp/<NMS>_<NMS Id>/MigrDataRestoring/Log directory.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 6 RELEASED Optics 8DG 31466 AAAATCZZA 111/157 .4.g. 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.sys.nonexistent constraint Supprimé : 7 is the NMS product. Select “any” value for GROUPS parameter. When importing 1354RM or 1354BMETH database inside import_db.sys.root # export KERNEL_RELEASE=8.

./RM_DB/Kernel/conf/MIGR.log glob failed (child exited with status 1) at /usr/Systems/1353NM_2-7.5/AS/script/migrate. in file restoreDB_PM./Kernel/data/INDEX at /alcatel/7. (e..log Error.log /usr/local/bin/pmdb_restore[3]: /usr/Systems/1353NM_2-7.g./lib/lib_perl/CfgParser.4..4.log ERROR: keys file not found Restore DataGroups files: .: for 1354RM is 7.1D/Kernel/etc/.1354RM_1-7.cfg./data/ascurim//configDb.sys.sav file not found in file SEC_AC_adjust.ac.4.sh: not found.log //usr/Systems/1353NM_1-7.5/ac_info: not found.pm line 83. in file updateSMFconfig.. sed: Cannot find or open file users.pm line 83./lib/lib_perl/CfgParser.. not permitted without written authorization from Alcatel Neglect the following messages. in file as_imp_action. is the NMS target version.root # update_DG <NMS>_<NMS Id>-<NMS Version> –restore Where: <NMS> <NMS Id> <NMS Version> is the NMS product. Error.4 file!! ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 112/157 1AA 00014 0004 (9711) A4 . ERROR: Cannot open file: /usr/Systems/1353NM_1-7..log /usr/local/bin/AC_create_links: /usr/Systems/1353NM_1-7.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> All rights reserved.pl line 10. line #3873: Unknown Application. use and communication of its contents. if present: in file ASdbManager_restore.4. line #2080: Unknown Function.5/ac_info/.4 file!! WARNING: restore invoked on a not-existing ..5/ac_info/./PMDS_DB/Kernel/conf/MIGR.3//MYSQL/script/envMYSQL. Error.4. Ignore warnings like the following: WARNING: restore invoked on a not-existing . Passing on and copying of this document.1D/Kernel/etc/./Kernel/data/INDEX at /alcatel/7. line #2084: Name Already Used.9).1354RM_17. in file SEC_import. ERROR: Cannot open file: /usr/Systems/1353NM_1-7.5/AS/script/. is the NMS instance identification number.4..cfg.

.13 APPENDIX F: 1353NM DATA CONVERSION Overview All rights reserved.. .pl cd /usr/Systems/1353NM_1-7. it is mandatory to re-import and re-convert data from the beginning.5/MYSQL/script/db_stop.. $ $ $ $ /usr/Systems/1353NM_1-7. 1353NM Data conversion Warning! Conversion scripts can be launched only once! If you have to relaunch them../pms_upgrade /usr/Systems/1353NM_1-7.4. . Passing on and copying of this document.5/MYSQL/script/db_start.4.. Login as axadmin user and execute the following command: .. use and communication of its contents.5/PMDS_DB/script ...4. not permitted without written authorization from Alcatel 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..pl 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 113/157 .

Install and customize DB migration tool to get to 1354RM 7. Install and customize DB migration tool to get to 1354RM 7.4s7 level 16. Convert DB to 1354RM 7.4s4 DB 9. Please use this appendix only when referenced to .tar. Convert DB to 1354RM 7.2-7-B1. To perform the DB conversion the following sections must be followed in sequence: 1.R7.5s0 level 21. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 1354RM DB conversion Warning! Conversion scripts can be launched only once! If you have to relaunch them. Convert DB to 1354RM 7. All rights reserved. use and communication of its contents.4s6 DB 13. Install and customize DB migration tool to get to 1354RM 7. Retrieve conversion tools 2. it is mandatory to re-import and re-convert data from the beginning. Install and customize DB migration tool to get to 1354RM 7.4s9 DB 17.3-10-B1. 1354RM-NRMIG.4s7 DB 15.gz b. Create Payload MAP tables entries 8. Convert DB to 1354RM 7.4s3 level 7. Convert DB to 1354RM 7.4s8 level 18. Install and customize DB migration tool to get to 1354RM 7.gz (cksum & size: 3568575964 85862) (cksum & size: 2508726815 9926040) ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 114/157 . Convert DB to 1354RM 7. Install and customize DB migration tool to get to 1354RM 7.tar.4s6 level 14. Convert DB to 1354RM 7.5s0 DB 20. Convert DB to 1354RM 7.9 3.3 DB 4.4. Install and customize DB migration tool to get to 1354RM 7. Install and customize DB migration tool to get to 1354RM 7.4s5 DB 11.4s4 level 10. Check DB conversion Retrieve Conversion Tools Copy 1354RM conversion tools into /alcatel/DEPOT directory: a.R7. 1354RM-NRMIG. Convert DB to 1354RM 7.3 level 5.4s9 level 19.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. Define how to migrate to 1354RM 7.4.4s3 DB 6. Passing on and copying of this document.4.4s5 level 12.

7. 1354RM-NRMIG_7.4.7_B1. Before starting conversion perform the following w/a: .gz f.tar.4.tar.3_B2.gz Warning: after download completion.4.gz g. 1354RM-NRMIG_7.5. use and communication of its contents.4..7_B2.0.4.sys.c.9. Passing on and copying of this document..pl 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 115/157 .10_B1.tar.tar. 1354RM-NRMIG_7.5.1PL2/NMA/RM_MIG/7.4. 1354RM-NRMIG_7. not permitted without written authorization from Alcatel (cksum & size: 4229474999 16231) (cksum & size: 3090942239 24909) (cksum & size: 3632164844 32855) (cksum & size: 4164855359 45979) (cksum & size: 260089226 22959) e.9/rm/migtool/bin/setNetworkInterfaceLevel.tar.gz All rights reserved.root # chmod 777 \ [Enter] /alcatel/8. 1354RM-NRMIG_7. it is recommended to check the package file checksum.gz d..2_B1.

4.4s8 and 7.4.4s5 Install RM_NRMIG Tool 7. Passing on and copying of this document.4s9 Install RM_NRMIG Tool 7.3 & Convert database to 7.4.0 & Convert database to 7.4.4s4 Install RM_NRMIG Tool 7.4s6 Install RM_NRMIG Tool 7.0 & Convert database to 7.7 & Convert database to 7.5s0 Install RM_NRMIG Tool 7.5.4s5 Install RM_NRMIG Tool 7.7 & Convert database to 7.5s0 Install RM_NRMIG Tool 7.6 & Convert database to 7.4s7 Install RM_NRMIG Tool 7.4s5 Install RM_NRMIG Tool 7.4. The paragraphs to be followed to convert your specific database depends on the your source release and your target version.4 & Convert database to 7.1 NM NM NM ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 116/157 .4.5 & Convert database to 7.4s9 Install RM_NRMIG Tool NR7.5 & Convert database to 7.4s3 (NR7.4s8 and 7.6 & Convert database to 7.1PL2 Install RM_NRMIG Tool 7.4 & Convert database to 7. The table hereafter explain you which paragraphs of this appendix must be followed to perform the conversion: Source NR All rights reserved.0 & Convert database to 7.4.2PL2 Install RM_NRMIG Tool 7.4s9 Install RM_NRMIG Tool 7.9 & Convert database to 7.3 NM Install RM_NRMIG Tool 7.9 & Convert database to 7.4) NR7.6 & Convert database to 7. use and communication of its contents.4.4s4 Install RM_NRMIG Tool 7.4 NM NM NR8.4.9 & Convert database to 7.5.4.4.4 & Convert database to 7.4s8 and 7.4s7 Install RM_NRMIG Tool 7.5.4s6 Install RM_NRMIG Tool 7.4.4.4.5s0 Install RM_NRMIG Tool 7.7 & Convert database to 7.3 & Convert database to 7.4.4s7 Install RM_NRMIG Tool 7.4.Convert database Hereafter are described steps needed to convert 1354RM database.4s9 Install RM_NRMIG Tool 7.2 & Convert database to NR7.9 & Convert database to 7.4.4s4 Install RM_NRMIG Tool 7.3 Install RM_NRMIG Tool 7.4s3 NR7.4s6 Install RM_NRMIG Tool 7.4.4.5 & Convert database to 7. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Target NR = 8.4s8 and 7.1DPL2 NR7.4s6 Install RM_NRMIG Tool Install RM_NRMIG Tool 7.4.6 & Convert database to 7.

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).7.0 & Convert database to 7.4.4s9 Install RM_NRMIG Tool 7.4s7 All rights reserved. use and communication of its contents.5.9 & Convert database to 7.0 & Convert database to 7. not permitted without written authorization from Alcatel 7. Passing on and copying of this document.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.5s0 NR8.7 & Convert database to 7.4s8 and 7. 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 117/157 .4.5.5s0 Install RM_NRMIG Tool 7.

4/rm/migtool/sql Install the conversion tool.4.root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG... Customize the conversion tool: ..root # cd /usr/Systems/1354RM_1-7.4.orig Edit the file “old_db_incremental_migration” in order to put a comment before the commands that delete the log files (lines 46...pl \ [Enter] -sys 1354RM -inst 1-7.tar..4.root # rm -r /alcatel/8. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 sql Don’t worry about them.R7. If you have to repeat the conversion...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.root # cp –p old_db_incremental_migration \ [Enter] old_db_incremental_migration..sys. Login into the system as user root and Install the tools executing: .2 Warning! Installing this software you overwrite any other version.root # ln –sf /alcatel/8. 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 6 RELEASED Optics 8DG 31466 AAAA TCZZA 118/157 .sys.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: . 58)...4.1PL2/Kernel/script/updateInstance.9/migtool ..1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time.sys..root # /alcatel/8.1PL2/NMA/RM_NRMIG/7. use and communication of its contents. skipping it .9/migtool/bin/ .4.sys..root # cd /usr/Systems/1354RM_1-7..Install and Customize NRMIG 7... Before NRMIG 7.2 installation execute: ...sys.4..... you have to execute .1PL2/NMC/…. Passing on and copying of this document.2-7-B1. All rights reserved.

sql.... .txt” otherwise you risk to launch other./.. In this phase the NR7. Set the environment for the 1354RM Instance . $ cd migtool/bin 4. not permitted without written authorization from Alcatel # 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. Hereafter a list of possible message that you should ignore.9 ..2 PL2) database will be converted to NR7. $ grep ORA.1D/7.err_MIG_NR71DtoNR73./conf/migrationNR71DtoNR73.3 ....tag with: . $ .snmlrc 3.echo "ERROR:\tduring database schema migration (log in ${MIG_TOOL_LOG})\n" exit 1 fi All rights reserved.. Change to the directory: . use and communication of its contents. similar..9/migtool/log 2. $ cd /usr/Systems/1354RM_1-7.. scripts corrupting your DB! Wait that the conversion ends (this could take long time for big networks)..sql.4.. $ cd /usr/Systems/1354RM_1-7.txt Take care to write correctly “migrationNR71DtoNR73.2 (NR7.1D/7. In this directory search file with name: err_MIG_NR71DtoNR73.lst | sort -u Check the log for critical errors. If all It’s 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 directory: . 1./old_db_incremental_migration -v –f \ [Enter] . Open a shell on the target 1354RM machine as snml user 2. $ . Passing on and copying of this document.lst In these files look for ORA. Execute the conversion of the database using the “RM_migration” tool: .3 Follow this section only if required (see section “convert database”). 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 119/157 .4.

. $ ..4.7/rm/migtool/sql sql ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 120/157 1AA 00014 0004 (9711) A4 .4.1PL2/NMA/RM_MIG/7.root # cd /usr/Systems/1354RM_1-7..root # ln –sf /alcatel/8. otherwise ask for support.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 All rights reserved.9/migtool .nonexistent constraint object <object name> does not exist If there is no errors outside the table you can proceed in the migration. not permitted without written authorization from Alcatel 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 .9/databases/dbsnml/admin/conv ....4.sys. as root: .. $ cd /usr/Systems/1354RM_1-7./migPTRSUBLINK. use and communication of its contents. Passing on and copying of this document.pl $NXNL_DATABASE After conversion execute.no such constraint cannot drop constraint . Run the following in order to fix a problem on map visualization: .... 5.sys.

Login into the system as user root 2.1PL2/NMA/RM_KERNEL/7..1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time...4. not permitted without written authorization from Alcatel Warning! Installing this software you overwrite any other version. Execute: .9/NRMIG/bin . you have to execute .R7.4. 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.sys.root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG.4. If you have to repeat the conversion.3 All rights reserved.1PL2/Kernel/script/updateInstance. Edit the file “RM_migration” in order to put a comment before the commands that delete the log files (lines 52. Don’t worry about them.root # cd /usr/Systems/1354RM_1-7..root # cd /usr/Systems/1354RM_1/NRMIG/sql sys.root # ln –sf /alcatel/8. Login into the system as user root and Install the tools executing: . 66)..4... Customize the conversion tool: . 53.* 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 6 RELEASED Optics 8DG 31466 AAAATCZZA 121/157 .tar..4.sys....3-10-B1..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..root # cp –p RM_migration RM_migration.1PL2/NMC/….orig 3. Install the conversion tool. Passing on and copying of this document...root # /alcatel/8.pl \ [Enter] -sys 1354RM -inst 1-7.. skipping it .sys. use and communication of its contents.Install and Customize NRMIG 7...sys. 65...9 -type NMA –comp RM_NRMIG -skipconfig –light .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.root # rm -r /alcatel/8.

9/NRMIG/log has the write access right for alcatel user with: . not permitted without written authorization from Alcatel ${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. Execute ./.. Execute the conversion of the database using the “RM_migration” tools. scripts corrupting your DB! All rights reserved... Passing on and copying of this document.. Save and exit Convert database to 1354RM7. $ cd /usr/Systems/1354RM_1-7... $ ll –d /usr/Systems/1354RM_1-7. $ exit 4...snmlrc 3.4s3 Follow this section only if required (see section “convert database”)..3 database will be converted to NR 7. Check that /usr/Systems/1354RM_1-7../RM_migration -v -f . $ chmod 777 /usr/Systems/1354RM_1-7... Set the environment for the 1354RM Instance . 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>.. . 1.4..4. 6. use and communication of its contents..9/NRMIG/log .9/NRMIG/log If not..txt ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 122/157 1AA 00014 0004 (9711) A4 Take care to write correctly “migrationNR73toNR74s3. Open a shell on the target 1354RM machine as snml user 2. $ su ./conf/migrationNR73toNR74s3.4.. Change to the directory: . In this phase the NR7. $ .* else echo "ERROR:\tduring fix database upgrade (log in ${MIG_TOOL_LOG})\n" exit 1 fi .. $ . . similar.4.4.9 .txt” otherwise you risk to launch other. remove any write protection entering: . $ cd NRMIG/bin 5. $ sqlplus $NXNL_DATABASE SQL> select index_name from all_indexes where table_name='PMTRAN' or table_name='PMTP'..4.

$ grep ORA. otherwise proceed with this : 1.4.cc at line 84: MIB array attributes is NULL ! 3.tag with: .4.../.MIG_ORACLE_NR73toNR74s3..9/NRMIG/log/payMapBuilder.9/NRMIG/sql/checkAZtopId.9/NRMIG/sql/postMigration743...log SQL> @/usr/Systems/1354RM_1-7.. Table 16 shows the list of message that you should ignore.9/NRMIG/log/payMapBuilder.. Passing on and copying of this document. use and communication of its contents.4.4..... Change to the directory: .. $ .4.4..4. If everything works fine.4..log 2.. Execute the script checkAZtopId. . ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 123/157 . $ cd /usr/Systems/1354RM_1-7..err | sort -u Check the log for critical errors.sql SQL> commit.sql and ensure that no rows are selected from the Database: . Always execute: .9/NRMIG/log/postMigration743.log” to see if errors have been detached entering: .sql 1AA 00014 0004 (9711) A4 In case of rows presence please contact TEC Italy.snmlrc . In this directory search file with name: MIG_ORACLE_NR73toNR74s3 In these files look for ORA. Table 16 shows the list of message that you should ignore.. Check logs file “payMapBuilder. not permitted without written authorization from Alcatel NOTE: Fix database upgrade OK In this case continue with the next command. Open a shell on the target 1354RM machine as snml user with graphical interface: . $ export NXNL_NE_FEATURES_DIR=/usr/Systems/1354RM_1-7./paymapMig -allMib -log \ [Enter] /usr/Systems/1354RM_1-7.9/NRMIG/lib:$SHLIB_PATH . $ cd NRMIG/bin . $ cd /usr/Systems/1354RM_1-7. $ export SHLIB_PATH=/usr/Systems/1354RM_1-7..9 .4...cc at line 567: Filter size (50) exceeded: reallocating Mib 00002 ERROR in file MibDescriptor. $ grep –i –e error –e warning \ [Enter] /usr/Systems/1354RM_1-7. SQL> quit Check the log for critical errors. $ sqlplus $NXNL_DATABASE SQL> spool /usr/Systems/1354RM_1-7. the following message appears when conversion finishes: All rights reserved.9/NRMIG/log 2. $ sqlplus $NXNL_DATABASE \ [Enter] @/usr/Systems/1354RM_1-7.9/NRMIG/conf .. 7.log If present ignore messages similar to these: aFILT 00002 WARNING in file GenericFilter. $ .Wait that the conversion ends (this could take long time for big networks). Create Payload MAP tables entires Create the payload Map tables executing the following command: 1..

sys...4..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.9/NRMIG/log has the write access right for alcatel user with: . /usr/snml/...1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time..root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG_7. In this phase the RM7..4 . If you have to repeat the conversion. remove any write protection entering: .. you have to execute .. 60 (see previous paragraph)..4. Set the environment for the 1354RM Instance .4s4.9/NRMIG/log If not..snmlrc . use and communication of its contents. $ cd /usr/Systems/1354RM_1-7..pl \ [Enter] -sys 1354RM -inst 1-7. Customize the conversion tool: .4..4s3 (NR7. .. 59..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: . Convert database to 1354RM7.9/NRMIG/log . Login into the system as user root and Install the tools executing: . Open a shell on the target 1354RM machine as snml user 2. $ exit ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 124/157 1AA 00014 0004 (9711) A4 All rights reserved.snmlrc 3.. skipping it .4.root # ln –sf /alcatel/8.1PL2/Kernel/script/updateInstance.sys. $ chmod 777 /usr/Systems/1354RM_1-7. 1.Warning! Installing this software you overwrite any other version..1PL2/NMA/RM_KERNEL/7.4.root # cd /usr/Systems/1354RM_1/NRMIG/sql sys.. $ .sys.2_B1..root # /alcatel/8. Don’t worry about them..4.4. not permitted without written authorization from Alcatel Install and Customize NRMIG 7. Install the conversion tool.4...4) database will be converted to RM 7.sys./. 47.tar. Passing on and copying of this document. $ su ..4s4 Follow this section only if required (see section “convert database”).4.root # rm -r /alcatel/8...1PL2/NMC/….9/rm/lib/perl/Config Config (Re)execute the adaptation to keep the log of the conversion at lines 46.9 .. $ ll –d /usr/Systems/1354RM_1-7. Check the /usr/Systems/1354RM_1-7.

use and communication of its contents./RM_migration -v -f . $ cd /usr/Systems/1354RM_1-7.4.tag with: .. $ export SHLIB_PATH=/usr/Systems/1354RM_1-7...4.. Don’t worry about them.MIG_ORACLE_NR74s3toNR74s4. 68 (see previous paragraph). $ cd NRMIG/bin All rights reserved.4. 53... $ . Change to the directory: . $ grep ORA.sys.pl \ [Enter] -sys 1354RM -inst 1-7.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..9 -type NMA -comp RM_NRMIG -skipconfig –light .txt Take care to write correctly “migrationNR74s3toNR74s4.4.4.. similar.. Install and Customize NRMIG 7..1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time.root # ln –sf /alcatel/8..3_B2. you have to execute .root # cd /usr/Systems/1354RM_1/NRMIG/sql sys.5 Warning! Installing this software you overwrite any other version......9/NRMIG/lib:$SHLIB_PATH .err | sort -u Check the log for critical errors.1PL2/Kernel/script/updateInstance. 67.. Customize the conversion tool: . Install the conversion tool.1PL2/NMA/RM_KERNEL/7. Table 16 shows the list of message that you should ignore.sys.. Execute the conversion of the database using the “RM_migration” tools: . 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 125/157 .sys.root # /alcatel/8.. skipping it .sys... not permitted without written authorization from Alcatel 5.4.4. scripts corrupting your DB! Wait that the conversion ends (this could take long time for big networks)..9/rm/lib/perl/Config Config (Re)execute the adaptation to keep the log of the conversion at lines 52.txt” otherwise you risk to launch other.root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG_7..9/NRMIG/log In this directory search file with name: MIG_ORACLE_NR74s3toNR74s4 In these files look for ORA.5. If you have to repeat the conversion. Passing on and copying of this document.root # rm -r /alcatel/8./conf/migrationNR74s3toNR74s4.. If everything works fine.tar.. Login into the system as user root and Install the tools executing: . otherwise proceed with this : Change to the directory: .1PL2/NMC/…. the following message appears when conversion finishes: NOTE: Fix database upgrade OK In this case continue with the next section.

.4s4 database will be converted to RM 7. $ chmod 777 /usr/Systems/1354RM_1-7.9/NRMIG/log .4. Install and Customize NRMIG 7. otherwise proceed with this : Change to the directory: ..err | sort -u Check the log for critical errors..1)..txt” otherwise you risk to launch other. $ su .. In this phase the RM7.sys.4. Open a shell on the target 1354RM machine as snml user Set the environment for the 1354RM Instance . $ cd /usr/Systems/1354RM_1-7..6 Warning! Installing this software you overwrite any other version.9/NRMIG/log If not. you have to execute .4..tag with: . .... similar. use and communication of its contents. $ cd /usr/Systems/1354RM_1-7.4s5 (NR8.MIG_ORACLE_NR74s4toNR74s5...snmlrc Check the /usr/Systems/1354RM_1-7.. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 In this case continue with the next section..1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time. If you have to repeat the conversion. If everything works fine..9/NRMIG/log In this directory search file with name: MIG_ORACLE_NR74s4toNR74s5 In these files look for ORA. the following message appears when conversion finishes: NOTE: Fix database upgrade OK All rights reserved. Table 16 shows the list of message that you should ignore./. $ exit Change to the directory: .9/NRMIG/log has the write access right for alcatel user with: .9 .. $ cd NRMIG/bin Execute the conversion of the database using the “RM_migration” tools: . scripts corrupting your DB! Wait that the conversion ends (this could take long time for big networks). $ ll –d /usr/Systems/1354RM_1-7..root # rm -r /alcatel/8.4../conf/migrationNR74s4toNR74s5. $ .. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 126/157 .4.../RM_migration -v -f .txt Take care to write correctly “migrationNR74s4toNR74s5.. $ . remove any write protection entering: .. Passing on and copying of this document.. $ grep ORA.4s5 Follow this section only if required (see section “convert database”).4.Convert database to 1354RM7.

. not permitted without written authorization from Alcatel 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.. skipping it ./.. If everything works fine..9/NRMIG/log If not... $ .pl \ [Enter] -sys 1354RM -inst 1-7.gz interactive=no All rights reserved.9/NRMIG/log .sys..6. $ chmod 777 /usr/Systems/1354RM_1-7. Passing on and copying of this document.. scripts corrupting your DB! Wait that the conversion ends (this could take long time for big networks). 78 (see previous paragraph).4.1PL2/NMC/…. 63.4. otherwise proceed with this : Change to the directory: .Install the conversion tool. $ su .. 77.5_B1. $ cd /usr/Systems/1354RM_1-7. $ . Convert database to 1354RM7... the following message appears when conversion finishes: NOTE: Fix database upgrade OK In this case continue with the next section.1PL1).. Don’t worry about them. Open a shell on the target 1354RM machine as snml user 5. similar. $ cd /usr/Systems/1354RM_1-7.. . 4../RM_migration -v -f . Change to the directory: .4s6 Follow this section only if required (see section “convert database”)..txt” otherwise you risk to launch other. remove any write protection entering: .4s6 (NR8.4.sys.tar.. use and communication of its contents. Execute the conversion of the database using the “RM_migration” tools: ./conf/migrationNR74s5toNR74s6.. Customize the conversion tool: .txt Take care to write correctly “migrationNR74s5toNR74s6.4.. Login into the system as user root and Install the tools executing: .. $ exit 7.snmlrc 6.1PL2/Kernel/script/updateInstance. Check the /usr/Systems/1354RM_1-7..9/NRMIG/log has the write access right for alcatel user with: . $ ll –d /usr/Systems/1354RM_1-7. Set the environment for the 1354RM Instance .9 -type NMA -comp RM_NRMIG -skipconfig –light (Re)execute the adaptation to keep the log of the conversion at lines 62....4.4.9 .9/NRMIG/log 1AA 00014 0004 (9711) A4 In this directory search file with name: MIG_ORACLE_NR74s5toNR74s6 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 127/157 .root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG_7...4.root # /alcatel/8. In this phase the RM7.. $ cd NRMIG/bin 8..4s5 database will be converted to RM 7.

Install and Customize NRMIG 7....root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG_7.7.sys. $ chmod 777 /usr/Systems/1354RM_1-7..9 -type NMA -comp RM_NRMIG -skipconfig –light (Re)execute the adaptation to keep the log of the conversion at lines 62..9/NRMIG/log If not. Passing on and copying of this document.1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time. If you have to repeat the conversion.. $ grep ORA.root # /alcatel/8.. $ su . Login into the system as user root and Install the tools executing: .1PL2/NMC/….4s7 (NR8.1PL1). a. Convert database to 1354RM7.snmlrc c../..7 Warning! Installing this software you overwrite any other version. you have to execute .tag with: All rights reserved. .9 . 77.tar.. skipping it . use and communication of its contents.4.. $ . Table 16 shows the list of message that you should ignore.err | sort -u Check the log for critical errors. 78 (see previous paragraph). not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 .9/NRMIG/log .4.4s7 Follow this section only if required (see section “convert database”). Open a shell on the target 1354RM machine as snml user b..1PL2/Kernel/script/updateInstance.MIG_ORACLE_NR74s5toNR74s6. Customize the conversion tool: . $ cd /usr/Systems/1354RM_1-7..4s6 database will be converted to RM 7...pl \ [Enter] -sys 1354RM -inst 1-7.4..root # rm -r /alcatel/8. Set the environment for the 1354RM Instance . $ ll –d /usr/Systems/1354RM_1-7.. Check the /usr/Systems/1354RM_1-7.4..9/NRMIG/log has the write access right for alcatel user with: . Install the conversion tool... Change to the directory: ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 128/157 .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.sys. 63.. remove any write protection entering: .In these files look for ORA..7_B1.4.4. In this phase the RM7. $ exit d.sys...4. Don’t worry about them..

txt doesn't exist at /usr/Systems/1354RM_17.9 Warning! Installing this software you overwrite any other version.10_B1.root # rm -r /alcatel/8..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.MIG_ORACLE_NR74s6toNR74s7... otherwise proceed with this : Change to the directory: ... . $ cd /usr/Systems/1354RM_1-7. Passing on and copying of this document. Execute the conversion of the database using the “RM_migration” tools: All rights reserved.... similar.. the following message appears when conversion finishes: NOTE: Fix database upgrade OK In this case continue with the next section. scripts corrupting your DB! If you get the following (or similar) error: Migration hist.pl line 499..4. 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 129/157 ..9/NRMIG/log In this directory search file with name: MIG_ORACLE_NR74s6toNR74s7 In these files look for ORA....tag with: .err | sort -u Check the log for critical errors. Install and Customize NRMIG 7.txt” otherwise you risk to launch other. If you have to repeat the conversion. skipping it ./conf/migrationNR74s6toNR74s7.4...7/NRMIG/bin/RM_migration.4..1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time. file: ./RM_migration -v -f .root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG_7..txt Take care to write correctly “migrationNR74s6toNR74s7. $ cd bin and repeat the command. If everything works fine.. ERROR: during database schema migration ! try to execute: . Wait that the conversion ends (this could take long time for big networks)./conf/migrationNR74s6toNR74s7..sys. $ cd NRMIG/bin e.. Don’t worry about them.... $ cd .9. use and communication of its contents. $ grep ORA. • • Login into the system as user root Install the tools executing: .sys. Table 16 shows the list of message that you should ignore.1PL2/NMC/…. you have to execute .4. not permitted without written authorization from Alcatel .tar. $ .

/setSch747_814../conf/migrationNR74s8toNR74s9./conf/migrationNR74s7toNR74s8.. Execute: . Login as snml user Set the environment for the 1354RM Instance . use and communication of its contents. $ .. ...4.9/NRMIG/log If not. $ chmod 777 /usr/Systems/1354RM_1-7.9 -type NMA -comp RM_NRMIG -skipconfig –light • Execute adaptation to keep the log of the conversion: ...root # vi RM_migration put a comment before the commands that delete the log files (lines 59. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 .txt .4s9 (NR8. $ ll –d /usr/Systems/1354RM_1-7.././RM_migration –v -f . $ cd NRMIG/bin ..txt” and “migrationNR74s8toNR74s9.4.. 75) Convert database to 1354RM7.9/NRMIG/log has the write access right for alcatel user with: ./conf/migration_SKIPPED_747_p18...4. $ $ $ $ $ cd ORACLE/databases/dbnml/etc start_db cd /usr/Systems/1354RM_1-7. similar.7. Passing on and copying of this document..1PL1 from 1354RM 7.pl line 499./.. $ su . $ cd /usr/Systems/1354RM_1-7...4s9 In this phase the RM7..... $ cd .. 74.txt doesn't exist at /usr/Systems/1354RM_17..txt” otherwise you risk to launch other.9/NRMIG/bin ..orig . . ..1PL2).txt Take care to write correctly “migrationNR74s7toNR74s8.4.root # cd /usr/Systems/1354RM_1-7.. scripts corrupting your DB! If you get the following (or similar) error: Migration hist.pl \ [Enter] -sys 1354RM –inst 1-7..4. ERROR: during database schema migration ! try to execute: ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 130/157 ..root # /alcatel/8..• Customize the conversion tool: All rights reserved. $ .4s8 database will be converted to RM 7....9/NRMIG/sql ..snmlrc Check the /usr/Systems/1354RM_1-7.txt ... 60.. $ ./conf/migrationNR74s7toNR74s8.4. $ .sys... ...9 .4.5 P17 or lower execute: ..1PL2/Kernel/script/updateInstance../RM_migration -v -f .root # cp –p RM_migration RM_migration./bin Execute the conversion of the database using the “RM_migration” tools: .4....4....pl cd . .9/NRMIG/bin/RM_migration..../RM_migration -v -f . $ exit Only if migrating from NR8.. file: .9/NRMIG/log . remove any write protection entering: .

use and communication of its contents..7_B2.err | sort –u .4..9/NRMIG/log In this directory search files with name: MIG_ORACLE_NR74s7toNR74s8 and MIG_ORACLE_NR74s8toNR74s9 In these files look for ORA.MIG_ORACLE_NR74s7toNR74s8. skipping it .. Don’t worry about them.. $ grep ORA..sys.err | sort -u Check the log for critical errors... not permitted without written authorization from Alcatel and repeat the command. you have to execute .root # /alcatel/8.tag with: .. the following message appears when conversion finishes: NOTE: Fix database upgrade OK In this case continue with the next section.5. $ grep ORA.1PL2/NMC/….5s0 In this phase the RM7. Login as snml user 1AA 00014 0004 (9711) A4 Set the environment for the 1354RM Instance ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 131/157 . If everything works fine..4s9 database will be converted to RM 7. Login into the system as user root Install the tools executing: ...sys. If you have to repeat the conversion.0.4. Wait that the conversion ends (this could take long time for big networks)..0 Warning! Installing this software you overwrite any other version. otherwise proceed with this : Change to the directory: ...9 -type NMA -comp RM_NRMIG -skipconfig –light Convert database to 1354RM7..1PL2/Kernel/script/updateInstance.root # rm -r /alcatel/8..5. Customize the conversion tool: . Install and Customize NRMIG 7.root # /alcatel/INSTALLER/Install 1354RM <hostname> \ [Enter] file=/alcatel/DEPOT/1354RM-NRMIG_7.1PL2/MD4+)..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. $ cd .pl \ [Enter] -sys 1354RM –inst 1-7.. Table 16 shows the list of message that you should ignore. .. $ cd /usr/Systems/1354RM_1-7..sys. Passing on and copying of this document..1PL2/NMA/RM_NRMIG/* and install and customize again this software like the first time..5s0 (NR8. $ cd bin All rights reserved..tar.MIG_ORACLE_NR74s8toNR74s9.

4. $ cd NRMIG/bin Execute the conversion of the database using the “RM_migration” tools: .0 DB Upgrade Always follow this section. $ .. similar.. ... $ .... Open a shell on the target 1354RM machine as snml user Set the environment for the 1354RM Instance . $ cd /usr/Systems/1354RM_1-7./conf/migrationNR74s9toNR75s0. $ grep ORA. $ exit Change to the directory: . In this phase some database old tables will be dropped.9 . otherwise proceed with this : Change to the directory: ... $ cd /usr/Systems/1354RM_1-7.4. not permitted without written authorization from Alcatel In this case continue with the next section.4.MIG_ORACLE_NR74s9toNR75s0.txt Take care to write correctly “migrationNR74s9toNR75s0./.9/NRMIG/log ..9 ..../PMDS_2.9/NRMIG/log In this directory search file with name: MIG_ORACLE_NR74s9toNR75s0 In these files look for ORA...snmlrc cd ORACLE/databases/dbnml/etc start_db Mise en forme : Puces et numéros Mise en forme : Puces et numéros Change to the directory: ....4.9/NRMIG/log If not. $ su .snmlrc Check the /usr/Systems/1354RM_1-7.tag with: .... $ .0_NML_DB_UPGRADE. remove any write protection entering: .. $ ll –d /usr/Systems/1354RM_1-7. Passing on and copying of this document.. If everything works fine... .9/NRMIG/log has the write access right for alcatel user with: . $ chmod 777 /usr/Systems/1354RM_1-7.4.. $ $ $ $ cd /usr/Systems/1354RM_1-7. scripts corrupting your DB! Wait that the conversion ends (this could take long time for big networks)../RM_migration -v -f . .4.sh –logpath \ [Enter] /usr/Systems/1354RM_1-7.4.err | sort -u Check the log for critical errors...4.. PMDS 2./. . $ cd /usr/Systems/1354RM_1-7. the following message appears when conversion finishes: NOTE: Fix database upgrade OK All rights reserved. use and communication of its contents. ..9/PMDS_DB/script/ Execute the script: 1AA 00014 0004 (9711) A4 Mise en forme : Puces et numéros ..9/PMDS_DB/trace/ -v ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 132/157 ..txt” otherwise you risk to launch other.. Table 16 shows the list of message that you should ignore.

. quit mkdir /alcatel/DEPOT/NR81PL2_RM_DB chmod 777 /alcatel/DEPOT/NR81PL2_RM_DB Get a snapshot of the database: .4...../MIB_Contents compare /alcatel/DEPOT/NR81PL2_RM_DB_Ref \ [Enter] /alcatel/DEPOT/NR81PL2_RM_DB > \ [Enter] /alcatel/DEPOT/NR81PL2_RM_DB_Diff.9 .. Check DB conversion Hereafter are described the steps to follow to compare the current database schema with the expected one.9/PMDS_DB/trace/ All rights reserved..tag with: .4.. not permitted without written authorization from Alcatel Mise en forme : Puces et numéros Look for ORA. $ . $ grep ORA./.. Login on the 1354RM target machine as user snml .. Passing on and copying of this document. $ vi /alcatel/DEPOT/NR81PL2_RM_DB_Diff. ...drop_pmds_useless_obj..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 6 RELEASED Optics 8DG 31466 AAAATCZZA 133/157 . Neglect the following differences (or similar): "<" indicates NR8.4.log If you find any significant difference please contact TEC Italy before continue with the conversion. Table 16 shows the list of message that you should ignore.log | sort -u Check the log for critical errors.. . . It’s recommended to check converted DB structure following “Check DB conversion“ paragraph.snmlrc sqlplus $NXNL_DATABASE purge recyclebin.. .9/ORACLE/script/ .... use and communication of its contents.. SQL SQL .. $ $ $ > > $ $ cd /usr/Systems/1354RM_1-7. $ cd /usr/Systems/1354RM_1-7./MIB_Contents get /alcatel/DEPOT/NR81PL2_RM_DB Compare the current DB schema with the expected one: ..Change to the directory: . $ .log Check the log file just created: .. $ cd /usr/Systems/1354RM_1-7.

> 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 6 RELEASED Optics 8DG 31466 AAAA TCZZA 134/157 All rights reserved. Passing on and copying of this document. use and communication of its contents. not permitted without written authorization from Alcatel > COUREP_BAK PMREPORTWINDOW NUMBER > COUREP_BAK SECURITYLABEL NUMBER > COUREP_BAK USERLABEL VARCHAR2 22 22 24 .

All rights reserved. use and communication of its contents. not permitted without written authorization from Alcatel < 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 6 RELEASED Optics 8DG 31466 AAAATCZZA 135/157 . Passing on and copying of this document.

use and communication of its contents. Passing on and copying of this document.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. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 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 1 COMPARING SEQUENCE DATA > SCHEDULER_SEQUENCE 1 1.< ROUTLISBL FK_ROUTLISBL_ROUTLINKID R ENABLED < ROUTLISBL FK_ROUTLISBL_SUBLINKID R ENABLED All rights reserved.124c123.124 < < --> OR updClassOid = 14 > OR updClassOid = 15 125a126 OR UPDCLASSOID = 14 OR UP OR PROPCLASSOID = 14 OR ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 136/157 .

1AA 00014 0004 (9711) A4 All rights reserved. not permitted without written authorization from Alcatel < < > --- 499a500 ED OR DISJCLASS = 135 497. use and communication of its contents.498c498 > OR disjClass = 135 Optics 6 RELEASED 8DG 31466 AAAATCZZA 137/157 . Passing on and copying of this document.

. All rights reserved. Customize the conversion tool: .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.5/. Don’t worry about them..1PL2/NMC/….22. for example.root # /alcatel/INSTALLER/Install 1354BMETH <hostname> \ [Enter] file=/alcatel/DEPOT/1354BMETH_MIBCONV_8.. Passing on and copying of this document.5 Install the conversion tool.. $ /usr/Systems/1354BMETH_1-8.. Startup 1354BMETH database: .0.. Please use this appendix only when referenced to.bmmlrc . $ cd /usr/Systems/1354BMETH_1-8..5.1.gz (cksum & size: 3771959693 58713) Warning: after download completion.1.pl \ [Enter] -sys 1354BMETH -inst 1-8. /usr/Systems/1354BMETH_1-8.3.1... Login into the system as user root and Install the tools executing: .. $ . Install and Customize MIBCONV 8. it is mandatory to re-import and re-convert data from the beginning.22.1PL2/Kernel/script/updateInstance.1. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Retrieve Conversion Tool Copy 1354BMETH conversion tools into /alcatel/DEPOT directory: 1354BMETH_MIBCONV_8.sys..1. skipping it ..5P2RP4 ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 138/157 . Connect to the ORACLE database and run the migration script to convert database (choose the first script according to BMETH starting version. if you have BM-ETH 7..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. it is recommended to check the package file checksum.. use and communication of its contents.sys.1.5.root # /alcatel/8.5/databases/dbbmml/admin/create 2.1.5/ORACLE/databases/dbnml/etc/start_db .tar.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. Warning! Conversion scripts can be launched only once! If you have to relaunch them.tar.

.. $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8141ToDB8157. $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8135ToDB8141......sql .lst Check the log for critical errors.sql . $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8157ToDB8158..sql .. not permitted without written authorization from Alcatel . $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8157ToDB8158... $ grep -i error *.sql ..4 execute: . $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8104ToDB8135...sql . $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8141ToDB8157. $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8104ToDB8135.1 execute: .sql ...sql): If upgrading from NR7..sql If upgrading from NR7. $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8135ToDB8141.sql ..sql .. $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFrom7305P2RP1To7305P2RP6.sql ..sql .. $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8157ToDB8158.. $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFrom711P14RP2To7305P1RP1. $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8135ToDB8141... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8103ToDB8104. Hereafter a list of possible message that you should ignore.sql .sql If upgrading from NR8..1PL1 execute: ... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFrom7305P1RP1To7305P2RP1... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8141ToDB8157. $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFrom7305P2RP6To8103.sql . use and communication of its contents.sql If upgrading from NR8.. $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8157ToDB8158. $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8141ToDB8157.sql .....sql ..lst in the directory: .sql . $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8104ToDB8135.choose as first script MigrateFrom7305P2RP1To7305P2RP6.. Passing on and copying of this document...1DPL2 execute: All rights reserved. $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFrom7305P2RP6To8103..... $ sqlplus ${DB_USER}/${DB_PASSWORD} @MigrateFromDB8103ToDB8104. Oracle code ORA-00942 1AA 00014 0004 (9711) A4 Meaning table or view does not exist ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 139/157 .sql .sql Verify that the migration of the data has been correctly executed checking the files having the extension ..sql ..

Passing on and copying of this document.. 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.no such constraint cannot drop constraint .log 2>&1 It’s recommended to check converted DB structure following “Check DB conversion“ paragraph./renameUnamedConstraints. Login on the 1354BMETH target machine as user bmml . use and communication of its contents./. .. . not permitted without written authorization from Alcatel Table 34.. 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 . .1.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 .1. $ $ $ > > $ $ cd /usr/Systems/1354BMETH_1-8...5/ORACLE/script/ . $ cd /usr/Systems/1354BMETH_1-8. ..5 ./renameUnamedConstraints. Check DB conversion Hereafter are described the steps to follow to compare the current database schema with the expected one..sh 1> ...bmmlrc sqlplus $NXNL_DATABASE purge recyclebin. $ . Execute the script: $ . SQL SQL .nonexistent constraint object does not exist All rights reserved./MIB_Contents get /alcatel/DEPOT/NR81PL2_BMETH_DB ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 140/157 .

/MIB_Contents compare /alcatel/DEPOT/NR81PL2_BMETH_DB_Ref \ [Enter] /alcatel/DEPOT/NR81PL2_BMETH_DB > \ [Enter] /alcatel/DEPOT/NR81PL2_BMETH_DB_Diff.. They are due to input files bad format. All rights reserved. $ . use and communication of its contents.log If you find any significant difference please contact TEC Italy before continue with the conversion.124 < < --> OR updClassOid = 14 > OR updClassOid = 15 125a126 1AA 00014 0004 (9711) A4 OR PROPCLASSOID = 14 OR OR UPDCLASSOID = 14 OR UP > ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 141/157 .124c123.log Check the log file just created: ...Compare the current DB schema with the expected one: .. $ vi /alcatel/DEPOT/NR81PL2_BMETH_DB_Diff.1PL2 database ">" indicates migrated database COMPARING CONSTRAINT DATA < B_PBTERM FK_BPBTERM_ETHSWITCHID R ENABLED Warning! Sometimes the compare tool detects false differences. Passing on and copying of this document. 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. not permitted without written authorization from Alcatel Neglect the following differences (or similar): "<" indicates NR8.

498c498 > OR disjClass = 135 OR DISJCLASS = 135 All rights reserved. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Optics 6 RELEASED 8DG 31466 AAAA TCZZA 142/157 . Passing on and copying of this document.> < < --- ED 499a500 497. use and communication of its contents.

select from the Action List ‘Remove <user> from the SEC database’ as appears in the figure below 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 143/157 ..9/SEC . not permitted without written authorization from Alcatel Adapt the 1354RM SEC database executing: 1. Expand it (click with the “mouse selection button” (MB1) on the inscription of the Operator on the window left side) 2.. The windows will appears as following Figure 16 . $ cd /usr/Systems/1354RM_1-7. Open the SEC graphical interface executing .. 3.. Passing on and copying of this document. On the right side of the window.16 APPENDIX I: 1354RM SEC (SECURITY) DATABASE ADAPTATION All rights reserved. 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). select the profile with the same name of the operator (click with the “mouse selection button” (MB1) on the inscription of the operator) 3.4. Clicking the “quick choice button” of the mouse (MB3). use and communication of its contents. Verify you are still logged in as user alcatel in graphical mode 2. $ script/secusm The SEC graphical interface will be opened. For each operator belonging to the “Operator” list (shown in the red circle): 1.“Operator” in SEC graphical interface 4.

Remove of the profile with the same name of “Operator” 4. The window will appears as following Figure 18 .Figure 17 .“Operator profile” list 1AA 00014 0004 (9711) A4 6. 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. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 144/157 All rights reserved. use and communication of its contents. not permitted without written authorization from Alcatel . Exit from SEC graphical interface selecting ‘Application -> Exit’ and answering “yes” to the question in the message box. Passing on and copying of this document.

..4...root .... not permitted without written authorization from Alcatel 9.: “acnsd_env.users.defined 10. Passing on and copying of this document..sys..sys.sys.7.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”.defined maintenance/tmp/...root .9 maintenance/tmp/. use and communication of its contents. Check the files in ‘/usr/Systems/1354RM_1-7. “prd_env”. Logout from NMS graphical interface 8. and “smf_env” are here present.initiators.9/env ..users.sys.defined repository/.sys.. 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 145/157 .sys...root .. delete it...9/env’ directory executing: . Login as user root... All rights reserved.old”).initiators.root ..root # cd /usr/Systems/1354RM_1-7. If there are some other files (e.root .g.sys..4.4.9/SEC repository/.sys. Remove (if they exist) some SEC configuration files executing: ..root # cd # rm # rm # cd # rm # rm /usr/Systems/1354RM_1-7.4..defined /usr/Systems/1354RM_1-7.

ERROR: . ERROR: . Importing from file:/usr/Systems/1353NM_1/SEC/repository/secimimports/EmlUsmSH5MW_SECPLUG. line #1583: Name Already Used.. NMS 1353NM Useless Error and Warning Messages to be ignored. . ERROR: . ERROR: . ERROR: . line #494: Name Already Used. line #577: Name Already Used. NOTE: Importing EmlUsmSH5MW_SECPLUG. line #426: Name Already Used. line #1074: Name Already Used. line #421: Name Already Used. line #582: Name Already Used. . Skip Action WARNING: Duplicate Id : Action_1 Instance: 1353NM_3 Number: 3 Table 35.. line #715: Name Already Used. line #1019: Name Already Used. line #499: Name Already Used. not permitted without written authorization from Alcatel This appendix shows the useless error and warning message types issued by customize script.import ERROR: . 1353NM Useless Custom Error and Warning messages ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 146/157 1AA 00014 0004 (9711) A4 . line #720: Name Already Used. line #289: Name Already Used. ERROR: . use and communication of its contents. ERROR: .import definitions . line #1578: Name Already Used. Import problem: Name Already Used.. WARNING: Instance: 1353NM_3 Component: NMS Menu: ID Not Defined. ERROR: . ERROR: .. ERROR: .import ERROR:. ERROR: . Passing on and copying of this document. ERROR: . ERROR: . Import problem: Name Already Used. Skip Action WARNING: Duplicate Id : Instance 1353NM_3 Number: 3 WARNING: Instance: 1353NM_3 Component: NMS Menu: ID Not Defined.. Ignore these messages when are issued in the customize log window.17 APPENDIX J: CUSTOM WARNING AND ERROR All rights reserved. line #1069: Name Already Used.. line #284: Name Already Used. Importing from file:/usr/Systems/1353NM_1/SEC/repository/secimimports/EmlUsmSH5WDM_SECPLUG. line #1014: Name Already Used. ERROR: .

ERROR: . ERROR: . line #12: Name Already Used. 1354RM Importing from file:/usr/Systems/1354RM_6/SEC/repository/secimimports/AsCurrentUsm. line #34: Name Already Used. line #82: Name Already Used. ERROR: . ERROR: .NMS All rights reserved.. line #61: Name Already Used. Passing on and copying of this document. line #17: Name Already Used. Table 36. ERROR: .import ERROR: . Import problem: Name Already Used.. ERROR: . line #56: Name Already Used. line #39: Name Already Used. use and communication of its contents. line #87: Name Already Used. NOTE: Importing AsCurrentUsm. 1354RM Useless Custom Error and Warning messages 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 147/157 .import definitions . not permitted without written authorization from Alcatel Useless Error and Warning Messages to be ignored. ERROR: .

not permitted without written authorization from Alcatel When the volume group free disk space is not enough for creating or extending file system or/and swap areas. 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.0 _(free)_ ______ ________ D c4t9d0 8672 0/4/0/0. Allow system to survive in case of a single disk failure.8. HP-UX™. Note: If you have the mirror disk protection before proceed read carefully the “Disk Mirror Configuration Policy” Mis en forme : Police :Italique.0 Pri_Boot _Main_ vg00 c2t2d0 8672 0/0/2/0. use and communication of its contents. Anglais (États-Unis) Supprimé : Disk Mirror Configuration Policy Disk Mirror Configuration Policy The disk mirror capability is used for two main purposes: 1. but to be able to reach the second one you must have an appropriate system configuration in terms of hardware and software. In particular the file name can be very helpful to identify the disk .0 _(free)_ ______ ________ c6t12d0 8672 0/7/0/0. HP-UX™ allows to connect a single disk to two different controller (Dual-Access). The hardware suggested by Alcatel are design to allow mirror configuration that allow system to survive to disk controller failure. It is possible to obtain better high availability only with a correct configuration of the disk resources available on the system. Passing on and copying of this document.2. First of all you have to be able to identify the hard disk present in the configuration. such as VA7110. t[0-15] SCSI of Fibre channel address of the device on the interface. but the software configuration has to be done as shown in this paragraph to do not loose this capability. The disk request list will be issued until the requested amount of disk space need will be not reached. the script issues a list like the following one. but the installation script manage this configuration by showing just one device with a “D” on the first column of the related line. Mirror Disk/UX™ allows reaching the first target without specific configuration. them are usually identified by their file name. Allow system to survive in case of a single disk controller failure.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. in this case the system command can show two device file for the same disk units. d[0-15] Is the device unit number.2. useful for disk array only.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. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 148/157 1AA 00014 0004 (9711) A4 . Using the c# of disk file name is possible to identify the relationship between disks and controllers.12.18 APPENDIX K: NEW DISK REQUEST All rights reserved.0 _(free)_ ______ ________ c6t13d0 8672 0/7/0/0. 2.9.0 Alt_Boot Mirror vg00 D c4t8d0 8672 0/4/0/0.

Because the I/O channel are balanced.Disks configuration Example c6t13d0 With this configuration the best one are: group 1 with c1t2d0. but provided all the case that can occur in field.Now you have to define two disk group (physical volume group) with the following characteristics: 1. Because the two non dual-access disks have been assigned to the two groups. and c2t2d0. Allowed configuration can be: group 1 with c4t8d0. group c4t9d0. The sum of disk space amount of the two group have to be the same. c4t8d0 and c6t12d0. Wrong configuration: group 1 with c1t2d0. The following picture is a schematic example of disk configuration that can produce the output shown before. c4t9d0 and c6t13d0. group 2 with c1t2d0. c1t2d0. c4t8d0 and c4t9d0. 3. The non Dual-Access disks connected to the same controller MUST belong to the same group. and the controller failure gets the system in failure too. All rights reserved. c6t12d0 and c6t13d0. group 2 with c2t2d0. The Dual-Access disks can be assigned to any group. c6t12d0 and c6t13d0. not permitted without written authorization from Alcatel 2. This is not a typical system. c6t12d0 and c6t13d0. c1t2d0 c2t2d0 c4t8d0 c4t9d0 c6t12d0 Figure 19 . c4t8d0 and c4t9d0. group 1 with c2t2d0. 1AA 00014 0004 (9711) A4 ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 149/157 . use and communication of its contents. Passing on and copying of this document. group 2 with c2t2d0.

sys. Otherwise.sys.sys. if it is set to 0.root # lp /etc/TIMEZONE ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 150/157 . This section requires the root access for each command.config.root # lp /etc/gated.sys.d/netconf The command output will show you the current routing configuration.sys.sys.d/netconf file.19 APPENDIX L: RETRIEVE HP-UX SYSTEM INFORMATION Overview This appendix show how retrieve installation relevant information from the a running hp-ux ™ system. in this case the relevant file is /etc/gated. not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 Retrieve IP Network Information Retrieve the hostname and lan0 IP address useful for HP-UX® installation entering: ….root # lp /etc/hosts To retrieve all LAN IP Address configured on the system enter the command: ….sys.root # grep ROUTE /etc/rc.sys. the dynamic routine is disable in this case enter the following command to retrieve the static routing setup: …. use and communication of its contents. if GATED variable is not set to 0.sys. Passing on and copying of this document.root # ifconfig lan0 Print the /etc/host file contents by entering: ….conf exist print it out by entring: …. that means the dynamic routing is enable.root # lp /etc/passwd /etc/group Retrieve Time Zone Print time zone defined by entering the command: ….root # hostname ….conf print it out by entrering: ….root # netstat -in Write down the IP Address of each LAN card.conf If the file /etc/resolv. Check if the dynamic routing is enabled looking at the GATED variable into /etc/rc.config.conf Retrieve User Information Print out the user and group defined by entering the command: …. All rights reserved.root # lp /etc/resolv.

answer “yes” to the following question: Remove all physical OPS startup the batch file removePhy.exe exit code = <0> go to the next point. available in 1354RM-NRMIG.pdl files previously created in order to re-create all the objects needed to restore the network with WDM OTN TP chain. In the first phase.log and go to Error during procedure paragraph. answer “yes” to the following question: Remove path and trail in all physical OPS startup the batch file removePathTrail. In order to remove WDM client paths and trails crossing the 1626LM NEs..pdl. the OPS physical connections. e. Warning! The procedure described in this appendix has to be applied only in case of 1354RM migration from NR7.pdl Do you want to start ? yes(started) or next step . else verify the trace file /tmp/preOTNtoOTN/log/removePhy. and only if the network contains 1626LM 2.. else verify the trace file /tmp/preOTNtoOTN/log/removePathTrail. Passing on and copying of this document. /usr/snml/.. is composed by two phases: d.1 or NR7. trails and physical connections and to recreate them. 3.20 APPENDIX M: 1354RM PRE-OTN TO OTN MIGRATION Overview All rights reserved. The preOtnToOtn procedure./preOtnToOtn.. preOtnToOtn procedure Login on the 1354RM target machine as user snml.pdl files containing commands useful to remove paths.pl 2.pdl Do you want to start ? yes(started) or next step .3 conversion tool.4.9/NRMIG/sql .4. use and communication of its contents. and the WDM client paths.R7. the OCH trails.0A NEs. In order to remove OPS physical connections starting from 1626LM NEs.exe exit code = <0> 1AA 00014 0004 (9711) A4 Mis en forme : Police :Italique Supprimé : Error during procedure go to the next point. Launch preOtnToOtn tool performing the following commands: … $ .3. not permitted without written authorization from Alcatel This appendix shows how to migrate 1354RM WDM TP chain from pre-OTN to OTN. In the second phase the operator is requested to execute the . starting from these nodes. It creates in /tmp/preOTNtoOTN the . If the procedure ends with the following message: rmBatchUtil.txt cd /usr/Systems/1354RM_1-7. 1.pdl.0 or 2. it retrieves 1626LM nodes and. If the procedure ends with the following message: rmBatchUtil.snmlrc … $ unset NLPMAUTOMATICAFTERPATHDISCOVERY … … … … $ $ $ $ export NAV_PORT_NUMBER=1 export ApplicationTraceFile=/tmp/batch_trace.log and go to ED 6 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

Supprimé : Error during procedure

Mis en forme : Police :Italique
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

Mis en forme : Police :Italique

Mis en forme : Police :Italique
Supprimé : Error during procedure

ED

6

RELEASED

Optics

8DG 31466 AAAA TCZZA

152/157

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

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 isn’t 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 doesn’t 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: It’s also possible to start preOtnToOtn procedure with –noStop option: in this case rmBatchUtil doesn’t 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

6

RELEASED

Optics

8DG 31466 AAAATCZZA

153/157

21 APPENDIX N: TROUBLESHOOTING
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

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 wasn’t 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

6

RELEASED

Optics

8DG 31466 AAAA TCZZA

154/157

Remove semaphores using the command: . . . use and communication of its contents...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: ./.. not permitted without written authorization from Alcatel --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..sys..root # ipcs -s | grep 0x00000000 | while read uno id foo do ipcrm -s $id done 3... ..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 All rights reserved. 1AA 00014 0004 (9711) A4 $ $ $ $ cd /usr/Systems/1354RM_1 .sys.... Passing on and copying of this document.. Database extension Oracle uses pre-allocated and not extendible tablespaces... . $ sqlplus /nolog ED 6 RELEASED Optics 8DG 31466 AAAATCZZA 155/157 .. so it could happen that db import fails and in import_db. Restart System Configuration procedure..snmlrc cd ORACLE/databases/dbnml/etc start_db Execute: .

... $ cd ORACLE/databases/dbnml/etc . use and communication of its contents... Stop 1354RM database: .. . $ cd /usr/Systems/1354BMETH_1 . $ $ $ $ cd /usr/Systems/1354BMETH_1 . not permitted without written authorization from Alcatel 1AA 00014 0004 (9711) A4 SQL> alter tablespace <ts_name> add datafile '/usr/Systems/1354RM_1/databases/dbsnml/data/<datafile>02. ED 6 RELEASED Optics 8DG 31466 AAAA TCZZA 156/157 . $ cd ORACLE/databases/dbnml/etc . . Passing on and copying of this document.dbf' size <xxx> M./. If necessay startup 1354BMETH database: ....dbf for the tablespace <ts_name> is created..dbf' size <xxx> M. $ stop_db In the previous sqlplus session a new datafile <datafile>02..... $ stop_db For 1354BMETH db: Login on the spare machine as user bmml. $ sqlplus /nolog SQL> connect / as sysdba SQL> alter tablespace <ts_name> add datafile '/usr/Systems/1354BMETH_1/databases/dbbmml/data/<datafile>02.. Stop 1354BMETH database: ..SQL> connect / as sysdba All rights reserved... $ cd /usr/Systems/1354RM_1 .bmmlrc cd ORACLE/databases/dbnml/etc start_db Execute: .... ... It is recommended to create the new datafile with the same size of the previous one.

not permitted without written authorization from Alcatel ED Optics 6 RELEASED END OF DOCUMENT 8DG 31466 AAAATCZZA 157/157 . use and communication of its contents. Passing on and copying of this document.1AA 00014 0004 (9711) A4 All rights reserved.