Migration Guide

for Network Node Manager (NNM) 7.51

For customers migrating from: NNM 6.2 to NNM 7.51 NNM 6.4x/ET 2.01 to NNM 7.51 NNM 7.01 to NNM 7.51 NNM SE 7.01/7.5 IPF to NNM AE 7.51 IPF NNM AE 7.5 Aries to NNM AE 7.51 IPF NNM 7.5 to NNM 7.51 December 2006

Legal Notices Hewlett-Packard makes no warranty of any kind with regard to the contents of this document, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental, or consequential damages in connection with the furnishing, performance, or use of this material. Warranty: A copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Office. Copyright Notices: Copyright 1983-2006 Hewlett-Packard Development Company, LP, all rights reserved.

WARNING
Once you migrate to NNM 7.51, you cannot go back to your previous version of NNM unless you have a complete and successful backup. Therefore, HP strongly recommends that you complete a full backup of your existing NNM installation, including all executables, configuration files, and database files.

Trademark Notices: Java is a U.S. trademark of Sun Microsystems, Inc. Microsoft is a U.S. registered trademark of Microsoft Corporation Windows, MS Windows, Windows NT, and Windows 2000 are U.S. registered trademarks of Microsoft Corporation Netscape and Netscape Navigator are U.S. trademarks of Netscape Communications Corporation Oracle is a registered U.S. trademark of Oracle Corporation, Redwood City, California Oracle7 is a trademark of Oracle Corporation, Redwood City, California Intel, Pentium, Itanium, and Itanium Processor Family (IPF) are trademarks or registered trademarks of Intel Corporation in the U.S. and other countries and are used under license. UNIX is a registered trademark of The Open Group

Contents
1 Introduction.....................................................................................................................................1
1.1 1.2 1.3 1.4 1.5 Who Should Use this Guide? ............................................................................................................................... 1 How to Use this Guide ........................................................................................................................................ 1 Product Structure and Use of Terms...................................................................................................................... 2 NNM Documentation .......................................................................................................................................... 2 NNM Migration Notes ........................................................................................................................................ 3

Migrating from NNM 6.2 to NNM 7.51 ...........................................................................................4

2.1 2.2 Supported Migration Paths.................................................................................................................................. 4 Migration Process Overview................................................................................................................................ 4

Migrating from NNM 6.4x & ET 2.01 to NNM 7.51 .........................................................................6

3.1 3.2 3.2.1 3.2.2 3.3 Supported Migration Paths.................................................................................................................................. 6 Scalability Differences between NNM 6.4x & ET 2.01 and NNM 7.5x Advanced Edition using ET technology ........... 6 Using bridge.nodiscover file in a Windows Environment.................................................................... 7 Operating Systems and Scalability ........................................................................................................ 7 Migration Process Overview................................................................................................................................ 7

Migrating from NNM 7.01 to NNM 7.51 .........................................................................................9

4.1 4.2 Supported Migration Paths.................................................................................................................................. 9 NNM 7.01 to 7.51 Migration Steps...................................................................................................................... 9

Migrating from NNM 7.01 or 7.5 to NNM 7.51 on HP-UX Itanium.................................................10

5.1 Migrating from NNM SE 7.0, SE 7.5 or AE 7.5 in Aries dynamic translation mode to NNM AE 7.5 in native mode on HP-UX Itanium ............................................................................................................................................................... 10 5.1.1 5.1.2 5.2 Migrating from NNM SE 7.01 or NNM SE 7.5 to the October 2005 NNM AE 7.5 Itanium release .............. 11 Migrating from NNM AE 7.5 in Aries dynamic translation mode to NNM AE 7.5 in native mode.................. 12 Completing your NNM 7.51 migration on HP-UX Itanium.................................................................................... 13

Updating NNM 7.5 to NNM 7.51 ..................................................................................................13

6.1 6.2 Supported Migration Paths................................................................................................................................ 13 NNM 7.5 to 7.51 Migration Steps...................................................................................................................... 13

Side-by-Side Migration to NNM 7.51.............................................................................................14

7.1 7.2 7.3 Supported Migration Paths................................................................................................................................ 14 High-Level Migration Steps................................................................................................................................ 14 Detailed Backup and Merge Steps...................................................................................................................... 14

Additional Migration Considerations..............................................................................................15

8.1 8.2 8.2.1 Hardware and Software Requirements............................................................................................................... 15 Licensing .......................................................................................................................................................... 15 License Upgrade Information .............................................................................................................. 15 ii

8.2.2 8.2.3 8.3 8.4 8.5 8.5.1 8.6 8.6.1 8.7 8.8 8.9 8.10

Installing a Provided License............................................................................................................... 15 Requesting a License If None Provided................................................................................................. 16 NNM 7.51 DIM Information .............................................................................................................................. 17 Remote Console Configurations ......................................................................................................................... 17 Migrating with Remote Consoles........................................................................................................................ 18 UNIX Remote Console to UNIX Management Server............................................................................... 18 Relational Database Management System .......................................................................................................... 18 Supported Relational Databases (Data Warehouse) ............................................................................... 18 Existing NNM Configuration Items ..................................................................................................................... 19 Applications with Bitmapped Files...................................................................................................................... 19 Changing Remote Database Management System............................................................................................... 19 Known Issues ................................................................................................................................................... 20 ovdbcheck may fail to start during startup ...................................................................................... 20 ovw.auth & ovwdb.auth are overwritten ..................................................................................... 20 NNM 7.01 to NNM 7.5 or 7.51 migration fails if the OVPI/NNM Integration Module is installed ............ 20

8.10.1 8.10.2 8.10.3 8.11 8.12

NNM Developer's Tool Kit ................................................................................................................................. 20 Application Migration for End Users................................................................................................................... 20 OpenView Applications Compatibility with NNM 7.51 ...................................................................... 20 Third-Party Applications Compatibility with NNM 7.51 ...................................................................... 20 Data Migration ............................................................................................................................ 21 Use of Remote Consoles ................................................................................................................ 21

8.12.1 8.12.2 8.12.3 8.12.4 8.13 8.14

Migration Information for Application Developers............................................................................................... 21 Compiler Issues ................................................................................................................................................ 21 HP-UX PA-RISC considerations ........................................................................................................ 21 HP-UX Itanium considerations ......................................................................................................... 22 Solaris considerations ................................................................................................................... 22

8.14.1 8.14.2 8.14.3 8.15 8.16 8.17 8.18 8.19 8.20

Upgrading NNM 6.2 or 6.4x Integrated Applications to NNM 7.51..................................................................... 22 Installation ....................................................................................................................................................... 22 Licensing .......................................................................................................................................................... 22 Data Stores ...................................................................................................................................................... 23 NNM 6.2 Object Database Port Number Change................................................................................................ 23 Integrating NNM 7.51 Features ......................................................................................................................... 23 Modified APIs.............................................................................................................................. 23 Internationalization....................................................................................................................... 23 Running NNM 5.0x Applications on Remote Consoles with NNM 7.51 ................................................ 23

8.20.1 8.20.2 8.20.3 8.21

Migration of Solid Database to Oracle Database ................................................................................................ 23

Migrating Existing Correlator Fact Stores........................................................................................24

9.1 Migrating Correlator Stores to Composer version 3.32 ........................................................................................ 24 iii

1 Introduction
1.1 Who Should Use this Guide?
This document is intended for NNM customers who have invested time and effort into customizing their current version of NNM and desire to preserve their customizations, such as: Adding symbols and changing map layout; Configuring discovery options; Configuring network polling options; Configuring data collection and thresholds monitoring; Configuring SNMP events; Establishing filters for various aspects of NNMs operation.

Most of the information that implements customization is stored in the NNM OpenView databases, configuration files, and registration files. The objective of this document is to help with the migration of the data in these databases to NNM 7.51. If you have NOT customized your NNM environment or if you wish to discard your customized environment, you can skip much of the information in this document. The specific section for your migration situation should be reviewed for any applicable information to be considered. Additional instructions for your particular migration path are discussed within the section that applies to your migration scenario.

1.2

How to Use this Guide

migrate HP OpenView Network Node Manager (NNM) 6.2, NNM 6.4x/Extended Topology (ET) 2.01, NNM 7.01, or NNM 7.5 to NNM 7.51, or on an HP-UX Itanium system, migrate NNM Starter Edition 7.01, Starter Edition 7.5, or Advanced Edition 7.5 in Aries dynamic translation mode to NNM Advanced Edition 7.51 in native mode.

This guide is designed to assist system administrators as they:

This guide is also intended to assist developers of software who need their software to integrate with NNM 7.51. This document is organized into sections that apply to specific migration scenarios. Before starting to upgrade, you should read all of the sections of this manual that apply to your situation. You might want to print the sections that apply to your scenario and check off the necessary migration steps, as they are completed. For any migration, you should read the following sections. Section 1.3: Product Structure and Use of Terms Section 1.4: NNM Documentation Section 1.5: NNM Migration Notes Section 8: Additional Migration Considerations

In addition, you need to read one of the following sections based on your particular migration scenario. Section 2: Migrating from NNM 6.2 to NNM 7.51 Section 3: Migrating from NNM 6.4x & ET 2.01 to NNM 7.51 Section 4: Migrating from NNM 7.01 to NNM 7.51 Section 5: Migrating from NNM 7.01 or 7.5 to NNM 7.51 on HP-UX Itanium Section 6: Updating NNM 7.5 to NNM 7.51 Section 7: Side-by-Side Migration to NNM 7.51

1.3

Product Structure and Use of Terms

NNM 7.51 Starter Edition (SE) only uses NNM Classic technology. NNM Advanced Edition (AE) uses NNM Classic technology, Extended Topology (ET) technology, and Problem Diagnosis (PD) technology in its base product. NNM AE is also the NNM extensibility platform. That is, you may purchase Smart Plug-Ins to increase the capabilities of your NNM AE product in technology areas such as IPV6, MPLS, or Frame Relay. NNM Starter Edition = NNM Classic product NNM Advanced Edition = NNM Classic product + Problem Diagnosis technology + Extended Topology technology

The product structure changed significantly as of the NNM 7.0 release. Please refer to the NNM 7.51 release notes for more detailed information. Note: The terms NNM 7.5 and NNM 7.51 in this guide refer to both NNM SE and AE products unless otherwise specified.

1.4

NNM Documentation

Before proceeding with an NNM 7.51 migration, please read the NNM 7.51 Release Notes. The Release Notes and NNM manuals are available at: 1. On the NNM CD set: Release Notes: \README.html or /README.html on the NNM 7.51 Update CD NNM 7.51 installation guide (includes NNM 7.5 installation instructions): o o o \Installation_Guide.pdf or /Installation_Guide.pdf (English) on the NNM 7.51 Update CD \Installation_Guide_jpn.pdf or /Installation_Guide_jpn.pdf (Japanese) on the NNM 7.51 Update CD \Installation_Guide_sch.pdf or /Installation_Guide_sch.pdf (Simplified Chinese) on the NNM 7.51 Update CD

All other manuals: \www\htdocs\<Locale>\manuals\<manual_file_name> or /www/htdocs/<Locale>/manuals/<manual_file_name> on CD1 of the NNM 7.5 CD set 2. With NNM installed: Windows http://<hostname of management station>/OvDocs/<Locale>/ReleaseNotes/README.html http://<hostname of management station>/OvDocs/<Locale>/manuals/<manual_file> The manuals can also be viewed using Adobe Acrobat reader on the files in the directory %OV_MAIN_PATH%\www\htdocs\<Locale>\manuals\. Unix http://<hostname of management station>:3443/OvDocs/<Locale>/ReleaseNotes/README.html http://<hostname of management station>:3443/OvDocs/<Locale>/manuals/<manual_file> NOTE: The Web server on your Unix management station may have been configured to use a different port than 3443. If you have trouble connecting at this port, contact your system administrator for the port in use on your NNM management station. The manuals can also be viewed using Adobe Acrobat reader on the files in the directory $OV_MAIN_PATH/www/htdocs/<Locale>/manuals/.

3.

On the Web: The NNM Release Notes and manuals can also be downloaded from HPs Web site. A few manuals, such as this migration guide, are only available on the Web. In addition, document updates and corrections are sometimes published on the Web. HP OpenView manuals are available at http://ovweb.external.hp.com/lpe/doc_serv/.

1.5

NNM Migration Notes

A direct migration: installation of NNM 7.5 and the NNM 7.51 Update CD directly onto a server that is currently running an older NNM release. Sections 2 through 6 describe direct migration scenarios. Direct migration for NNM 7.51 means a direct migration to 7.5, followed by installation of the 7.51 Update CD. Going from NNM 7.5 to NNM 7.51 is not so much a migration as it is a straightforward update. This guide contains consolidated instructions for migrating to NNM 7.5, then updating your NNM 7.5 system to NNM 7.51. A direct migration scenario does require that NNM be stopped and restarted during the installation of the new NNM versions. A side-by-side migration: bringing NNM 7.51 up on a new server and transferring the database, customizations and other configuration information from a server that is currently running an older NNM release. This is sometimes called a database migration. Section 7 describes how to do a side-by-side migration. A big advantage of a side-by-side migration is that it minimizes NNM downtime.

Two possible ways to migrate to NNM 7.51 from a previous release are:

Many of the considerations for bringing customizations forward will apply to both types of migration. The difference lies simply in whether files need to be copied from an existing server to a new server. NOTE: Direct migrations to NNM 7.5 from NNM 6.2, 6.4x, and 7.01 are supported. You can then directly update an NNM 7.5 system to NNM 7.51. No other versions of NNM can be directly migrated to NNM 7.5. Again, direct migration for NNM 7.51 means a direct migration to 7.5, followed by installation of the 7.51 Update CD. If you are migrating from pre-NNM 6.2 (NNM 4.11, NNM 5.x or NNM6.1, for example), you must first migrate to NNM 6.2. Once you have NNM 6.2 installed successfully, you may migrate directly to NNM 7.5 Starter Edition or Advanced Edition, then install the 7.51 Update CD. For assistance with migration to NNM 6.2, please refer to the NNM 6.2 Migration Guide (available online at http://ovweb.external.hp.com/lpe/doc_serv/). If you are migrating from NNM 6.3x/ET1.x, you must first migrate to NNM 6.4x/ET 2.01, see the NNM 6.4x Migration Guide for details. Once you have migrated to NNM 7.51, you can only roll back to the prior NNM version by uninstalling NNM 7.51 and restoring a backup of your NNM installation. You cannot use the database that was converted to NNM 7.51 format with any previous NNM version. Therefore, HP strongly recommends that you complete a full backup of your current installation prior to migrating. Note that databases are automatically converted to the NNM 7.51 format during the update process. Integrated application binaries that work with NNM 7.5 can be used directly with NNM 7.51. Finally, HP cannot possibly test for all potential migration variances that may result from your specific system configuration of hardware, third-party software, NNM configurations, additional OpenView software, and/or historical modifications. If you also have existing applications integrated with NNM, be sure to read sections 8.12 Application Migration for End Users and 8.13 Migration Information for Application Developers.

2 Migrating from NNM 6.2 to NNM 7.51

2.1 Supported Migration Paths
Table 1 Supported Migration Paths to NNM 7.51 From Current Installation Version 6.2 6.2 On this platform HP-UX 10.20, 11.0, 11.11 Solaris 2.6, 2.7, 2.8 To NNM 7.51 On this platform HP-UX 11.0, 11.11, 11.23(1) Solaris 2.8, 2.9, 2.10 Win2000, WinXP(2), Win2003, Win2003 R2

6.2
(1) (2)

WinNT 4.0, Win2000

HP-UX 11.23 is supported on both PA-RISC and Itanium platforms. WinXP here is indicating Windows XP Professional or server. Windows XP Home is not supported.

NOTE: If you are upgrading your operating system in a direct migration scenario at the same time as you are migrating to a new NNM version, you must upgrade your operating system first, before you install NNM 7.5 followed by the NNM 7.51 Upgrade CD. Be sure to apply all necessary operating system patches as specified in the NNM 7.51 Release Notes (available online at http://ovweb.external.hp.com/lpe/doc_serv/). If you upgrade your operating system to Solaris 2.10, you must use the NNM 7.5 product CDs included in the NNM 7.51 product media kit to install NNM 7.5. The CD part numbers for the required Solaris CDs are T2489-15044 and T248915045. If you upgrade your operating system to Windows 2003 R2, you must use the NNM 7.5 product CDs included in the NNM 7.51 product media kit to install NNM 7.5. The CD part numbers for the required Windows CDs are T2489-15046 and T2489-15047.

2.2

Migration Process Overview

Warning: If you are upgrading to NNM 7.51 Advanced Edition from an existing NNM 6.x deployment, you need to be aware of any licensing changes. For example, your 6.x deployment may use an enterprise license, managing an unlimited number of nodes. If you received as your NNM 7.x upgrade an NNM 7.x Advanced Edition license entitling you to manage 1000 nodes, you must check how many nodes are being managed in your NNM 6.x environment. Use the ovtopodump l command to check the number of managed nodes, license type, and number of licensed nodes. If you are currently managing more than 1000 nodes using an existing NNM 6.x enterprise license, you will need to determine which 1000 nodes you want to continue managing with your NNM 7.x Advanced Edition license for 1000 nodes. HP strongly recommends that you complete a full backup of your current installation prior to performing any migration. You will need to stop and restart NNM several times during the migration process. The migration steps are: 1. Backup NNM configuration and database. Follow the instructions from chapter 6 of the NNM 6.2 Managing Your Network with HP OpenView Network Node Manager manual. Go to the chapter titled Preserve Your Sanity: Backup and Polling Configuration and look in the section titled, Backup/Restore to Protect Your Investment of Time. 2. If you are upgrading your operating system at the same time as you are migrating to NNM 7.51, follow your operating system providers instructions for upgrading your operating system to the desired operating system revision. NOTE: If you are using Oracle to store NNM data, please see section 8.6, Relational Database Management System, for information on how to preserve your database installation when upgrading the operating system. 4

3. 4. 5.

Whether upgrading your operating system or not, ensure that you have installed all operating system patches required for NNM 7.51. Refer the NNM 7.51 Release Notes (available online at http://ovweb.external.hp.com/lpe/doc_serv/). Upgrade to an NNM 7.x license key (see section 8.2 Licensing below). Install NNM 7.5, then install the NNM 7.51 Upgrade CD, as follows. Stop NNM in one of the following ways. o o Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Stop Use the %OV_BIN%\ovstop -c or the $OV_BIN/ovstop -c command.

Install NNM 7.5 using the NNM 7.5 CD set as described in the NNM 7.51 Installation Guide. If NNM was not started at the end of the installation, start NNM in one of the following ways in order to complete the migration to NNM 7.5. o o Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Start Use the %OV_BIN%\ovstart -c or $OV_BIN/ovstart -c command.

Stop NNM in one of the following ways. o o Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Stop Use the %OV_BIN%\ovstop -c or the $OV_BIN/ovstop -c command.

Install the NNM 7.51 update CD as described in the NNM 7.51 Installation Guide. If NNM was not started at the end of the installation, start NNM in one of the following ways in order to complete the migration to NNM 7.51. o o Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Start Use the %OV_BIN%\ovstart -c or $OV_BIN/ovstart -c command.

If you also have existing applications integrated with NNM, be sure to read section 8.12, Application Migration for End Users and section 8.13, Migration Information for Application Developers. NOTE: If you use the NNM Developer's Toolkit, you must install NNM 7.51 prior to installing the NNM 7.51 Developers Toolkit. See section 8.11, NNM Developer's Tool Kit.

3 Migrating from NNM 6.4x & ET 2.01 to NNM 7.51

3.1 Supported Migration Paths
Table 2 Supported Migration Paths to NNM 7.51 Starter Edition or Advanced Edition

From Current Installation Version 6.4x 6.4x On this platform HP-UX 11.0, 11.11 Solaris 2.8, 2.9

To NNM 7.51 On this platform HP-UX 11.0, 11.11, 11.23(1) Solaris 2.8, 2.9, 2.10 Win2000, WinXP(2), Win2003, Win2003 R2

6.4x
(1) (2)

Win2000, WinXP

(2)

HP-UX 11.23 is supported on both PA-RISC and Itanium platforms. WinXP here is indicating Windows XP Professional or server. Windows XP Home is not supported.

NOTE: If you are upgrading your operating system in a direct migration scenario at the same time as you are migrating to a new NNM version, you must upgrade your operating system first, before you install NNM 7.5 followed by the NNM 7.51 Upgrade CD. Be sure to apply all necessary operating system patches as specified in the NNM 7.51 Release Notes (available online at http://ovweb.external.hp.com/lpe/doc_serv/). If you upgrade your operating system to Solaris 2.10, you must use the NNM 7.5 product CDs included in the NNM 7.51 product media kit to install NNM 7.5. The CD part numbers for the required Solaris CDs are T2489-15044 and T248915045. If you upgrade your operating system to Windows 2003 R2, you must use the NNM 7.5 product CDs included in the NNM 7.51 product media kit to install NNM 7.5. The CD part numbers for the required Windows CDs are T2489-15046 and T2489-15047.

3.2

Scalability Differences between NNM 6.4x & ET 2.01 and NNM 7.5x Advanced Edition using ET technology

Since ET is very CPU and memory intensive, during the discovery and modeling phases, deploying ET to manage a fairly large network might require some tuning to efficiently use resources where system resources cannot easily be increased. An option is the use of discovery zones or using the exclusion list-filtering features {bridge.noDiscover} discussed below. As of the NNM 7.5 release, there is no longer a need to manually configure zones for discovery. It will be done automatically. The zone discovery feature takes the approach of dividing a network into a number of zones, discovering each zone independently and merging them together through connections at the edges of the zones. However, some rules apply: Switches that are connected together within a subnet should never be separated into different zones. Smaller subnets could be combined to form a zone. Verify appropriate zone definition by checking known VLAN views to confirm they are not split.

For recommended zone sizes, please review the NNM Using Extended Topology manual. The exclusion list-filtering feature is used to specify a list of nodes that should not be discovered. This is enabled by the creation of the $OV_CONF/nnmet/bridge.noDiscover file to contain the list of nodes to be excluded. Below is the suggested process for setting up the exclusion list-filtering feature on a Unix system. $OV_BIN/setupExtTopo.ovpl

If you haven't set up ET yet, you'll need to run the setupExtTopo.ovpl script to enable NNM ET.

$OV_BIN/etrestart.ovpl ovstop c ovet_bridge o After a couple of minutes, stop ET by stopping ovet_bridge

wc l $OV_DB/nnmet/hosts.nnm o Count the number of lines in the hosts.nnm file.

cp $OV_DB/nnmet/hosts.nnm $OV_CONF/nnmet/bridge.noDiscover o Copy the hosts.nnm file to the bridge.noDiscover file.

Edit bridge.noDiscover. o At this point, you now need to tailor your bridge.noDiscover file. Edit the file and delete all the lines with nodes that you want to have ET discover. Leave in the entries of the nodes you want the discovery process to ignore. Remember, the bridge.noDiscover file is used to stop Extended Topology from discovering device information about the nodes listed in this file.

cut f 1 bridge.noDiscover > tmpfile o The bridge.noDiscover file only needs one column of hostnames/IP addresses listed.

mv tmpfile bridge.noDiscover o Now that you have the file populated with all the nodes you wish to exclude, you need to remove the node names since this file only takes IP addresses.

$OV_BIN/etrestart.ovpl o Restart ET to use the bridge.noDiscover file.

wc l $OV_DB/nnmet/hosts.nnm o After a minute, make sure that the new hosts.nnm file is reduced in size.

3.2.1

Using bridge.nodiscover file in a Windows Environment

Manually edit the file bridge.nodiscover using the Windows text editor of your choice. Note only one column of hostnames/IP addresses is needed as opposed to the multiple columns listed in the hosts.nnm file.

3.2.2

Operating Systems and Scalability

Please pay special attention to the following important operating system-related changes in the NNM 7.51 requirements, as documented in the NNM 7.51 Release Notes. It is important that the NNM system to be migrated can meet these requirements; otherwise, an upgrade is not recommended: Increased kernel parameter settings Operating system patch requirements New minimum system requirements for RAM and available swap space, which are higher than in previous versions of NNM.

NOTE: If you are utilizing ovbackup.ovpl, large-scale discoveries in NNM 7.51 ET module can take over 1GB of hard disk space. Please ensure you have enough space to handle such data. Very large discoveries can take several GBs of hard disk space.

3.3

Migration Process Overview

Warning: If you are upgrading to NNM 7.51 Advanced Edition from an existing NNM 6.x deployment, you need to be aware of any licensing changes. For example, your 6.x deployment may use an enterprise license, managing an unlimited number of nodes. If you received as your NNM 7.x upgrade an NNM 7.x Advanced Edition license entitling you to manage 1000 nodes, you must check how many nodes are being managed in your NNM 6.x environment. Use the ovtopodump l command to check the number of managed nodes, license type, and number of licensed nodes. If you are currently managing more than 7

1000 nodes using an existing NNM 6.x enterprise license, you will need to determine which 1000 nodes you want to continue managing with your NNM 7.x Advanced Edition license for 1000 nodes. HP strongly recommends that you complete a full backup of your current installation prior to performing any migration. You will need to stop and restart NNM several times during the migration process. The migration steps are: 1. Backup NNM configuration and database. Follow the instructions from chapter 6 of the NNM 6.4x Managing Your Network with HP OpenView Network Node Manager manual. Go to the chapter titled Preserve Your Sanity: Backup and Polling Configuration and look in the section titled, Backup/Restore to Protect Your Investment of Time. 2. If you are upgrading your operating system at the same time as you are migrating to NNM 7.51, follow your operating system providers instructions for upgrading your operating system to the desired operating system revision. NOTE: If you are using Oracle to store NNM data, please see section 8.6, Relational Database Management System, for information on how to preserve your database installation when upgrading the operating system. 3. 4. 5. Whether upgrading your operating system or not, ensure that you have installed all operating system patches required for NNM 7.51. Refer the NNM 7.51 Release Notes (available online at http://ovweb.external.hp.com/lpe/doc_serv/). Upgrade to an NNM 7.x license key (see section 8.2 Licensing below). Install NNM 7.5, then install the NNM 7.51 Upgrade CD, as follows. Stop NNM in one of the following ways. o o Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Stop Use the %OV_BIN%\ovstop -c or the $OV_BIN/ovstop -c command.

Install NNM 7.5 using the NNM 7.5 CD set as described in the NNM 7.51 Installation Guide. If NNM was not started at the end of the installation, start NNM in one of the following ways. o o Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Start Use the %OV_BIN%\ovstart -c or $OV_BIN/ovstart -c command.

Migrate ET 2.0 data to NNM AE 7.5 To migrate ET 2.0 data to NNM 7.5, you must be migrating to NNM 7.5x Advanced Edition. To migrate your ET 2.0 data to NNM 7.5, run setupExtTopo.ovpl at this point. This is needed to pick up the latest extensibility changes, check requirements such as kernel parameters and number of managed nodes, and ensure any new MIBs are loaded. This setup script does more than just enable ET technology. It performs a number of configuration steps that may change between releases. After setupExtTopo.ovpl completes, invoke etrestart.ovpl to initiate a rediscovery. This makes the discovery data preserved from the previous installation accessible to the new version of NNM.

Stop NNM in one of the following ways. o o Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Stop Use the %OV_BIN%\ovstop -c or the $OV_BIN/ovstop -c command.

Install the NNM 7.51 update CD as described in the NNM 7.51 Installation Guide. If NNM was not started at the end of the installation, start NNM in one of the following ways in order to complete the migration to NNM 7.51. o Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Start 8

Use the %OV_BIN%\ovstart -c or $OV_BIN/ovstart -c command.

If you also have existing applications integrated with NNM, be sure to read section 8.12, Application Migration for End Users and section 8.13, Migration Information for Application Developers. NOTE: If you use the NNM Developer's Toolkit, you must install NNM 7.51 prior to installing the NNM 7.51 Developers Toolkit. See section 8.11, NNM Developer's Tool Kit.

4 Migrating from NNM 7.01 to NNM 7.51

4.1 Supported Migration Paths
Table 1 Supported Migration Paths to NNM 7.51 From Current Installation Version 7.01 7.01 On this platform HP-UX 11.0, 11.11 Solaris 2.8, 2.9 To NNM 7.51 On this platform HP-UX 11.0, 11.11, 11.23(1) Solaris 2.8, 2.9, 2.10 Win2000, WinXP(2), Win2003, Win2003 R2

7.01
(1) (2)

Win2000, WinXP

(2)

HP-UX 11.23 is supported on both PA-RISC and Itanium platforms. WinXP here is indicating Windows XP Professional or server. Windows XP Home is not supported.

NOTE: If you are upgrading your operating system in a direct migration scenario at the same time as you are migrating to a new NNM version, you must upgrade your operating system first, before you install NNM 7.5 followed by the NNM 7.51 Upgrade CD. Be sure to apply all necessary operating system patches as specified in the NNM 7.51 Release Notes (available online at http://ovweb.external.hp.com/lpe/doc_serv/). If you are migrating an Itanium system from NNM Starter Edition 7.01, NNM Starter Edition 7.5, or NNM Advanced Edition 7.5 in Aries mode to NNM Advanced Edition 7.51, refer to section 5, Migrating from NNM 7.01 or 7.5 to NNM 7.51 on HP-UX Itanium for important migration information. If you upgrade your operating system to Solaris 2.10, you must use the NNM 7.5 product CDs included in the NNM 7.51 product media kit to install NNM 7.5. The CD part numbers for the required Solaris CDs are T2489-15044 and T248915045. If you upgrade your operating system to Windows 2003 R2, you must use the NNM 7.5 product CDs included in the NNM 7.51 product media kit to install NNM 7.5. The CD part numbers for the required Windows CDs are T2489-15046 and T2489-15047.

4.2

NNM 7.01 to 7.51 Migration Steps

NOTE: If you have the OVPI/NNM Integration Module installed, you need to stop the ICO_RNS service before continuing. For more information see section 8.10.3, NNM 7.01 to NNM 7.5 or 7.51 migration fails if the OVPI/NNM Integration Module is installed. 1. 2. If your 7.01 deployment uses Overlapping Address Domains (also known as dupIP), back up $OV_CONF/nnmet/dupip. If you are upgrading your operating system at the same time as you are migrating to NNM 7.51, follow your operating system providers instructions for upgrading your operating system to the desired operating system revision. NOTE: If you are using Oracle to store NNM data, please see section 8.6, Relational Database Management System, for

information on how to preserve your database installation when upgrading the operating system. 3. 4. Whether upgrading your operating system or not, ensure that you have installed all operating system patches required for NNM 7.51. Refer the NNM 7.51 Release Notes (available online at http://ovweb.external.hp.com/lpe/doc_serv/). Install NNM 7.5, then install the NNM 7.51 Upgrade CD, as follows. Stop NNM in one of the following ways. o o Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Stop Use the %OV_BIN%\ovstop -c or the $OV_BIN/ovstop -c command.

Install NNM 7.5 using the NNM 7.5 CD set as described in the NNM 7.51 Installation Guide. If NNM was not started at the end of the installation, start NNM in one of the following ways in order to complete the migration to NNM 7.5. o o Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Start Use the %OV_BIN%\ovstart -c or $OV_BIN/ovstart -c command.

If using Extended Topology, re-enable ET by running $OV_BIN/setupExtTopo.ovpl. Do a full discovery (after this, incremental discoveries are fine). Stop NNM in one of the following ways. o o Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Stop Use the %OV_BIN%\ovstop -c or the $OV_BIN/ovstop -c command.

Install the NNM 7.51 update CD as described in the NNM 7.51 Installation Guide. If NNM was not started at the end of the installation, start NNM in one of the following ways in order to complete the migration to NNM 7.51. o o Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Start Use the %OV_BIN%\ovstart -c or $OV_BIN/ovstart -c command.

NOTE: If you use the NNM Developer's Toolkit, see section 8.11, NNM Developer's Tool Kit.

5 Migrating from NNM 7.01 or 7.5 to NNM 7.51 on HP-UX Itanium

Migration to NNM 7.51 on HP-UX Itanium is only supported from the October 2005 NNM release which supported both SE and AE on Itanium in native mode. NNM Starter Edition 7.01, 7.5 and 7.51 are supported on the Itanium platform with HP-UX 11.23 in native mode. At one time, NNM Advanced Edition 7.5 was supported in Aries dynamic translation mode only. As of October 2005, NNM 7.5 Starter Edition and Advanced Edition were both supported on the Itanium platform in native mode when installed with the October 2005 Itanium package. At that time, this install package was only available via the Web. As of the NNM 7.51 release, the October 2005 Itanium install package is shipped on the NNM 7.5 CDs included with the NNM 7.51 product. In order to migrate to NNM 7.51 from prior HP-UX Itanium releases, you must first migrate to the October 2005 NNM 7.5 Itanium release. You can then update your NNM 7.5 Itanium server to NNM 7.51 as described in section 6 below.

5.1

Migrating from NNM SE 7.0, SE 7.5 or AE 7.5 in Aries dynamic translation mode to NNM AE 7.5 in native mode on HP-UX Itanium

This subsection discusses migrating from prior deployments of NNM on the Itanium platform to the October 2005 Itanium release of NNM 7.5. 10

Before migrating from NNM SE 7.01, NNM SE 7.5, or NNM AE 7.5 in Aries dynamic translation mode to the October NNM 7.5 release, you must read the most recent NNM 7.5 Release Notes for important support information. This release notes file is available on the OpenView product manual Web site http://ovweb.external.hp.com/lpe/doc_serv/. The October 2005 NNM 7.5 Itanium release is shipped on the NNM 7.5 CDs included with the NNM 7.51 product. You can ensure that you have the correct install CDs by looking for October 2005 on the CDs to the left of the CD part numbers. Or, you can verify that the CD part numbers are T2489-15035 and T2489-15036. To determine if you have the October 2005 NNM native mode bits installed on your Itanium system, use the ovnnmversion command: /opt/OV/bin/ovnnmversion -v". The first two output lines should display as: 7.50 SE and AE If the line SE and AE is not displayed, you do not have the currently supported NNM bits installed on your Itanium system.

5.1.1

Migrating from NNM SE 7.01 or NNM SE 7.5 to the October 2005 NNM AE 7.5 Itanium release

The major steps in this migration process are: 1. 2. 3. Perform an operational data backup and an analytical backup (if needed) on the NNM SE system. Uninstall NNM SE. Install NNM AE 7.5. o a. b. As root, run ./install cd ../disk2/ run ./install

Note that the NNM AE 7.5 install archive includes patches up to and including Consolidated Patch 2. Do not install Consolidated Patch 2 or earlier patches on top of this NNM AE 7.5 installation. 4. 5. 6. 7. 8. 9. 5.1.1.1 1. 2. 3. Stop NNM. Restore your operational data backup and re-apply any customizations to config, registration, field, symbol and lrf files from your NNM SE 7.01 or SE 7.5 deployment. Restore your analytical backup if an analytical backup was performed. Restart NNM. Prepare to use NNMs Extended Topology by creating new tables for the NNM ET database (see section 5.1.1.1, step 12). Enable NNMs Extended Topology capabilities. Detailed migration steps Ensure environmental variables are set correctly per the $OV_BIN/ov.envvars.sh script. Perform a backup of your NNM SE operational data using the command ovbackup.ovpl -operational d <backup_path_old>, where <backup_path_old> is a path of your choosing. If you are using NNMs snmpCollect or Data Warehouse capabilities, perform an analytical backup using the command ovbackup.ovpl -analytical -d <backup_path>, where <backup_path> is any path name of your choosing. Uninstall NNM SE 7.01 or NNM SE 7.5. Install NNM AE 7.5. Note that the NNM AE 7.5 install archive includes patches up to and including Consolidated Patch 2. Do not install Consolidated Patch 2 or earlier patches on top of this NNM AE 7.5 installation. Stop NNM using the command ovstop -c. Perform an operational backup for your NNM AE 7.5 installation using the command ovbackup.ovpl operational d <backup_path_new>, where <backup_path_new> is a path of your choosing. 11

4. 5.

6. 7.

8. 9.

Replace <backup_path_new>/ovbackup/var with <backup_path_old>/ovbackup/var. This results in a backup directory <backup_path_new> where only the databases are from your NNM SE deployment. Compare the config, registration, field, symbol and lrf files in <backup_path_new>/ovbackup/etc/opt/OV/share with the same files in <backup_path_old>/ovbackup/etc/opt/OV/share. Re-apply any customizations from the NNM SE files to the NNM AE files. Also compare the files in <backup_path_new>/ovbackup/opt/OV/WWW and <backup_path_old>/ovbackup/opt/OV/WWW to determine if any customizations need to be re-applied.

10. Restore the final result of the merged SE and AE back-ups using the command ovrestore.ovpl -operational d <backup_path_new>. 11. If you performed a Data Warehouse analytical backup, restore the backup using the command ovrestore.ovpl analytical -d <backup_path>, where <backup_path> is the path you specified in step 3 above. 12. Restart NNM AE using the command ovstart -c. 13. Before enabling NNM AEs Extended Topology capabilities, you need to create new tables in the NNM ET database using the following commands. $OV_BIN/ovdwquery file $OV_CONF/analysis/sqlScripts/tables_TopoService.schema $OV_BIN/ovdwquery file $OV_CONF/nnmet/topology/schema/ovet_topo_create_view_1.schema
$OV_BIN/ovdwquery file $OV_CONF/nnmet/topology/schema/ovet_topo_create_view_upd_1.schema

14. Enable NNM AEs Extended Topology using the command $OV_BIN/setupExtTopo.ovpl.

5.1.2

Migrating from NNM AE 7.5 in Aries dynamic translation mode to NNM AE 7.5 in native mode

The steps in this process are very similar to those described for the migration of NNM SE 7.01 or 7.5 to NNM AE 7.51. The one change is in the parameters for the command used to restore your operational backup. The detailed migration steps are as follows: 1. 2. 3. 4. Ensure environmental variables are set correctly per the $OV_BIN/ov.envvars.sh script. Ensure that your Aries mode NNM AE deployment is updated to Consolidated Patch 2 or later, by installing PHSS_33662 or superseding patch. Perform a backup of your Aries mode NNM AE operational data using the command ovbackup.ovpl operational d <backup_path_old>, where <backup_path_old> is a path of your choosing. If you are using NNMs snmpCollect or Data Warehouse capabilities, perform an analytical backup using the command ovbackup.ovpl -analytical -d <backup_path>, where <backup_path> is any path name of your choosing. Uninstall the Aries mode deployment of NNM AE 7.5. Install the native mode version of NNM AE 7.5. Note that the install archive for the October 2005 Itanium version of NNM AE 7.5 includes patches up to and including Consolidated Patch 2. Do not install Consolidated Patch 2 or earlier patches on top of this NNM AE 7.5 installation. Stop NNM using the command ovstop -c. Perform an operational backup for your NNM AE 7.5 installation using the command ovbackup.ovpl operational d <backup_path_new>, where <backup_path_new> is a path of your choosing. Replace <backup_path_new>/ovbackup/var with <backup_path_old>/ovbackup/var. This results in a backup directory <backup_path_new> where only the databases are from your NNM AE Aries mode deployment.

5. 6.

7. 8. 9.

10. Compare the config, registration, field, symbol and lrf files in <backup_path_new>/ovbackup/etc/opt/OV/share with the same files in <backup_path_old>/ovbackup/etc/opt/OV/share. Re-apply any customizations from the NNM AE Aries mode files to the new NNM AE files. Also compare the files in <backup_path_new>/ovbackup/opt/OV/WWW and <backup_path_old>/ovbackup/opt/OV/WWW to determine if any customizations need to be re-applied. 11. Restore the final result of the merged Aries mode and native mode back-ups using the command ovrestore.ovpl 12

operational -aries d <backup_path_new>. (The -aries parameter specifies a restore from an Aries mode deployment to a native mode deployment.) 12. If you performed a Data Warehouse analytical backup, restore the backup using the command ovrestore.ovpl analytical -d <backup_path>, where <backup_path> is the path you specified in step 3 above. 13. Restart NNM AE using the command ovstart -c.

5.2

Completing your NNM 7.51 migration on HP-UX Itanium

After updating to the October 2005 NNM 7.5 Itanium release, you can update to NNM 7.51 as described in the next section.

6 Updating NNM 7.5 to NNM 7.51

Unless you migrate from NNM 7.5 under one of the Itanium scenarios described above, updating 7.5 to 7.51 is simple.

6.1

Supported Migration Paths

Supported Migration Paths to NNM 7.51 From Current Installation Version 7.5 7.5 On this platform HP-UX 11.0, 11.11, 11.23(1) Solaris 2.8, 2.9, 2.10 To NNM 7.51 On this platform HP-UX 11.0, 11.11, 11.23(1) Solaris 2.8, 2.9, 2.10 Win2000, WinXP(2), Win2003, Win2003 R2

7.5
(1) (2)

Win2000, WinXP , Win2003

(2)

HP-UX 11.23 is supported on both PA-RISC and Itanium platforms. WinXP here is indicating Windows XP Professional or server. Windows XP Home is not supported.

NOTE: If you are upgrading your operating system in a direct migration scenario at the same time as you are migrating to a new NNM version, you must upgrade your operating system first, before you install the NNM 7.51 Upgrade CD. Be sure to apply all necessary operating system patches as specified in the NNM 7.51 Release Notes (available online at http://ovweb.external.hp.com/lpe/doc_serv/). If you are migrating an Itanium system from NNM Starter Edition 7.01, NNM Starter Edition 7.5, or NNM Advanced Edition 7.5 in Aries mode to NNM Advanced Edition 7.51, refer to section 5, Migrating from NNM 7.01 or 7.5 to NNM 7.51 on HP-UX Itanium for important migration information.

6.2
1.

NNM 7.5 to 7.51 Migration Steps

If you are upgrading your operating system at the same time as you are migrating to NNM 7.51, follow your operating system providers instructions for upgrading your operating system to the desired operating system revision. NOTE: If you are using Oracle to store NNM data, please see section 8.6, Relational Database Management System, for information on how to preserve your database installation when upgrading the operating system.

2. 3.

Whether upgrading your operating system or not, ensure that you have installed all operating system patches required for NNM 7.51. Refer the NNM 7.51 Release Notes (available online at http://ovweb.external.hp.com/lpe/doc_serv/). Stop NNM in one of the following ways. Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Stop

13

 4. 5.

Use the %OV_BIN%\ovstop -c or the $OV_BIN/ovstop -c command.

Install the NNM 7.51 update CD as described in the NNM 7.51 Installation Guide. If NNM was not started at the end of the installation, start NNM in one of the following ways in order to complete the migration to NNM 7.51. Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Start Use the %OV_BIN%\ovstart -c or $OV_BIN/ovstart -c command.

7 Side-by-Side Migration to NNM 7.51

A side-by-side migration is a migration scenario where you bring up a new NNM 7.51 server and transfer database and configuration files from an existing NNM deployment over to the new server.

7.1

Supported Migration Paths

If Solaris 2.10 is the operating system on your new server, you must use the NNM 7.5 product CDs included in the NNM 7.51 product media kit to install NNM 7.5. The CD part numbers for the required Solaris CDs are T2489-15044 and T2489-15045. If Windows 2003 R2 is the operating system on your new server, you must use the NNM 7.5 product CDs included in the NNM 7.51 product media kit to install NNM 7.5. The CD part numbers for the required Windows CDs are T2489-15046 and T2489-15047. If your new server is an HP-UX Itanium system, you must use the NNM 7.5 product CDs included in the NNM 7.51 product media kit to install NNM 7.5. The CD part numbers for the required HP-UX CDs are T2489-15035 and T2489-15036.

A side-by-side migration to NNM 7.51 can be done for any version of NNM from 6.4x onward.

7.2

High-Level Migration Steps

Obtain a license key for your new NNM server. Backup the database and configuration files on your existing NNM server. Install NNM 7.51 on your new NNM server. Merge database and customization files from your existing NNM server with the files on your new NNM server and install the result onto your new NNM server using the ovrestore.ovpl utility.

7.3
1. 2.

Detailed Backup and Merge Steps

On your existing NNM server, ensure environmental variables are set correctly per the %OV_BIN%\ov.envvars.bat or $OV_BIN/ov.envvars.sh script. On your existing NNM server, perform a backup of your NNM operational data using the command ovbackup.ovpl -operational d <backup_path_old>, where <backup_path_old> is a path of your choosing. On your existing NNM server, if you are using NNMs snmpCollect or Data Warehouse capabilities, perform an analytical backup using the command ovbackup.ovpl -analytical -d <backup_path>, where <backup_path> is any path name of your choosing. On your new NNM server, install NNM 7.51 as described in the NNM 7.51 Installation Guide. On your new NNM server, stop NNM using the command ovstop -c. On your new NNM server, perform an operational backup for your NNM 7.51 installation using the command ovbackup.ovpl -operational d <backup_path_new>, where <backup_path_new> is a path of your choosing. On your new NNM server, replace the database files in <backup_path_new> with the database files in 14

3.

4. 5. 6.

7.

<backup_path_old>. This results in a backup directory <backup_path_new> where only the databases are from your prior NNM deployment. For the location of the database files within your backup directory structure, refer to Chapter 6 of the 7.5 Managing Your Network with HP OpenView Network Node Manager manual, particularly Table 6-1 and the paragraph that follows this table. (See section 1.4 above, NNM Documentation, for NNM documentation locations.) 8. On your new NNM server, compare the config, registration, field, symbol and lrf files in <backup_path_new> with the same files in <backup_path_old>. Re-apply any customizations from the NNM files in <backup_path_old> to the new NNM files in <backup_path_new>. For the location of these files within your backup directory structure, refer to Table 6-1 in Chapter 6 of the 7.5 Managing Your Network with HP OpenView Network Node Manager manual. (See section 1.4 above, NNM Documentation, for NNM documentation locations.) If you backed up analytical data files as discussed on page 153 of the 7.5 Managing Your Network with HP OpenView Network Node Manager manual, compare the appropriate files in <backup_path_new> and <backup_path_old> to determine if any customizations need to be re-applied. 9. If your new NNM server is a Unix system, ensure that you have brought forward NNM 7.51 changes to the Unix $ODBCINI file: o o On your new NNM server, compare $OV_NEW_CONF/OVDB-RUN/conf/analysis/system_odbc.ini to <backup_path_old>/ovbackup/$OV_CONF/analysis/system_odbc.ini. Place the merged results in the file <backup_path_new>/ovbackup/$OV_CONF/analysis/system_odbc.ini.

10. On your new NNM server, restore the final result of the merged new and old back-ups using the command ovrestore.ovpl -operational d <backup_path_new>. 11. If you performed a Data Warehouse analytical backup, restore the backup using the command ovrestore.ovpl analytical -d <backup_path>, where <backup_path> is the path you specified in step 3 above. 12. On your new NNM server, restart NNM 7.51 in one of the following ways in order to complete the migration to NNM 7.51. o o Use the Windows utility: Start Menu Program Files HP OpenView Network Node Manager Admin NNM Services - Start Use the %OV_BIN%\ovstart -c or $OV_BIN/ovstart -c command.

8 Additional Migration Considerations

8.1 Hardware and Software Requirements
For proper installation and operation of NNM 7.51, make sure all hardware and software requirements are met, including installation of any required patches, as well as performing any required kernel reconfiguration. The NNM 7.51 hardware and software requirements are included in the Release Notes (available online at http://ovweb.external.hp.com/lpe/doc_serv/).

8.2
8.2.1

Licensing
License Upgrade Information

Customers who have a license for NNM 6.x will need to acquire a new NNM 7.x license and password. NNM 7.x introduces a new licensing model, and as such, old NNM licenses will not be recognized. Since these licenses are not recognized and the product installs an unlimited node capacity license, a new NNM license will need to be obtained and installed prior to doing the migration to protect against nodes being unmanaged after 60 days.

8.2.2

Installing a Provided License

For customers with support contracts, a license has been provided. This license needs to be installed prior to doing the migration by using the following steps: 15

Save the license to a file. If on Unix, become the root user. Run the command ovnnmInstallLic [license file]. Verify that $OV_CONF/.license contains the license.

8.2.3

Requesting a License If None Provided

Pre-NNM 6.4x customers: WARNING: Do not try to enter the license at the text box as displayed by ovnnmPassword. ovnnmPassword has logic that recognizes the license is not known, and as such, it will not be accepted. You must save the license to a file and run ovnnmInstallLic for non-NNM 6.4 customers. Run ovnnmPassword and request a license for NNM 7.x. Now the license must be installed manually. Save the license to a file. If on Unix, become the root user. Run the command "ovnnmInstallLic [license file]". Verify that $OV_CONF/.license contains the license.

NNM 6.4x customers: WARNING: If you dont use the automatic license request and installation capability outlined below, you must enter the license manually from the command line following the instructions for pre-NNM 6.4x customers above. If on Unix, become the root user. Run ovnnmPassword and request a license for NNM 7.x. The license will be installed automatically. Verify that $OV_CONF/.license contains the new license.

For NNM 6.4x customers using a high availability (HA) environment, follow the steps for requesting HA licenses as documented in the NNM ServiceGuard whitepaper, and use the pre-NNM 6.4x steps since HA customers cannot fully request a license electronically. NOTE: The HP AutoPass installation program leads you through the licensing process. When installing NNM 7.5 or 7.51, you will be provided a GUI environment that will walk you through the process. Do not attempt to install licenses from the .license file. Licenses are generated directly from licfile.txt through the AutoPass program. You do not need to add them manually. If you attempt to add licenses manually, you will most likely run into problems. NOTE: NNM AE license is a superior license compared to NNM SE. This is true irrespective of the node count or type of license. So, any license check will first check for the presence of NNM AE and then NNM SE. Even if there is an NNM AE node pack license whose count is less than the NNM SE node pack, it will be assumed that the customer has done this deliberately. Also note that NNM SE Instant-On will not be available. One major exception to the superiority approach is when a customer purchases an NNM SE license while the AE Instant-On is still valid. In this case the following will happen: NNM functionality will use the node count obtained from the NNM SE licenses. NNM AEs ET functionality will work for the instant-on time period. NNM ET functionality will allow more than 250 nodes to be managed even though the AE Instant-On is for 250 nodes only. Node limit violation messages will continue to be generated.

If multiple license types of a product (SE or AE) exist on a system, then the overall node count will be the sum of the node counts provided by each license type. However, only one product type (AE or SE) will be considered in node counting. NNM does not mix product types for the purposes of counting licensed nodes.

16

8.3

NNM 7.51 DIM Information

Table 4 Management Station

NNM 7.51 AE

NNM 7.51 SE

NNM 7.5 AE

NNM 7.5 SE

NNM 7.01 AE

NNM 7.01 SE

NNM 6.2

NNM 6.4x

NNM 7.51 AE

Yes

No

Yes

No

No

No

No

No

NNM 7.51 SE Collection Station

Yes

Yes

Yes

Yes

No

No

No

No

NNM 7.01 AE

Yes

No

Yes

No

Yes

Yes

No

No

NNM 7.01 SE

Yes

Yes

Yes

Yes

Yes

Yes

No

No

NNM 6.4x

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

NNM 6.2

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

8.4

Remote Console Configurations

NNM 7.51 includes new Web-based Container Views, which also support background graphics and layout persistence. Consider using this superior new presentation technology, accessible in either a browser or as a Java Webstart application, instead of remote consoles. An NNM 7.51 remote console client must run the same version of NNM as the management station (server). For example, it is not possible to mix an NNM 6.x remote console with an NNM 7.51 management station server, or vice versa. NNM Starter Edition can be a remote console client only for a SE server. NNM Advanced Edition can be a remote console client only for an AE server.

17

Table 5 NNM 7.51 Remote Consoles If NNM 7.51 management station (server) is: HP-UX 11.0, 11.11 or 11.23 Solaris 2.8, 2.9 or 2.10 Then the NNM 7.51 remote console client can be: HP-UX 11.0, 11.11 or 11.23 Solaris 2.8, 2.9, or 2.10 Win2000, WinXP(1), Win2003 or Win2003 R2 Win2000, WinXP(1), Win2003 or Win2003 R2

(1)

Win2000, WinXP(1), Win2003 or Win2003 R2

WinXP here is indicating Windows XP Professional. Windows XP Home is not supported.

8.5

Migrating with Remote Consoles

An NNM 7.51 remote console client must run the same version of NNM as the management station (server). For example, using an NNM 6.2 or 6.4x remote console client with an NNM 7.51 management station (server) is not supported. It will be necessary to upgrade your NNM management station (server) to NNM 7.51 and ensure it is running properly prior to upgrading remote consoles. WARNING: Be sure remote consoles are not active during the upgrade procedure. Once the management station (server) has been upgraded to NNM 7.51 and verified to be properly running, upgrade the remote consoles to NNM 7.51. For installation and configuration of the management station (server) and the remote console, refer to A Guide to Scalability and Distribution (available with the NNM product and onlinesee section 1.4 NNM Documentation above).

8.5.1

UNIX Remote Console to UNIX Management Server

See the ovwsetupclient(1M) manpage for instructions on configuring HP OpenView Remote Consoles. A brief overview of the process is outlined below: 1. 2. 3. 4. Install the full version of NNM on the computer that will be the HP OpenView Management Server (UNIX). On the system to be an HP OpenView Management Server (UNIX), use NFS to export the /etc/opt/OV/share and /var/opt/OV/share directories to each HP OpenView Remote Console with full root access. You need to install NNM 7.51 on the remote console. On each HP OpenView Remote Console, insert NNMs installation CD, run ovwsetupclient, using the correct parameters to specify the location of the mounted directories exported in step #2 above. This will cause the Management Servers databases, log files, and local configuration files to be mounted on top of any databases, log files, or local configuration files on the Remote Console machine, in case you had previously installed the full version of NNM. You can now run NNM from the remote console as if you were working directly on the management station.

5.

8.6

Relational Database Management System

The use of Relational Database Management Systems (RDBMS) with NNM 7.51 has not changed from NNM 6.4x UNIX. Supported database information is detailed in the following sections. Note that it is possible to leave the existing 6.4x RDBMS in place and simply upgrade to NNM 7.51; no RDBMS changes are required. However, if you are going to perform an OS migration in addition to an NNM 7.51 migration, then follow the steps below: Upgrade to NNM 6.4x on the current OS. Upgrade the OS to the desired level.

8.6.1

Supported Relational Databases (Data Warehouse)

NNM 7.51 enables a data warehouse that uses standard SQL query language to RDBMS schemas. Three data sets may be exported to the data warehouse: snmpCollect data from the snmpCollect binary file

18

Event data from the Binary Event database Topology data from the ovtopmd database

Beginning with version 6.0, NNM delivers a data warehouse for use in conducting analytical activities such as generating reports. The data warehouse can store a duplicate copy of the data in NNMs native database. As a result of this new data store, NNM 6.x permits you to configure the data warehouse using either the embedded RDBMS system shipped with NNM or:
(1)

On Unix: Oracle(1) On Windows: Oracle or SQL Server(1) See NNM Release notes for exact DB versions supported

NOTE: An embedded database is installed by default during the installation of NNM 7.51; it is not user configurable during the installation process. However, after successful installation, you may convert the data warehouse from the embedded RDBMS to one of the supported external RDBMS. See the NNM Reporting and Data Analysis manual (available with the NNM product and onlinesee section 1.4 NNM Documentation above).

8.7

Existing NNM Configuration Items

Every effort has been taken to ensure that existing configuration items (loaded MIBs, SNMP configuration, event configuration, etc.) will be preserved during the upgrade. However, it is recommended that you back up these items prior to embarking on the migration process. See the man page for the ovbackup.ovpl command or the NNM Managing Your Network With OpenView Network Node Manager guide for more information on backing up existing configuration items.

8.8

Applications with Bitmapped Files

If an application that integrated with NNM prior to 6.2 uses custom bitmapped symbols, the symbols will not be properly displayed in the new NNM 7.51 Web Network Presenter user interface until a GIF version of the bitmap source files are placed in a new directory. The graphic files for the map symbols are now stored in two places, a directory used by NNM on the management station and a directory used by NNMs web-based interface. The web-based interface requires GIF files. GIF and other graphic file formats are supported on the management station: Current Location: $OV_BITMAP/$LANG/ Gif Location: $OV_WWW/htdocs/bitmaps/$LANG/ A contributed utility is provided that takes the bitmapped files used on the management station, creates equivalent GIF versions of these files, and places them in the directory used by the Network Presenter. Please note that the contrib directory containing these utilities is installed by default on UNIX. Look for the README file associated with the contrib/NNM/ImageMagik/convertBitmaps.ovpl utility for more information. To convert from bitmapped to GIF images: 1. 2. 3. Make sure you have sourced the $OV_BIN/ov.envvars.sh file. cd $OV_CONTRIB/NNM/ImageMagik. Run the command convertBitmaps.ovpl.

8.9

Changing Remote Database Management System

Install a new version of Oracle, Switch from using Oracle to using the embedded database or, Switch from using the embedded database to using Oracle.

After installing NNM 7.51 as described above, you will need to take further steps if you want to:

See the HP OpenView Network Node Manager Reporting and Data Analysis manual, chapter 4, Migrating Data Between Databases for the steps required to upgrade your database (available with the NNM product and onlinesee section 1.4 NNM Documentation above).

19

8.10 Known Issues

8.10.1 ovdbcheck may fail to start during startup
If you performed a side-by-side migration and did not bring forward the NNM 7.51 $ODBCINI changes as described in step 9 of section 7.3, Detailed Backup and Merge Steps, ovdbcheck may fail during start-up on a Unix system with an Oracle 10g NNM database. Workaround: Merge the contents of $OV_NEW_CONF/OVDB-RUN/conf/analysis/system_odbc.ini with the contents of $OV_CONF/analysis/system_odbc.ini. Place the merged result in $OV_CONF/analysis/system_odbc.ini.

8.10.2 ovw.auth & ovwdb.auth are overwritten

Resolution: Customers need to re-apply their customizations

8.10.3 NNM 7.01 to NNM 7.5 or 7.51 migration fails if the OVPI/NNM Integration Module is installed
This problem only applies to the Window platforms running the OVPI/NNM Integration Module on a NNM 7.01 installation. Note: The NNM 7.01 compatible OVPI/NNM Integration Module was available via the Reporting and Network Solutions (RNS) 5.0 CD. The RNS 5.0 OVPI/NNM Integration Module installs an ICO_RNS service that used the NNM-supplied Java runtime environment. During the NNM migration, this service continues to run while NNM 7.5 is attempting to install over NNM 7.01. This causes the NNM 7.5 installation to abort when it tries to install a new Java runtime environment while the Java runtime is being used by the active ICO_RNS service. Resolution: Stop the Windows ICO_RNS service prior to running the NNM 7.5 installation. If the installation error has already occurred, stop the ICO_RNS service and re-run the NNM 7.5 installation. The ICO_RNS service will have to be restarted after the NNM 7.5 installation has completed.

8.11 NNM Developer's Tool Kit

For most platforms (Solaris and Itanium excepted), the NNM Developer's Tool Kit (also known as NNM DevKit or SDK) has not undergone any changes in NNM 7.51. Customers should be able to run their applications on NNM 7.51 without any changes. However, if the applications have been compiled with certain compiler versions not supported in NNM 7.51, an explicit recompilation of applications would be required. NNM 7.51 on the HP-UX 11.23 Itanium platform was compiled using the 6.01 version of the native compiler. Applications compiled on Itanium in native mode using a cross compiler are not supported with NNM 7.51. In this case, an explicit recompilation of the applications is required. NOTE: The NNM DevKit version 4.11 is no longer supported. Applications developed with it may not work with NNM 7.51 or later. Of course, if the user application was compiled on an operating system or platform which is no longer supported by NNM 7.51, the application will require an explicit recompile for the new operating system on which NNM 7.51 is installed.

8.12 Application Migration for End Users

This section discusses from an end user perspective the migration of existing NNM 6.2/6.4x applications to NNM 7.51. Applications that run on HP-UX 11.x PA-RISC and Solaris 2.8, 2.9 or 2.10 operating systems will most likely work with NNM 7.51 on the same operating system.

8.12.1 OpenView Applications Compatibility with NNM 7.51

View NNM 7.51 Release Notes for latest OpenView Applications.

8.12.2 Third-Party Applications Compatibility with NNM 7.51

The release notes highlight some of our third-party applications that are compatible with NNM. For third party integrated applications, call your HP OpenView application provider to officially confirm whether their application has been installed, tested and certified with NNM 7.51 or check the 3rd party catalog at 20

http://www.openview.hp.com/partner/isv/index.jsp.

8.12.3 Data Migration

If your application places data into the ovw object database, this data gets migrated to the NNM 7.51 format the first time NNM 7.51s interface (ovw) is run.

8.12.4 Use of Remote Consoles

Applications designed for pre-NNM 6.x versions of UNIX Remote Consoles and UNIX Management Stations (servers) will most likely migrate to NNM 7.51 without customizations being required. Be sure to test your application within the NNM 7.51 environment.

8.13 Migration Information for Application Developers

The table below presents a high-level overview of when modifications may be required to run NNM 6.2 or NNM 6.4x applications on NNM 7.51: Table 6 Modification Required to Existing 6.2 Applications If NNM 6.2 Application Runs on HP-UX 10.20 HP-UX 11.x Solaris 2.6 Solaris 2.7 Solaris 2.8
1

It Should Run with NNM 7.51 on HP-UX 11.x PA-RISC HP-UX 11.x PA-RISC Solaris 2.8, 2.9 or 2.10 Solaris 2.8, 2.9 or 2.10 Solaris 2.8, 2.9 or 2.10

Modification Required No No Yes1 Yes1 Yes1

Modification Required to Use New Features Yes Yes Yes Yes Yes

NNM 7.51 uses different compilers on Solaris, which could be an issue in development.

Table 7 Modification Required to Existing 6.4x and ET 2.01 Applications If NNM 6.4x Application Runs on HP-UX 11.x Solaris 2.6 Solaris 2.7 Solaris 2.8
1 2

It Should Run with NNM 7.51 on HP-UX 11.x PA-RISC Solaris 2.8, 2.9 or 2.10 Solaris 2.8, 2.9 or 2.10 Solaris 2.8, 2.9 or 2.10

Modification Required Yes1 Yes2 Yes2 Yes2

Modification Required to Use New Features Yes Yes Yes Yes

NNM 7.51 uses different compilers on HP-UX 11.x, which could be an issue in development. NNM 7.51 uses different compilers on Solaris, which could be an issue in development.

NOTE: Only applications that are compatible with NNM 6.2, 6.31, or 6.4x can be migrated to NNM 7.51. You should verify that your application runs on NNM 7.51 via your own testing methods.

8.14 Compiler Issues

8.14.1 HP-UX PA-RISC considerations
The compilers used for HP-UX 11.x are different from those used for HP-UX 10.20; therefore applications intended to integrate 21

with NNM on HP-UX 11.x or later must be re-compiled using the HP-UX 11.x C/ANSI C or ANSI C++ available for HP-UX 11.0 and HP-UX 11.11.

8.14.2 HP-UX Itanium considerations

The cross compilers used in NNM SE 7.01 and the original NNM SE 7.5 on Itanium in native mode are different from the native compilers used for NNM 7.51 on Itanium in native mode; therefore, applications intended to integrate with 7.51 on Itanium must be re-compiled using the HP-UX 11.23 ANSI C++ 6.01 compiler.

8.14.3 Solaris considerations

The compilers used in NNM 7.51 on Solaris 2.8, 2.9 and 2.10 are different from those used in NNM 6.2; therefore applications that are to integrate with NNM 7.51 must be re-compiled using Forte Developer 6 update 2, available from Sun in the Forte Developer 6 for High Performance Computing package. See http://developers.sun.com/prodtech/cc/support/support_matrix.jsp#hpc for more details.

8.15 Upgrading NNM 6.2 or 6.4x Integrated Applications to NNM 7.51

The goal for NNM 7.51 is to be binary compatible with NNM 6.2 or 6.4x applications, so that unmodified NNM 6.2 or 6.4x binaries should run on NNM 7.51 with the same level of functionality. Following are some general guidelines for application migration to NNM 7.51: If your existing NNM 6.2 or 6.4x application runs on HP-UX 11.x or Solaris 2.8 or 2.9, then your application will most likely be backward compatible with NNM 7.51 with the same operating system. All applications developed using NNM 4.11 SDK must be recompiled using the latest supported devkit. Changes to existing 5.0x APIs are minor (additional parameters are supported). Several new APIs are shipped with NNM 6.x, but these should not cause backward compatibility issues. Changes to existing 6.x APIs are minor (additional parameters are supported). For source code backward compatibility for NNM 6.x to NNM 7.51, you can recompile NNM 6.x-based application code with no code changes; there is no need to include DOVwAPILevel=6 on the compiler line.

8.16 Installation
As in NNM 6.2 for UNIX, NNM 7.51 does not support ovinstall for installing NNM applications. Make a choice on installation; use Software Distributor, tar, or use your own installer.

8.17 Licensing
NOTE: A License Entitlement Certificate (a license) for a given version of NNM is a piece of paper that is evidence to the fact that the owner thereof has the right to use that version of NNM. NNM comes with a 60-day instant-on license. To run the software beyond 60 days, a permanent NNM password is needed to run the NNM software. Customers who do have a license for NNM 6.x will need to acquire a new NNM 7.x license and password. The NNM 7.x license may be obtained in one of three ways: 1. If the customer has an active HP Support Contract for NNM 6.2 or 6.4x, the customer will receive a letter asking them to reply back to HP with specific information. Next, HP will send the customer a password to log into the new migration web site. Then, the customer will retrieve their new NNM 7.x LTU from this web site. Finally, the customer will need to follow the license installation process in section 8.2 above. The customer can purchase an upgrade to NNM 7.51 from Hewlett-Packard and following the NNM 7.x licensing process to get a permanent password. NNM 7.51 can be bundled with an OEM solution and the OEMs end-user can get a permanent password in one of two ways: o o The OEM end user would follow the NNM 7.x licensing process to get a permanent password using the Entitlement Certificate. OEMs could obtain NNM permanent passwords and pass them on to their end users.

2. 3.

22

8.18 Data Stores

NNM 7.51 supports the following data warehouse RDBMS for Event, snmpCollect, and Topology data: On HP-UX: NNM-provided embedded RDBMS OR Oracle v8.1.7, v9.2.0.3 or Oracle for OpenView On Solaris: NNM-provided embedded RDBMS OR Oracle v8.1.7, v9.2.0.3 On Windows: NNM-provided embedded Oracle v8.1.7, v9.2.0.3 (only if ET is enabled) or SQL Server (SP3)

For detailed information regarding the schemas used for each of the three data sets, see the HP OpenView Network Node Manager Reporting and Data Analysis manual (available with the NNM product and onlinesee section 1.4 NNM Documentation above). NOTE: Beginning with version 6.0, NNM no longer supports RDBMS access to the real time operational topology data files. Access to this information is through the new data warehouse.

8.19 NNM 6.2 Object Database Port Number Change

Starting with NNM 6.2, the default port number in /etc/services for ovwdb has changed from 9999 to 2447. If your process connects to ovwdb, and you hard coded it to 9999, you will need to get the port number using getservbyname().

8.20 Integrating NNM 7.51 Features

This section assumes that you have migrated your existing application so that it was compiled with the NNM 6.2, NNM 6.31, or NNM 6.4x libraries and header files.

8.20.1 Modified APIs

Existing NNM 5.0x, and NNM 6.x APIs will work with NNM 7.51.

8.20.2 Internationalization
NNM 7.51 is internationalized. Because this feature impacts developers who produce applications for worldwide release, this information is presented here for your planning purposes. Beginning with the 5.0 releases, NNM internationalization was improved so that no special workarounds were necessary for multiple internationalized applications to run on localized versions of NNM. Furthermore, the Developers Toolkit has been enhanced to allow customers to produce localized versions of their applications using single source binaries. Developers can produce a single, internationalized version that runs with NNM 7.51 for all languages. Localized messages depend, of course, on the availability of message catalogs for the desired language. This new internationalization feature was implemented with backwards-compatibility in mind. However, the 4.x devkit is now obsolete. All 4.x applications must be recompiled with the latest supported version of the SDK. Although NNM applications later than 4.x require certain modifications, which are documented in the OVW Developers Guide (available with the NNM product and onlinesee section 1.4 NNM Documentation above). See chapter 10 in the OVW Developers Guide, Developing Internationalized and Localized Applications.

8.20.3 Running NNM 5.0x Applications on Remote Consoles with NNM 7.51
With the introduction of remote consoles in NNM 4.0, applications must be recompiled in order to run correctly on the remote console. The libovw will give your application the ability to transparently connect to the database on the management server. NNM 5.0x UNIX applications that correctly supported remote consoles (i.e., used OVwInitSession() instead of OVwInit()) require no additional code changes to work with NNM 7.51 remote consoles on UNIX.

8.21 Migration of Solid Database to Oracle Database

The HP OpenView Network Node Manager Reporting and Data Analysis guide is the main source for database-related information.

23

9 Migrating Existing Correlator Fact Stores

9.1 Migrating Correlator Stores to Composer version 3.32
NNM 6.4x included ECS 3.2 and NNM 7.51 uses ECS 3.32. The Composer factstore has changed format in ECS 3.32 version and consequently some manual migration steps are required to migrate Composer correlators. The 6.4x update installation of 7.51 will NOT overwrite the deployed Composer correlators ($OV_CONF/ecs/circuits/Composer.fs). This is to protect any customization that the user may have done to the out-ofbox correlators in the 6.4 product. The migration steps are as follows: 1. 2. 3. Save a copy of the Composer factstore to preserve any customizations that may have been done. (e.g., cd $OV_CONF; cp Composer.fs MyComposer.64.fs). After saving the correlators, you can now deploy the new 7.51 out-of-box correlators (e. g., $OV_BIN/csdeploy.ovpl or via the GUI: $OV_BIN/ovcomposer -m a Correlators Deploy). Migrate the original factstore to the new format in order to examine it for customizations (e. g., $OV_CONTRIB/ecs/csmigrate.ovpl MyComposer.64.fs -lang ENGLISH -o MyComposer.70.fs). Use the Composer development GUI to examine the original factstore for customizations and follow the processes documented in $OV_DOC/ecs/COMPOSER.pdf for creating correlators and namespaces to migrate those changes into the new factstore.

4.

24

 Copyright 1983-2006 Hewlett-Packard Development Company, L. P., all rights reserved.

December 2006
Last updated: 7 December 2006 http://ovweb.external.hp.com/lpe/doc_serv

25