HP OpenView Network Node Manager Release B.06.20 Runtime Release Notes

NNM Release B.06.20
May 08 2001
Copyright © 1990-2001 Hewlett-Packard Co., All Rights Reserved
Post-release updates to this document are available at
http://ovweb.external.hp.com/nnm/NNM6.2/relNoteUpd/relNoteUpdate.htm

Congratulations on your purchase of HP OpenView Network Node Manager 6.2 (NNM) for the Windows NT^® 4.0/Windows ^® 2000 operating system! HP OpenView Network Node Manager is the industry-leading network management solution, and we're proud to have you join the HP OpenView family. We thank you for purchasing HP OpenView Network Node Manager for Windows NT^® 4.0/Windows ^® 2000, and we hope this product exceeds your network management expectations.

We suggest that you use this document in conjunction with our two printed manuals (Managing Your Network with NNM and A Guide to Scalability and Distribution for Network Node Manager). The guidelines detailed below reflect the very latest information we have about the product, some of which was documented after the manuals were printed.

Installation Information

Before installing, please check that your system meets the Pre-Installation requirements.  This links to an online version of the insert included with your NNM installation CD.

Licensing

NNM comes with a 60-day password that is activated during installation. If installing NNM for the first time, only 250 managed nodes are allowed with the initial password. If you already have a previous version of NNM installed and licensed for unlimited managed nodes, unlimited nodes are allowed with the initial password. Before 60 days pass, you must request a permanent password even if you are upgrading from NNM 4.x or 5.x.  To request a permanent password, from the command prompt run ovnnmPassword, or pick [OK] when the NNM user interface prompts you to request your password.

It is advised that you request your permanent password immediately.

The following license types are the available for Network Node Manager 6.x:

• Windows NT and Windows 2000
• J1240AA HP OpenView Network Node Manager Enterprise 6.x (unlimited managed nodes)
• J1241AA HP OpenView Network Node Manager 250 6.x (250 managed nodes)
• J1242AB HP OpenView 250-Node Increment 6.x (additional 250 managed nodes)
• HP-UX
• J1247AA HP OpenView Network Node Manager Enterprise 6.x (unlimited managed nodes)
• J1248AA HP OpenView Network Node Manager 250 6.x (250 managed nodes)
• J1249AB HP OpenView 250-Node Increment 6.x (additional 250 managed nodes)
• SOLARIS
• J1254AA HP OpenView Network Node Manager Enterprise 6.x (unlimited managed nodes)
• J1255AA HP OpenView Network Node Manager 250 6.x (250 managed nodes)
• J1256AB HP OpenView 250-Node Increment 6.x (additional 250 managed nodes)

When you purchased your media and manuals, you purchased either an "HP OV NNM ENTERPRISE" or "HP OV NNM 250" product. If you bought the "HP OV NNM 250" product, you can increase the initial 250 managed nodes by purchasing any number of "HP OV NNM 250 NODE INCREMENT" products.

If you want to run HP OpenView Remote Consoles, you do not need an additional  license or password for each remote console as long as the HP OpenView Management Server has a valid password.

If you change the IP address of your management station, you will need to request a new password. Fill in the form:
\Program Files\HP OpenView\NNM\conf\OVLicense\forms\nnm\C\server_move.txt

Using Node View/CDP View

Node View and CDP (Cisco Discovery Protocol) View allow you to view collections of nodes through your web browser.  They use a combination of Java and XML to allow you to view nodes from any browser that supports the Java Plug-in (JPI) version 1.2 or later.  You can access them through ovw's Tools:Node View or Tools:CDP View.  For instructions on how to obtain the latest version of the JPI, see the links in Supported Configurations.

Using the Reporting System

You can easily configure NNM to generate HTML-based reports.  By specifying the type of report, NNM will automatically configure data collection, and automatically generate daily and/or monthly reports.  The system can optionally mail these reports to any one in your organization.  You can configure or view the reports with your web browser.  For more information, launch the configurator using ovw's Options:Report Configuration.  You can view the reports using ovw's "Tools:Report Presenter".  Reports are generated the day following data collection, so you can expect to see reports the next day after configuration.

Using the Event Correlation Services

The Event Correlation Service (ECS) is integrated into NNM such that events are routed through the ECS engine before they are distributed to applications, such as NNM's Alarm Browser.  This allows correlations to prevent extraneous events from overwhelming the application or network administrator. For more information, see Managing Your Network with NNM.

The following event correlations are included in NNM:

• Connector Down
  Distinguishes between physical failures of network devices and failures that are due to a connector device failure (e.g. router), and presents this distinction on the map and in the Alarm Browser.
• Repeated Event
  Allows multiple alarms which are associated with a single physical event to be bundled together and replaced by a single alarm in NNM's Alarm Browser, reducing the network administrator's information overload.
• Scheduled Maintenance
  Allows network administrators to configure the event correlation system to suppress event storms during periods where portions of the network are down for routine maintenance
• Pair Wise
  Allows an event to delete or acknowledge one or more related alarms in the Alarm Browser (for example, a node up alarm to cancel out a node down alarm). You can configure other paired events in addition to the default settings.
• Manage-X Connector Down
  Allows correlation of events between HP OpenView Network Node Manager and HP OpenView Manage-X systems.

For detailed descriptions of each correlation, bring up the ECS Config/Management GUI:

1. Open the NNM user interface and select Options:Event Configuration.
2. Select Edit:Event Correlation.
3. Highlight any correlation and click the Describe... button.

Additional correlations can be developed by purchasing and using the HP OpenView ECS Designer product.

Using the Data Warehouse System

NNM comes with an embedded SQL data warehouse database that supports ODBC queries. See the Reporting and Data Analysis with Network Node Manager manual for complete information. The list of currently supported databases is in the Supported Configurations section.

To export NNM's topology, event, or SNMP collected data into the data warehouse, either:

• Open the NNM user interface and select Tools:DataWarehouse->Export Topology, Tools:DataWarehouse->Export Events, or Tools:DataWarehouse->Export Trends.
• From the command prompt run ovdwtopo, ovdwevent, or ovdwtrend.

See the ovdwtopo, ovdwevent, and ovdwtrend reference pages in NNM's online help (or the UNIX manpages) for details about these commands. For maintenance of the data warehouse, these commands support query, aggregate, and trim parameters.

See also the ovdwquery reference page in NNM's online help (or the UNIX manpage) for more information.

You can access the data warehouse information using your favorite ODBC tools. The database schemas are described in a series of ASCII files in the \Program Files\HP OpenView\NNM\conf\analysis\sqlScripts  directory.  See tables_topo.solid (topology schema), tables_event.solid (event schema), or tables_trend.solid (SNMP collected data schema).

Using the HP OpenView Java-Based Web Interface

Using any JDK 1.1 compatible browser you can connect to your NNM management station through NNM's Launcher. You can view topology, alarms, node status, and browse MIBs. NNM's user interface must be running on the management station with the desired map displayed. See Managing Your Network with NNM for information about NNM's new web interface.

The HP OpenView Java-based Web Interface is available at URL:

• http://<MACHINENAME>/OvCgi/ovlaunch.exe (to access an NNM  management station running on Windows NT/2000)
• http://<MACHINENAME>:8880/OvCgi/ovlaunch.exe (to access an NNM  management station running on UNIX)

NNM's web version of the mapping feature is called the Network Presenter. When you access the Network Presenter, a list of submaps is shown in the left scoping pane. In the right scoping pane, you view the selected submap in graphical or tabular format.

You can integrate your own choice of management URLs into NNM's Java-based web interface. See the LauncherRegIntro reference page in NNM's online help (or the UNIX manpage) for more information.  See also Managing Your Network with NNM and Creating and Using Registration Files.

The NNM Java-based grapher is available as a contributed application (not supported by HP).  This tool allows you to view the equivalent of NNM's Graph SNMP Data feature (xnmgraph) over the web.  See \Program Files\HP OpenView\NNM\contrib\NNM\javaGrapher\README.txt (you must run a "Custom" install to get contributed program files)  for more information.

The server processes for the HP OpenView Java-Based Web Interface can be located on an HP OpenView Remote Console to offload the management server.  For more information see the Microsoft word document  <DRIVE>:\doc\WhitePapers\WebUIFromRemoteConsoles.doc located on your CD-ROM.

By default, the HP OpenView Java-Based Web Interface has most security mechanisms disabled.  You can enable launcher login by turning on the UserLogin parameter in $OV_CONF/www/session.conf.  You can also enable user roles. For more information see Managing Your Network with NNM. You can control operations which may be performed through the web-based Alarm Browser with options to the ovalarmsrv daemon.  For more information see the ovalarmsrv reference pages.

Configuring Discovery with Custom Installation

See Managing Your Network with NNM, Chapter 5 for information about the choices available for customizing and troubleshooting NNM's discovery process.

If you wish to delay the discovery process until after you decide which configuration choices to implement:

1. During installation choose "Custom" in the Setup options dialog.
2. When you get to the dialog box titled "Configure Discovery Options," uncheck "Start network auto-discovery after installation". This will prevent Network Node Manager from starting network auto-discovery. 

When you are ready to run discovery, open NNM's user interface and select Options:Network Polling Configuration. Then enable the IP Discovery:Discover new IP nodes  field. Also, enable the IPX Discovery:Discover new IPX nodes field.

Configuring for HP OpenView Remote Consoles

HP OpenView Remote Consoles allow full-featured access to NNM on the management station from multiple computers. The NNM management station becomes the HP OpenView Management Server and runs the services or background processes that perform network monitoring and maintain the databases.  The HP OpenView Remote Consoles need only install and run the NNM user interface or foreground processes.  This allows more users to simultaneously use one copy of  NNM without needing to start multiple instances of NNM on the management station. See A Guide to Scalability and Distribution for Network Node Manager for more information. (Remote consoles do not run across the WWW.)

If you want to run HP OpenView Remote Consoles, you do not need a license for each computer. A license is only needed for the NNM management station serving as the central HP OpenView Management Server. However, the HP OpenView Management Server and any HP OpenView Remote Consoles must be upgraded to the same version of NNM.

NOTE: If it becomes necessary to modify the port numbers used for various NNM services on the management station, you must modify the port numbers for the corresponding services used on all remote consoles connected to that management station.

The server processes for the HP OpenView Java-Based Web Interface can be located on an HP OpenView Remote Console to offload the management server.  For more information see the Microsoft word document  <DRIVE>:\doc\WhitePapers\WebUIFromRemoteConsoles.doc located on your CD-ROM.

There are three possible configurations:

• Management server (Windows NT/2000) for remote consoles (Windows NT/2000)
• Management server (UNIX) for remote consoles (Windows NT/2000)
• Management server (UNIX) for remote consoles (UNIX)

NOTE: Management server (Windows NT/2000) for remote consoles (UNIX) is not supported.

Management station (Windows NT/2000) for Remote Consoles (Windows NT/2000)

1. First install the full version of NNM on the computer that will be the HP OpenView Management Server (Windows NT/2000).
2. NOTE: It is required that the HP OpenView Management Server's IP name match it's computer name (Net BIOS name) so that HP OpenView Remote Consoles can properly communicate with the HP OpenView Management Server.
3. Start NNM on the HP OpenView Management Server (Windows NT/2000) and verify correct operation:
• On the system to be an HP OpenView Management Server, share the \Program Files\HP OpenView NNM\ directory (where \Program Files\HP OpenView\NNM\ is your NNM installation directory). Do this with Windows Explorer using a right mouse click. Give the users "Full Control" access.
• On the system to be an HP OpenView Remote Console, verify that you can connect to the shared \Program Files\HP OpenView\NNM\ directory. Do this using Windows Explorer. You may need to log into a shared domain or mount the remote drive (if in a different domain). Verify the connection via the following command from a command prompt:
      dir \\SERVERMACHINE\OpenView
  where SERVERMACHINE is the name of the machine acting as an HP OpenView Management Server)
4. On each HP OpenView Remote Console system, insert the NNM installation CD and run setup.exe and pick the "Remote Console Installation". This will remove any databases, log files, or local configuration files, if you had previously installed the full version of NNM. Supply the machine name of the HP OpenView Management Server and the default share name "OpenView".

NOTE: On HP OpenView Remote Consoles, ovstop and ovstart must be run from the command prompt, and you must explicitly name which services to startup or shutdown.

You can now run NNM from the remote console as if you were working directly on the management station.

Management station (UNIX) for Remote Consoles (Windows NT/2000)

You need to buy a third party NFS product that runs on the Windows NT/2000 operating system and install it on each system to be an HP OpenView Remote Console.  See the supported configurations for information on which NFS packages are supported.

• Intergraph DiskAccess (works with the minimum amount of additional configuration)
• WRQ NFS
• Hummingbird Maestro
• FTP Software 4.0 or later (Version 3.0 has a known file locking problem)

1. First install the full version of NNM on the computer that will be the HP OpenView Management Server (UNIX).
2. Start NNM on the HP OpenView Management Server (UNIX) and verify correct operation:
• On the system to be an HP OpenView Management Server, export the /etc/opt/OV/share and /var/opt/OV/share directories through NFS to each Remote Console with full root access.
• On each system to be an HP OpenView Remote Console (Windows NT/2000), use your NFS software on the PC Remote Console to map the UNIX directories. Do this using Windows Explorer's "Map Network Drive" function. Be sure to consult your NFS software documentation about how to "enable locking".  It is suggested that you map the UNIX /etc/opt/OV/share filesystem as user root to drive letter G: and the UNIX /var/opt/OV/share filesystem as user root to drive letter H:.
3. On each HP OpenView Remote Console system, insert the NNM installation CD and run setup.exe and pick the "Remote Console Installation". This will remove any databases, log files, or local configuration files, if you had previously installed the full version of NNM. Supply the two mapped drive letters.

NOTE: On HP OpenView Remote Consoles, ovstop and ovstart must be run from the command prompt, and you must explicitly name which services to startup or shutdown.

You can now run NNM from the remote console as if you were working directly on the management station.

Management station (UNIX) for remote consoles (UNIX)

See the ovwsetupclient(1M) manpage for instructions about configuring HP OpenView Remote Consoles.

1. First install the full version of NNM on the computer that will be the HP OpenView Management Server (UNIX).
2. On the system to be an HP OpenView Management Server (UNIX), export the /etc/opt/OV/share and /var/opt/OV/share directories to each HP OpenView Remote Console.
3. On each HP OpenView Remote Console, install the full version of NNM by running ./install.
4. On each HP OpenView Remote Console, run ovwsetupclient.

NOTE: On HP OpenView Remote Consoles, ovstop and ovstart must be run from the command prompt, and you must explicitly name which services to startup or shutdown.

You can now run NNM from the remote console as if you were working directly on the management station.

Configuring as an HP OpenView Collection Station

An HP OpenView Collection Station runs a complete copy of NNM,  monitors its own designated portion of your network, and forwards topology and alarm information to the central NNM management station. The central management station that is receiving information from HP OpenView Collection Stations must be running NNM 4.1 or greater.  The central NNM management station must have an HP OpenView Network Node Manager Enterprise license. Each collection station must have its own NNM license. To learn more about Distributed Internet Data Monitoring (DIDM), refer to the A Guide to Scalability and Distribution for Network Node Manager manual.

There are four possible configurations:

• Collection station (Windows NT/2000) to central NNM management station (Windows NT/2000)
• Collection station (Windows NT/2000) to central NNM management station (UNIX)
• Collection station (UNIX) to central NNM management station (Windows NT/2000)
• Collection station (UNIX) to central NNM management station (UNIX)

Configure an SNMP SET-community name for each  HP OpenView Collection Station:

• On each HP OpenView Collection Station, modify the  \Program Files\HP OpenView\NNM\conf\SNMPAgent\snmpd.conf file (where \Program Files\HP OpenView\NNM\ is your installation directory) Remove the comment near the bottom of the snmpd.conf file and enter a value for the set-community-name field.
• On the central NNM management station, open NNM's user interface and select Options:SNMP Configuration. Enter the SET-community name or names in the dialog box.

On the central NNM management station:

• To determine which HP OpenView Collection Stations are configured and available for use, run the xnmtopoconf -print command.
• To begin using an HP OpenView Collection Station  in your DIDM scheme, run the xnmtopoconf -manage command.
• To notify the central NNM management station of the existence of a new OpenView Collection Station, run the xnmtopoconf -add command.

See the xnmtopoconf reference page in for more information. 

Microsoft Management Console Snap-in

(Windows NT/Windows 2000 Only) You can install the Microsoft Management Console (MMC) snap-in on any Intel-based Windows NT/2000 computer.  With the snap-in you can launch the native NNM (if installed locally), or launch NNM's web-based interface.  To install, run the \mmc\ovnnmsnapin.exe which resides on your CD-ROM.  For more information on the MMC snap-in, see the \doc\WhitePapers\NNMManageXInteg.pdf file on your CD-ROM.

Improving Performance

You can improve the performance of your NNM management system in several ways.  See also the latest version of the HP OpenView Performance and Configuration guide which is available at:
    http://ovweb.external.hp.com/lpe/doc_serv/. From this URL, choose the Product Network Node Manager. Choose a Release. Select the Performance and Configuration Guide.
Some ways of improving your performance include:

1. Ensure that your management station does not swap memory.
   (Windows NT/Windows 2000 Only) You can monitor how much swapping is being done via the Windows NT/2000 Programs:Administrative Tools->Performance Monitor.
   Pick Edit:Add to Chart.
   Select Object:Memory,  Counter:Available Bytes, and click Add, then Counter:Pages/sec and click Add.
   This graph will help you determine how much memory you are using, and if you are low on memory.
   • You can improve Windows NT/2000 operating system's swap performance by correctly configuring the initial paging file size (see discussion below).
   • Install enough memory. Generally performance per dollar is better spent on RAM than CPU speed. Performance will likely improve with additional physical RAM.  If other applications are running at the same time as Network Node Manager, or if many nodes are managed, more memory will be needed for optimum performance.
2. (Windows Only) Check your tasking model and ensure that foreground processes have highest priority.
   From Settings:Control Panel, open the System applet. Pick the "Performance" tab. Ensure that the slider in on Maximum (Windows NT/2000's default).
3. Install a high quality video card.
   NNM is a very graphical application. Fast video cards will allow operations like panning and zooming on the map to perform better.
4. Enable maximum throughput.
   If you are running the Windows NT/2000 Server software, from Settings:Control Panel, open the Network applet. Pick the "Services" tab. Select "Server" and pick "Properties". Enable the Maximize Throughput for Network Application field.
5. Reduce DNS and NETBIOS lookup delays.
   See Improving Name Service Performance below.
6. Use a caching name server on the NNM management station to reduce network traffic and time required for name lookups.
7. Customize polling intervals to reduce the amount of network traffic used
   See Chapter 6 in Managing Your Network with NNM for more information.
   • Adjust status polling intervals for less important nodes. This is done using "Options->SNMP Configuration"
   • Adjust discovery, configuration, and connector topology polling intervals to be less frequent
   • Modify the number of simultaneous ICMP, IPX (Windows NT/2000 only), and SNMP requests made by netmon by modifying its -q, -x, and -Q command-line startup options (see also the netmon reference page for specific details).
8. Customize discovery options to eliminate or reduce the amount of network traffic used.
   See Chapter 5 in Managing Your Network with NNM for information.
   • use the netmon.noDiscover file to exclude specified nodes
   • use a discovery filter to specify which nodes will or will not be included
   • use the loadhosts program to include only listed nodes
   • modify the oid_to_type file to unmanage specific types of nodes

A good discussion on tuning your Windows NT system can be found on the Microsoft TechNet CD entitled "Optimizing and Tuning of Windows NT" by Scott B. Suhy. This discusses using Performance Monitor and optimizing your memory, processor, and I/O system resources. This article also talks about how to use Perf2Mib.EXE to instrument these values for SNMP so that NNM can monitor the variables. Additional information can be found in the NNM Performance and Configuration Guide, which is located on NNM's installation CD in doc\WhitePapers\perfGuide.wri.

You can improve Windows NT/2000 operating system's swap performance by correctly configuring the initial paging file size, you will get better performance than if Windows NT/2000 needs to grow the paging file. If you have multiple hard disks, splitting up the paging file is a good idea, as it will speed up the access time. If you have two hard disks, and you split the paging file, both hard disks can be accessing information simultaneously, greatly increasing the throughput. However, if you have two hard disks, and one hard disk is faster than the other, it may be more effective to store the paging file on only the faster hard disk. Some experimentation may be necessary to arrive at the best configuration for your system.

NOTE: There is no point in splitting up the paging file between multiple partitions of the same disk as it does not increase the ability of the hard disk to access the paging file. This may be a good idea, however, if your logical drives aren't large enough for the entire paging file.

A good guideline for virtual memory paging file size is to have double the size of your physical memory. For example: RAM=128MB paging file=256MB. If you don't have a large amount of RAM, it may be useful for the paging file to be four times the size of your existing RAM. 

Improving Name Service Performance

• NameSrvQueryCount (default=3)
  Consider reducing this value (you can disable NETBIOS queries to WINS with a value of 0).
• NameSrvQueryTimeOut (default=1500)
  Consider reducing this value (which is the number of milliseconds successive name queries to WINS), especially with a local name server configured.
• NodeType (default=1 or 8 based on WINS server configuration).
  A value of 2 will disable broadcasts and allow for point-to-point queries to WINS.

For complete details about configuring these parameters, see the Microsoft TechNet article "Microsoft Windows NT 3.5, 3.51, 4.0 - TCP/IP Implementation Details". 

In certain situation you can improve name resolution by changing the hostname resolution order between DNS and NetBIOS over TCP/IP (NetBT) name resolution mechanisms.

In order to change the hostname resolution order (between DNS and NetBT name resolution mechanisms), change the “DnsNbtLookupOrder”  to 1 or 0.  The default value is 0.  A value of 1 causes NetBT name resolution to be attempted before DNS.  Note that this subkey doesn't exist by default, so you must create it in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters Registry key (See Windows® NT® 4.0 ServiceProvider Priority Values Not Applied  Article ID: Q171567). Exit the Registry Editor and restart the computer for the change to take effect.

Changing Name Resolution Order on Windows® NT®

The following four registry subkeys control the relative priority of using the local name cache, the HOSTS file, DNS, and NetBT name-resolution methods (including WINS), respectively (similar to the nsswitch file on Unix). The values can range from -32768 to 32767 (lower numbers specify a higher priority) with the following default values (in decimal!). 

These values explain the Windows® NT® client's preference for DNS (e.g., DnsPriority = 2000) over WINS (e.g., NetbtPriority = 2001).  You can simply reorder the values so that DNS has a higher value (and thus a lower priority) than NetBT and WINS.  For additional information, please see the following article in the Microsoft®  Knowledge Base:  Q170619.

The above motioned registry entries are located on the following registry path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ServiceProvider.

Disabling NetBios over TCP/IP

(Windows 2000 only) DNS is used as the name locator service in Windows® 2000. This means you must have DNS servers implemented on your network if you want to connect to resources other than by specifying their IP address.  In Windows® 2000 NetBIOS over TCP/IP is enabled by default. You can disable NetBIOS over TCP/IP by using the Advanced TCP/IP settings box.

Note that if you disable NetBIOS over TCP/IP you won't be able to restrict a user's access to specific workstations using the Account tab of the property sheet for the user account since this feature requires NetBIOS over TCP/IP in order to work.

Online and Printable Documentation

NNM includes a library of detailed reference materials for your use. They are shipped as Adobe's Portable Document Format (.pdf) files, and viewed through your web browser.  Adobe's Acrobat Reader can be installed from http://www.adobe.com/products/acrobat/.  If you are installing on a Unix browser, be sure to read Adobe's knowledge base article #317421, available at http://www.adobe.com/support/techdocs/142ba.html, which documents how to install the plug-in into your Unix browser. You can use Netscape's Help:About Plug-ins to see which plug-ins are enabled.  For Japanese browsers, be sure to download the Acroread ASIAN Font Pack. from http://www.adobe.com/products/acrobat/acrrasianfontpack.html.

The following manuals are provided with NNM, and are available from the Help menu of ovw, or in the $OV_WWW/htdocs/LANG/manuals directory.  They can also be accessed through NNM's web server at a URL like:
http://<MACHINE_NAME>:<PORT_NUMER>/OvDocs/C/manuals/Welcome_to_NNM.pdf.

• HP OpenView Network Node Manager Installation Quick Start
  This book contains instructions about installing and configuring NNM.
• Welcome to Network Node Manager
  An overview of NNM, its features, and its capabilities.
• Managing Your Network with NNM
  This book contains detailed information to help network administrators configure, maintain, and troubleshoot NNM for their team.
• Reporting and Data Analysis with Network Node Manager
  This book contains information about configuring and using NNM’s data warehouse feature. This book also contains information about how to export the historical data collected by NNM for your use with other statistical analysis programs of your choice.
• Creating and Using Registration Files
  This advanced book contains information about how to create and modify NNM’s registration files, customizing the appearance and behavior of NNM.
• A Guide to Scalability and Distribution for Network Node Manager
  This advanced book outlines the steps you need to take to deploy NNM across multiple management stations within your organization. It contains specific configuration procedures for using the scaling and distribution features of NNM. These features are important when the size of your organization’s network exceeds the resources of one NNM management station. They allow you to divide the work load among multiple management stations, yet share the network management information as needed.

Numerous additional HP OpenView online manuals are available at the following web site:

• http://ovweb.external.hp.com/lpe/doc_serv/ (for Adobe Acrobat .pdf documents)

"Get Acquainted with HP OpenView Network Node Manager" CBT

Included with your NNM product is a separate CD-ROM, entitled Get Acquainted with HP OpenView Network Node Manager: Training for NNM Operators.

All new users are encouraged to take advantage of this convenient and focused computer-based training (CBT) to acquire essential expertise with the NNM software. Build the foundation concepts and skills you need, develop a broad understanding of NNM's functionality and operation, and learn the basic tactics of fault identification and isolation.

Just follow the easy installation instructions on the CD sleeve.  This CBT runs under reasonably current versions of any Microsoft Windows operating system (excluding Windows 3.x).

For in-depth information about administrative and advanced tasks (such as configuration or customization), see the NNM documentation.  Also, explore NNM's extensive online help system for information about specific tasks and procedures.  Comprehensive classroom training on NNM is regularly available; visit http://openview.hp.com/training/ for detailed information and schedules.

Recommended Paging Software

Network Node Manager now offers improved integration with Telamon’s Telalert automated notification software for alerting and remote management.

Follow http://ovweb.external.hp.com/nnm/paging for details to download the TelAlert product that fits your needs.

Telamon provides all customer support for their products.

Uninstalling (and Manual Product Removal)

If you only want to repeat initial discovery, you can remove only your topology databases and re-discover. See Chapter 5 of Managing Your Network with NNM for instructions.

To fully uninstall the product:

• Close the NNM user interface by exiting ovw
• If you have the Network Node Manager SDK installed, uninstall it first. Select Programs:HP OpenView:Network Node Manager Admin->Uninstall HP OpenView SDK. Optionally use the 'remove software' menu from the Control Panel's "Add/Remove Programs" icon.
• Select  Programs:HP OpenView:Network Node Manager Admin->Uninstall Network Node Manager. Optionally use the 'remove software' menu from the Control Panel's "Add/Remove Programs" icon.

To be completely sure you have removed everything, in the event your uninstall was unsuccessful, you can follow the manual removal instructions.

Migration from Past Versions

You can migrate directly from NNM 4.11, NNM 5.x, or NNM 6.x to NNM 6.2.   Hewlett-Packard recommends that you backup your system and have the latest patches for your release before migrating to NNM 6.2 .

Note that the behavior of automatic actions have changed to use ovactiond Trusted Commands, which can cause automatic actions to be disabled until they are explictly enabled.  For more information, see the ovactiond reference page.

Compatibility with Other OpenView and 3^rd Party Applications

Network Node Manager 6.2 has been tested with the current version of many third-party OpenView applications. Most of the tested applications work on NNM 6.2 just as they do on NNM 4.11 and/or NNM 5.01 without any change. 

HP OpenView Customer Views

HP OpenView VantagePoint Operations (Formerly ITO)

NNM 6.2 is compatible with VPO 5.3 and VPO 6.0. When migrating the NNM component of VPO to NNM 6.2, a normal NNM update is performed using the NNM 6.2 "install" script. In order to maintain proper support levels for NNM, VPO customers may be required to migrate to NNM 6.2. See HP OpenView VantagePoint Operations (VPO, formerly ITO) and NNM Installation Notes for further information on migrating the NNM component of VPO to NNM 6.2.

HP OpenView ECS Designer

ECS Designer 3.1 should be used on systems with NNM 6.2. NNM will not operate correctly if ECS Designer 3.0 is installed on the same system.  NNM 6.2 can load and run circuits (.eco files) that have been developed using ECS Designer 3.0 or ECS Designer 3.1 and can utilize new features available with ECS Designer 3.1.

VPO/ITO can load and run circuits (.eco files) that have been developed using ECS Designer 3.0 or ECS Designer 3.1. However, VPO/ITO versions 6.0 or older will generate an error and fail to load circuits developed with ECS Designer 3.1 if the circuits make use of any of the new ECS feature "Generation of Multiple events using CreateNode".

HP OpenView Vantage Point Internet Services (VPIS)

VPIS installs its own version of ov.dll, ovsnmp.dll, ovutil.dll, and ovw.dll in c:\rpmtools\bin.  These conflict with the newer versions shipped with NNM.  You can either copy the newer NNM 6.2 version to c:\rpmtools\bin or delete the versions in c:\rpmtools\bin.

HP OpenView PolicyXpert

PolicyXpert  installs its own version of ov.dll and ovsnmp.dll.  These conflict with the newer versions shipped with NNM.  You can either copy the newer NNM 6.2 version to the PolicyXpert install directory, or delete them.  If you uninstall NNM, you must re-install PolicyXpert, because NNM deletes the shared registry keys.

HP-UX Service Guard

Network Node Manager on HP-UX supports MC/Service Guard. See the white paper, located in /opt/OV/doc/WhitePapers/MCServiceGuard.doc

Join the OpenView Forum User's Group

The OpenView Forum is an association of users and developers of OpenView network and system management solutions. OpenView Forum was formed as a non-profit corporation by four of the largest licensees of HP OpenView (Duke Power, GTE Government Systems Corporation, Martin Marietta and US WEST) to represent the interests of OpenView users and developers world-wide.

If you are an OpenView end user or developer, OpenView Forum is your voice to vendors of OpenView products. Become a member and make sure that OpenView vendors listen to your requirements. OpenView Forum is your advocate.

For more information about the OpenView Forum, conference, or for a membership application, please visit http://www.ovforum.org/.

OpenView Forum is an independent corporation, not affiliated with Hewlett-Packard Company.

Copyright Information

Copyright © 1990-2001 Hewlett-Packard Co., All Rights Reserved

What's New in Network Node Manager Runtime Release

For more details about the following features, see the NNM documentation set or the extensive information under NNM's Help menu item.

NNM 6.2

• Improved Visualization of Your Network
  • Node View - View your entire network infrastructure on one map from within your web browser with an XML-based Java applet.  You can view any set of nodes that are defined by NNM's filters.  This requires at least version 1.2 of the Java Plug-in (JPI).  See ovw's Tools:Node Views menu item for more information about Node View or see the "Java Plug-in" section of the release notes.
  • Cisco Discovery Protocol (CDP) View - View the CDP information on a singular node or a series of nodes.  Aggregated (trunked) ports are displayed with thicker lines, and meshed switches are displayed. See ovw's Tools:Node View menu item for more information on CDP or see the "Java Plug-in" section of the release notes.  You can view individual CDP details using ovw's Configuration:Network Configuration->Cisco Discovery Protocol menu items.
  • Port Labeling - Display interface port labels on ovw connections.  Enable this feature with ovw's View:Show Connection Labels menu or use the toolbar button to toggle the port labeling. You will see "Connection Labels Off" in the lower right corner of ovw's status when this feature is disabled.
  • Show Path - Display the topological path between two nodes. A new URL allows you to view the path between nodes.  This URL is available from ovw by selecting one or two nodes and running Fault:Network Connectivity->Show Path.
  • Web Version of ovtopodump - View details about a particular node (using the name or the ovw object ID) with a URL in the form: http://<YOURMACHINE>:<PORT>/OvCgi/ovtopodump.ovpl?node=<YOURNODE>.
• Improved Management of Switched Networks
  • SNMP-based Status Polling - Monitor interfaces that are not directly available to the management station, but are accessible through SNMP (such as on a remote isolated network). Do this by looking at the ifAdminStatus ifOperStatus MIB-2 variables.  See netmon.snmpStatus(4) reference page for more information.
  • Object-based Status Polling - Use filters to set the ICMP/SNMP polling intervals for a node based on it's attributes.  See netmon.statusIntervals(4) reference page or the "Poll Objects " button from ovw's Options:SNMP Configuration for more information.
  • Status Suppression of Unconnected Interfaces - Improve status propagation by marking unconnected interfaces as "unknown" instead of "critical".  See the connectorL2Ports and nonConnectorL2Ports keyword option in the netmon(1M) reference page.
  • Additional Device Discovery - Discover additional devices, based on their supportability of certain MIBs.  See the ovwdb attributes isFrameRelay, isRMON, isRMON2, isCDP, isATM, isDS1, isDS3, and isSONET.
  • Display Bridge MIB Tables - Display various Bridge MIB (RFC 1493) tables from network devices. See rnetstat(1) or ovw's Configuration:Network Configuration->Bridge MIB (rfc 1493) menu items for details.
  • View Connected Nodes - View nodes connected to a switch sorted by port and VLAN.  See ovw's Tools:Connected Nodes menu item.
  • Improved Handling of Port Aggregation (trunking) - To assist with detection of port aggregation, netmon now reads a new user-configured file, $OV_CONF/netmon.equivPorts. This file contains information on a per-device basis about which ports participate in a trunk.  See netmon.equivPorts(4) for more information.
• Improved Data Collection
  • Attribute-based Data Collection Using Filters - See Data Collector U/I.
  • Baselining/Automatic Threshold Setting - Set thresholds automatically using statistical baseline (Standard Deviation) thresholds.  These threshold values are based on the data collected and stored in the data warehouse, using time slots that are based on user-definable buckets.  See Data Collector U/I and $OV_CONF/statTimeRanges.conf.  See statTimeRanges.conf(4) for more information.
  • Collection of String Data - See Data Collector U/I.
  • Collection of Ping Response Time and Ping Retries - netmon collects the response time and retry count for pings and stores the data like any other MIB expression.  See pingResponseTime and pingPercentRetry expressions in $OV_CONF/mibExpr.conf.  Two new reports have been added to the NNM reporting system to allow easy viewing of this data.
  • Improved Data Collection Rate - Default data collection throughput rate has improved more than 10x due to increased parallelism.  See the -n option to snmpCollect(1M).
  • Faster Startup Time - Data Collector will start collecting immediately, instead of waiting until all collections have been determined
  • Out-of-the-box Configuration for Network Infrastructure Devices - Some MIB variables and thresholds for network infrastructure devices are automatically configured by NNM (new installations only).  See $OV_CONF/snmpCol.conf or use Data Collector U/I.
  • Support for Router Reboot via ifAlias - Some routers (such as Cisco routers) may remap their SNMP instance to interface after a reconfiguration.  The data warehouse now stores interface-related data by ifAlias string instead of interface number, compensating for this change.  See OV_IF_Index_Remapped event in $OV_CONF/$LANG/trapd.conf.
  • Additional Information on snmpCollect Process - Additional information about the snmpCollect process is available via ovstatus -v snmpCollect. This includes information such as how many instances are being collected, how many PDUs have been sent and other information to help you characterize your SNMP data collection.
• Improved Data Warehouse
  • ovdwquery -secureFile and -force options - Allow non-root Unix users to run pre-defined secure scripts, and build more complex SQL commands that continue even if a particular SQL command fails.  See ovdwquery(1) reference page for details.
  • New Reports - Top ICMP Ping Response Time, Top ICMP Ping Retries, Top RMON Segments By Octets, Top Frame Relay Congestion
  • Automatic Report Generation - NNM automatically generates Ping Response Time, Ping Retry, Availability, and Inventory reports (new installations only).  You can turn these off or modify them using the NNM Report Configuration interface.
  • Trend data exports and trim are now enabled by default (to facilitate data collector baselining).  This can increase the size of your data warehouse disk space over time.  For more information about managing the size of the data warehouse, see the Managing Trend Data section in chapter 6 of the Reporting and Data Analysis online manual, and the -trimpriorto -delpriorto options of ovdwtrend(1).
• Improved Event Correlation
  • New, faster ECS engine.
  • Circuits improved and up to 5 times faster
  • Supports version 3.1 of ECS Circuit Designer (purchased separately from NNM)
• Improved User Interface
  • Zoom to Highlight - Highlight a node using xnmevents or ovw's Find dialog box. You can choose to open the submaps that contain the object. Each submap zooms to the highlighted object if the map contains many objects.  The ovw Panner is displayed, showing the context of the selected object.
  • Find Dialog Box in Network Presenter - The Edit:Find functionality is available in the Java-based Network Presenter.
  • Menu Graying in Network Presenter - The Network Presenter registration files support menu graying and CONTEXT keywords.
• New Menu Items
  • Telnet - Available from ovw as a right-click pop-up menu.
  • Trace Route - Available from the ovw menu as Fault:Network Connectivity->Trace Route and right-click pop-up menus.
  • RMON Menus Items in ovw - See ovw's Performance:RMON menu items.
  • Link Management Menu Items in ovw - See ovw's Configuration:Network Configuration menu items:ATM, Frame Relay, DS1/E1 Serial Line, DS3/E3 Serial Line, SONET/SDH, along with various Performance, and Fault menu items.
  • Unused IP Addresses - A web-based tool to find the IP address ranges that have not been heard by NNM's topology.  The URL to this report is available from ovw by running Tools:Unused IP Addresses.
• Improved Self-Management
  • Self-monitoring of Event System - The event system (pmd) generates an OV_EventStorm event if an event storm is detected.
  • Name Service Response Time - netmon continuously checks for an appropriate Name Service response time. netmon generates OV_DNS_PerformErr or OV_DNS_PerformWarn events if performance is not appropriate.  For more information, see -T and -U options in the netmon(1m) reference page.
  • Self-monitoring of Data Collector (snmpCollect) - snmpCollect generates an OV_DataColl_Busy event if your network cannot respond fast enough and Data Collector is falling behind.
  • Additional Information on the netmon Process - View how many pings per hour the netmon process is performing, as well as the number of interfaces currently available.  Run ovstatus -v netmon to see the output.
• ovactiond Trusted Commands - By default, ovactiond only runs commands that are listed in the directory $OV_CONF/trustedCmds.conf/.  These commands are often called actions, and are configured by xnmtrap into the configuration file trapd.conf.  If a command is to be executed but is not listed, a OV_NotTrustedCmd pop-up event is generated and the action is not performed.  To disable this feature, as root/administrator create a file $OV_CONF/trustedCmds.conf/ALLOW_ALL.  For more information, see the ovactiond(1M) reference page.
• SNMP Community String Discovery - Let NNM determine which of several community strings are used on a particular node.  See the netmon.cmstr(4) reference page for details.
• Preferred SNMP Address - Nodes in ovwdb now have an additional field, Preferred SNMP Address, which is the IP/IPX address that netmon uses to speak SNMP with the node. Use this field in registration files to control which address is used for SNMP communication.  For more information, see the OVwRegIntro(5) reference page.
• Firewall Support of Traps Received Through a NAT Device.  See -u option in ov_event(5) reference page for details.
• ovdumpevents -t and -l Options - Watch the latest events as they occur by using the -t and -l options of ovdumpevents.  See ovdumpevents(1) reference page for details.
• M Flag in HPoid2type File - (New installations only.) This flag is set so that UNIX workstations no longer appear as gateways in the ovw Internet view.
• Manuals Available as .pdf Files - Manuals are viewable with your web browser.  See the Printable Documentation section of the Release Notes.
• ovwdb TCP port number change - The port number in /etc/services for ovwdb has changed from 9999 to 2447.
• ovalarmsrv and ovalarmsrv_cmd TCP port number change - The port number in /etc/services for ovalarmsrv has changed from 2345 to 2953, the port number for ovalarmsrv_cmd has changed from 2346 to 2954.
• Obsolescence of Excel Report Templates - Use the standard NNM reporting system to generate reports.
• Windows NT/2000-only Features:
• Installation into directories with spaces is now supported.  The default Windows installation is now C:\Program Files\HP OpenView\NNM\.
• Drag-and-Drop from ovw map.
• Microsoft Terminal Server on Windows 2000.
• Tip-of-the-day.
• Use of Winsock-2 instead of Winsock-1 libraries.
• OVSHELL and OVHIDESHELL trapd.conf Keywords - Determines whether or not ovactiond displays a window when running an action.  See trapd.conf(4) reference page for details.

NNM 6.1

• Web Based Reporting Service
  Using any JDK 1.1 compatible browser you can connect to your NNM management station to configure or view NNM reports. An intuitive interface automatically configures data collection and automatically generates reports using NNM's data warehouse on a daily and monthly basis
• Improved Layout for Switched Environments
    - Segment Reduction
    - Better layout/Root Port computation for connectors
    - More efficient layout/less intermediate steps during layout.
  These features on enabled for new installations, but disabled for upgrade installations.   This feature can be modified with netmon's -k option in netmon.lrf
• Support for Windows^® 2000
• Support of secure web servers (https://)
  See $OV_DOC/WhitePapers/secureWebServerConfig.html for more details
• Microsoft Management Console (MMC) Snap-in
  Get access to your UNIX or Windows NT NNM management station from any Windows NT workstation running MMC
• Improved integration with HP OpenView ManageX
  includes a new "MgXServerDown" correlation and ManageX publishing to NNM's report presenter
• Software Update Menu
  Detect new versions or patches to NNM from the Help:NNM->Patches and Updates menu item

NNM 6.01

• New capability in xnmgraph to automatically configure data collections for the data currently being shown on the graph.  Use the File->Configure Data Collector... menu item.  Only the new items being configured are shown in the xnmcollect GUI when this operation is performed, but on a save the new items become part of the normal collections stored in snmpCol.conf.
• New capabilities have been added to perform many functions on interfaces as well as entire nodes. Both xnmgraph and rnetstat now support invocation for a specific interface (not just a node).  This is especially helpful in xnmgraph when the node may have many interfaces.  rnetstat now has special capabilities for gathering information specific to an interface.  Thus, all of the standard menu items under the Performance, Configuration, and Fault menus can now be invoked on a selected set of Interface objects, not only on a selected set of Node objects.  In addition new pop-up menu items for Interface objects have been added to quickly obtain status information.
  To see this new functionality, rather than selecting a node symbol, instead select a line between two symbols or drill down into a node and select one or more of the interfaces.   Then select one of the menu items to view status or statistics, for example: Configuration->Network Configuration->Interface: Properties or Performance->Network Activity->Interface->Traffic->Utilization
• rnetstat now supports many new options for inquiring about various aspects of a node or interface.  New functionality includes support for querying Frame Relay, DS1/DS3, ATM and SONET MIBS.  See the rnetstat reference page for details.
• New support in xnmgraph (and a helper executable 'ovexprguru') to do "smart" graphing of various statistics based on the configuration of the particular device being graphed.   For example, you can now see a utilization graph which for Full Duplex interfaces shows input and output rates as separate lines, but Half Duplex interfaces are graphed as a single line.  These enhancements support the proper use of high speed counters.   See the ovexprguru.1 man page for more details.
• In conjunction with the above functionality many new expressions are shipped as part of mibExpr.conf.
• The NNM installation is now split into three main phases.  First the Event Correlation Services, then the OpenView SNMP Agent (and corresponding man pages), and lastly Network Node Manager itself.

NNM 6.0

• Event Correlation Services (ECS)
  Event correlation improves the information content of alarms in NNM's Alarm Browser by removing unwanted, redundant alarms and by adding new, more informative alarms.
• Data Warehouse
• Data Warehouse allows you to store historical NNM trend, topology, and event data with an ODBC SQL interface
• Lightweight embedded database for NNM (Solid) automatically installed
• Support for commercial relational databases or NNM's embedded database via ODBC
• The -Ro/-Ri (store operational data in Oracle/Ingres) options to ovtopmd have been obsoleted in favor of the option to use commercial databases as the data warehouse
• Data Warehouse export of topology (inventory) data
• Data Warehouse export and summarization of trend and events data into daily, weekly, and monthly buckets
• HP OpenView Java-based Web Interface
• Launch other HP OpenView applications and third party products from a common integration point with the HP OpenView Launcher
• Explore the NNM map hierarchy with the Network Presenter
• Use the Web Alarm Browser to view, filter, delete, and acknowledge alarms
• Use the SNMP Data Presenter to view SNMP data
• Additional URLs can be added through simple "drop-in" registration file extensibility
• Automated Backup
• Provides backups with database consistency without stopping and restarting the NNM background processes
• Enables easy integration into existing archiving facilities and schedulers
• Additional backup scripts can be added through simple "drop in" backup script extensibility
• Improved Alarm Browser
• Support for multiple operators - when one operator (either locally or through the Web Alarm Browser) acknowledges/deletes/reclassifies an alarm, all operators see the change
• New indicator for correlated events
• New View:Show Correlated Events to view the alarms suppressed by the Event Correlation Services.
• The event browser (xnmevents) has been renamed 'Alarm Browser' in support of NNM's new operational model for alarm management, and menu items have changed from 'event' to 'alarm'.
• Simpler Licensing
• Node locked only (netls) license server no longer used.
• Licenses can be requested over the World Wide Web.
• Performance improvement by not adding unmanaged nodes past licensed limit.
• Remote Console Support
• Remote Consoles running NNM on Windows NT can now communicate with NNM management stations running on either UNIX or Windows NT
• Gracefully terminate all NNM processes using a single command (ovstop -c ovuispmd) on the management station
• Collection Station Support
• Management stations running on Windows NT can now receive distributed data from Collection Stations running on either UNIX or Windows NT
• The ovrepld service (background process) that listens for Collection Stations is not automatically started on a fresh installation.  It is only started after the first xnmtopoconf command establishes a Collection Station.
• Automatic management station/Collection Station failover
• Management stations will take over status polling for any Collection Station that is no longer reachable
• Once the Collection Station is reachable again, the management station will automatically release status polling for the nodes reported by the Collection Station
• A failover filter controls which objects assigned to a Collection Station will be status polled by the management station during failover
• DHCP support
• Ability to designate a bank of IP addresses as DHCP leased nodes, allowing NNM to intelligently handle the changing MAC addresses, configurable through Options:Network Polling Configuration dialog box.
• Events added to the OpenView MIB (.1.3.6.1.4.1.11.2.17.1) for informing NNM about DHCP node leases: OV_DHCP_Alloc and OV_DHCP_Release
• Support for Intel's Wired for Management Initiative (Windows NT only)
• Remote Power On -- provides the ability to bring a system to a fully powered state from a reduced power state by sending a special network packet to the system.
• DMI 2.0 Support via Intel's DMI 2.0 Service Provider version 1.10 and DMI Explorer version 1.11
• DynaText Browser
• NNM's Help:Online Manuals menu item allows you to view, search, and print the complete set of NNM manuals using DynaText. DynaText is shipped on the CD with Network Node Manager.
• Data Collector Enhancements
• Start-up and reconfiguration performance improvements (see -I startup option in the snmpCollect reference page in NNM's online help or the UNIX manpage)
• Multiple sysObjectIds per collection
• Multiple node/instance combinations per collection
• An alarm is generated when a node is up but an SNMP request fails
• More persistence choices when a node does not respond (slowly back-off deferring collection within the first hour)
• Menu Items in NNM's Windows NT Version and UNIX Version Match
• The Locate menu has been removed from the menu bar. This functionality is now under Edit:Find->
• The map, submap, and snapshot descriptions can now be found under Map:Properties, Map:Submap->Properties, and Map:Snapshot->Properties.  Object and symbol descriptions can now be found by right-clicking on any symbol and selecting Object Properties or Symbol Properties.
• The Window menu has been added to the menu bar. Menu items under this menu are also located on the toolbar
• The Help:HP OpenView On The Web menu item connects to the HP OpenView Bridging the Gap web page.
• The Help:Release Notes menu item displays the NNM's Release Notes
• The Tools:HP OpenView Launcher menu item opens the Java-based Web Interface
• Other menu items have been renamed or slightly changed
• Previous UNIX-only features now available on Windows NT
• Submap Window Overlay
• Submap Geometry
• Non-display of uninitialized capabilities fields
• Connection symbol type
• Command line interface for map status propagation and map copy/delete. See the ipmap reference page in NNM's online help (or the UNIX manpage) for more information.
• Repeater MIB (RFC 2108)  support
• SNMPv2C support in all NNM applications
• Higher performance status polling.  The use of the connector down correlation and fewer pings when a node is down prevents unnecessary pinging.
• New "Map->Export..." and "Map->Import..." menu items allow for moving certain map customizations between machines. See NNM's "Help:NNM->Topics" for more information.
• Registration files now support platform specific definitions (#ifdef support)
• Integration and auto-detection of HP OpenView ManageX product
• Even more user friendly installation (smarter ./install on UNIX)
• Perl 5.003 automatically installed into \OpenView\bin\Perl\ or $OV_BIN/perl
• Web server for NNM automatically installed (UNIX only)
• Java Runtime Environment for NNM automatically installed
• The Binary Event Store replaces the trapd.log file .  If you still need trapd.log, see Managing Your Network with NNM for more information.
• ovwdb.auth and ovw.auth files now shipped with full access (+ +) by default for web interface support
• Discovery via ping sweep capability through loadhosts -c command. See the loadhosts reference page in NNM's online help (or the UNIX manpage) for more information.
• Support for GIF89a images on the maps.
• Support for pixmap format icons on the Windows NT version of the map.
• ovspmd now generates an alarm that causes a popup window to display whenever any of NNM's services (background processes) unexpectedly terminate.
• New Contributed Applications (See Managing Your Network with NNM for more information.)
• Java-based grapher
• Web-based Report Presenter (a framework for browsing and displaying HTML reports of data warehouse information)
• High Availability Support/Service Guard (HP-UX only)

NNM 5.02

• Windows NT-only release with features:
• NNM Special Edition for OEM bundled solutions
• Year 2000 compliance
• DMI 2.0 capability discovery and event management
• ACE*COMM NetPlus(tm) WinSNMP replaces the FTP Software WinSNMP stack
• NNM SNMP Trap Reception (using ACE*COMM WinSNMP) is now compatible with Microsoft SNMPTRAP service and applications such as Microsoft SMS Server

NNM 5.01

• Textual Web interface to topology, events (replaced by Java web interface of NNM 6.0)
• Textual Web SNMP MIB browser
• Support for Japanese language (new for Windows NT, already supported on UNIX)
• Support for mixed English and Japanese language (new for Windows NT, already supported on UNIX)
• Perl programming language available in contrib directory
• Windows NT Contributed Applications on CD-ROM (installable via "custom" option at installation, installed by default on UNIX)
• Windows NT 35% Smaller installed disk footprint than NNM 5.0
• oid_to_sym has moved from $OV_CONF/C to $OV_CONF
• HP TopTOOLS DMI tool in contrib directory (Windows NT only)
• Year 2000 Safe
• Nodelock licensing (UNIX-only)
• Improved internationalization support

NNM 5.0

• Level-2 (below IP) discovery and layout
• Bridge MIB and unnumbered interfaces support
• SNMPv2C support for secondary NNM components (such as counter64 in grapher)
• WEB-manageable device discovery
• WEB application launching
• Better looking/more ovw icons
• Better mapping of new icon symbols to node (i.e. different icon/O.S.)
• WinHelp hyperlinked reference pages
• Postscript versions of printed manuals
• Easier-to-use licensing
• Much faster discovery of your network
• The snmptrap command has been replaced by snmpnotify
• Command to print out the NNM version information
• Compact output of ovstatus and ovstart via 'ovstatus -c'
• Windows NT-only features:
• DMI browsing
• Integration with Microsoft Systems Management Server (SMS)
• Native NT tools integrated into ovw menu bar
• Redesigned SNMP configuration (xnmsnmpconf)
• Redesigned IP/IPX configuration (xnmpolling)
• Redesigned event configuration (xnmtrap)
• Redesigned application builder with wizard (xnmbuilder)
• Redesigned ovw's Edit:Add Object dialog
• Redesigned ovw's Map:Properties dialog
• Redesigned ovw's Map:Submap->Properties dialog
• New ovw "Map:New" wizard
• New ovw "Map:Submap->New" wizard
• ovw "View:Status Bar" toggle
• More Windows NT-friendly menu structure on ovw
• "Designed for BackOffice" Microsoft certification
• "Intro to HP OpenView Network Node Manager" CD-ROM
• Participation in distributed management as a HP OpenView collection station
• Native Windows NT GUI: no "UNIX Motif/X11" display mapping
• Native Win32 application - no "UNIX" porting layer
• IPX Discovery and Monitoring
• SNMP over IPX for all applications
• Demonstration bitmaps and screen shots in the demo subdirectory on the CD-ROM
• Includes WinSNMP runtime
• Tracing/Logging into the NT event log
• UNIX-only features:
• Drag and drop
• Submap window overlay, geometry and printing
• Non-display of unset capability fields
• Choosing map status propagation mode from the OVw command line
• Copy and delete maps from the OVw command line
• New telecom icons
• More extensive and detailed set of color background GIF files (maps)
• Connection symbol thickness and icons

Network Node Manager 6.2 Supported Configurations

This document contains the following topics:

• Hardware and Software Minimum Requirements
• Supported Web Browsers
• Java Plug-in Minimum Requirements
• Supported Web Servers
• Supported External Databases
• Supported Japanese and Non-English Locale Configurations
• Supported NFS Packages for Remote Consoles to Windows NT/Windows 2000
• Supported PC-based X Window Emulators
• Mixing Versions of NNM in a Distributed Environment
• Supported Versions of Microsoft SMS

Hardware and Software Minimum Requirements

Supported Web Browsers

The following browsers are supported with NNM 6.2.  For an updated list of browser support, please visit http://ovweb.external.hp.com/nnm/NNM6.2/relNoteUpd/relNoteUpdate.htm.

Java Plug-in (JPI) Minimum Requirements

Node View and CDP View require the Java Plug-in (JPI) version 1.2 or newer for display, as described below. 

HP-UX JPI Install Instructions:
Node View and CDP View require the Java Plug-in (JPI) version 1.2 or later version.  When you view Node View or CDP View, you will be prompted with a dialog like:

This page contains information of a type (application/x-java-applet;version=1.2) that can only be viewed with the appropriate Plug-in.
Click OK to download Plugin.

Clicking OK will direct you to a page for downloading the plug-in. Use the following steps for installing the JPI.

1. swremove any previous versions of the JPI.
2. Remove any files in /opt/java1.2/plugin directory.
3. Download the software from the URL in the table above.
4. Stop Netscape.
5. Use swinstall to install the Plug-In according to the instructions on the web page.
6. cd /opt/java1.2/plugin.
7. sh /opt/java1.2/plugin/package according to the instructions in /opt/java1.2/plugin/jpi.release.notes.  This step will need to be done by each user (not as root) that wants to run nodeView/cdpView.
8. Configure the runtime Plug-In using the ControlPanel script $HOME/.netscape/java/ControlPanel.html, which creates the properties file for finding the Plug-In.  
9. Enable the JPI by running Netscape and selecting Edit:Preferences, expanding the Advanced category, and checking [ ] Enable Java Plugin.
10. Verify the configuration by selecting Netscape's Help:About Plug-ins. You should see a definition for Mime Type application/x-java-bean;version=1.2, with a description of Java (tm) Plug-in.
11. Verify that the JPI Control Panel works by opening the $HOME/.netscape/java/ControlPanel.html (e.g. run $MOZILLA_HOME/netscape $HOME/.netscape/java/ControlPanel.html)
12. To verify which exact version of the JPI you are using, bring up the ControlPanel.html, and pick the "Basic" tab, and check "Show Java Console".  Restart the browser, then browse to Node View.  The version of the JPI will show up in the Java Console.

Note:
The 1.2.2.07 JPI version on Netscape 4.76 does not display the 'Show Connection Labels' button in Node View and CDP View.
Note:
The HP-UX JPI 1.3 Beta ControlPanel.html is instead installed in $HOME/.netscape/jre/ControlPanel.html.
Note:
It appears with the 1.2 JPI on Netscape 4.76 that printing hangs - unconfirmed if printing works with JPI 1.3 Beta

Solaris JPI Install Instructions:
Netscape 6 is available on Solaris. Downloading this version may be simpler than trying to install the Java Plug-in.
You may need to get the Java Plug-in (JPI) 1.2.0 or later.

The steps to install the JPI (as root) are listed below. 

1. Download the JRE v 1.3.0 from the URL in the table above.
Be sure to set your NPX_PLUGIN_PATH environment variable as described in the JPI installation instructions, or copy the .so file to your $HOME/.netscape/plug-ins directory. For example, you might set NPX_PLUGIN_PATH as:
export NPX_PLUGIN_PATH=/opt/j2re1_3_0/plugin/sparc:/opt/acrobat4/Browsers/sparcsolaris:/opt/NSCPcom/netscape/plugins


You do not need to set the environment variable MOZILLA_HOME, but be sure it is not incorrectly set.  In some cases you may need to
    export CLASSPATH=""
or you may receive a "BUS ERROR" message.

2. Download and install any Solaris patches as needed from the same web site using the patchadd command as described in README.sparc.
3. Run the 1_3_0-solsparcJPI1.3.0.bin executable from the directory where you would like the software installed, such as /opt.
4. Create the symbolic link as indicated in the README.html such that the JRE can be found, e.g.:
   ln -s /opt/j2re1_3_0 /usr/java
5. Enable the JPI by running Netscape and selecting Edit:Preferences, expanding the Advanced category, and checking [ ] Enable Java Plugin.
6. Verify the configuration by selecting Netscape's Help:About Plug-ins. You should see a definition for Mime Type application/x-java-bean;version=1.2, with a description of Java (tm) Plug-in.
7. Bring up the JPI control panel, e.g.:
   export MOZILLA_HOME=/opt/NSCPcom; /opt/NSCPcom/netscape /opt/j2re1_3_0/ControlPanel.html

Windows NT/Windows 2000 JPI Install Instructions:
The first time you visit Node View or CDP View with your browser, you'll likely get a dialog like:

Do you want to install and run the "Java Plug-in 1.3" signed on 5/11/2000 1:09 PM and distributed by:
Sun Microsystems, Inc.

You must answer yes to this question to download the Java 1.3 Plug-in. Follow the instructions to install the Java 1.3 Plug-in. You may verify the installation and configure the plug-in from the Control Panel by selecting Java Plugin.

You can also load the JPI using the URL from the above table. 

To view which version of the JPI you are running, you can look at Start:Settings->Control Panel->Add/Remove Programs, and see an installed version entitled "Java 2 Runtime Environment Standard Edition v1.3".
Next, select Start:Settings->Control Panel->Java Plug-in.  Click on the About tab to see the version of the JRE and JPI. To view the Java Console, select the Basic tab, and check Show Java Console, and click Apply.
Close all browser windows and browse to Node View again.  The version will also display at the top of the Java Plug-in Console.

To see what version of Java that Internet Explorer has, you must select Tools:Internet Options; Advanced Tab. Under Microsoft VM check Java console enabled (requires restart).  After restarting, select View:Java Console and the release will show at the top of the Java Console (Do not confuse IE's Java Console with the JPI's Java Console).

Japanese Users:
When you first download the JPI, at the "Select Java(TM) Plugin Installation..." dialog, be sure to set your Locale to "International".  Otherwise, your Japanese IE 5.5 browser will disappear every time you load Node View or CDP View.

Supported Web Servers

NNM currently only supports the following web servers:

• Apache on UNIX (NNM installs this by default)
• Apache based Stronghold and Raven servers on UNIX
• Peer Web Services or Internet Information Server (IIS) on Windows NT/Windows 2000

You may replace the NNM Web Server with your own web server by following the instructions on the CD in $OV_DOC/WhitePapers/changeWebServer.html

Supported External Databases

If you are using the embedded database that is installed with Network Node Manager, you have no additional requirements.  If you want to run an enterprise database, the following external databases are supported:

For Oracle, the following products are required to run together with NNM.

• Oracle server
• SQL*Plus
• NET 8 (or SQL*Net, version 2 for Oracle 7 on HP-UX 10.20)
• The following components are not required by NNM, but can be used for reporting:
  • Oracle Data Query
  • SQL*ReportWriter
  • SQL*Report
• If you are configuring Oracle on a remote server, the database client (NNM system) requires:
  • Oracle client
  • NET 8 (or SQL*Net, version 2 for Oracle 7 on HP-UX 10.20)

HP only supports 32 bit Oracle on HP-Unix.  However if you want to install 64 bit Oracle then in order to run NNM with Oracle you will need to install 32 bit Oracle as well and ensure NNM loads the 32 bit libraries.  Please refer to the OfO (Oracle for OpenView) release notes or contact Oracle support on how to do this.

Supported Japanese and Non-English Locale Configurations

A single installation of Network Node Manager can support both English and Japanese. Other languages can be set to get locale specific values such as dates, sorting/collation, character handling, and currency, but NNM is only localized to U.S. English and Japanese languages. Various parts of Network Node Manager  force LC_NUMERIC to be C to enforce consistent use of ',' instead of '.' for numbers. The following settings will select the various fully localized languages.

• For HP-UX:
  • U.S. English: export LANG=C
  • Japanese SJIS: export LANG=ja_JP.SJIS
  • Japanese EUC: export LANG=ja_JP.eucJP
• For Solaris:
  • U.S. English: export LANG=C
  • Japanese SJIS: export LANG=ja_JP.PCK
  • Japanese EUC: export LANG=ja
• For Windows NT 4.0:
  • Language-specific installation of operating system required
  • Locale is set to "Japanese" or "Japanese_Japan.932" for SJIS
  • $LANG variable should be unset.
• For Windows 2000:
  • No language-specific installation of the operating system is required
  • Language is set via the Control Panel's  Regional Options.  Set the Your locale (location): field appropriately from the General tab.  Picking "Japanese" enables the Japanese localized version of Network Node Manager.
  • $LANG variable should be unset.

NNM does not support Japanese versions of jovw.exe, jalarms.exe, and ovlaunch.exe from Netscape browser under HP-UX 10.20.  This is because of a known defect in Java, and is supposedly fixed via a plug-in. However, these Java applets do not make use of the plug-in. NNM's CGIs generate an HTML page with a java applet embedded which is incompatible with the plug-in. Netscape on HP-UX 10.20 and Java 1.1.6 causes ovlaunch to hang as it initializes at 40%.

The native NNM GUI is supported with Japanese locale but the 4.7x Netscape browser called from it isn't supported in a Japanese configuration. You can change the browser's Language Setting to English[en] but this causes another serious problem in the jovw.exe GUI.  Showing any submap which has a Japanese submap name (multi-bytes character) has problems. These submap names are shown as corrupted strings in the Content Selection Box and Scoping Pane of the jovw.exe GUI. Additionally, NNM assigns Japanese text to the Internet submap name under Japanese environment, not the "Internet" string of English. This causes the  Internet submap to be shown as garbage characters in the jovw.exe GUI.

(Unix only) Be sure that the ovspmd process (started upon bootup via /etc/init) has the correct locale set, or the web-based alarm browser will not have localized categories. This happens if ovalarmsrv is running with LANG=C in it's environment.  The environment is set at the time ovstart is first run, usually at the operating system startup, and is passed to it's child processes, such as ovalarmsrv.  Running 'ovstop ovalarmsrv; ovstart ovalarmsrv' will not change the parent's environment. Often the operating system has the default language of "C" when it first starts, so this environment is passed indirectly to ovalarmsrv. To work around this problem, set the correct language variable (such as 'export LANG=ja_JP.SJIS') into the /sbin/init.d/ov500 file. Or after every re-boot, run ovstop;ovstart with the correct $LANG in the environment.

Netscape Japanese-specific browsers no longer exist because they have been merged with the English Netscape browser version. If you add japanese[ja] support at Language support tab, you can use the Japanese version Netscape. If you install the Java Plug-in (JPI) using the "java1.3/plugin/package i18n" option, all internationalization options are automatically enabled.

Configuring Internet Explorer Web Browser/Java Plug-in to Display Japanese

A Japanese web browser pointed at a system which supports multi-locales will display Japanese characters, while an English web browser will display English when pointed at the same system.  This requires that the Japanese locale be installed on the server for Unix systems. With Internet Explorer browser you can adjust your locale by selecting Tools:Internet Options and clicking the Languages... button.  To view Japanese, select Add... and make  "Japanese [ja]" the first item in the list.  Note that an input method must also be selected, and it configured via Regional Settings of the Windows Control Panel.

If you get a message like:

Cannot set locale LC_ALL to [system default]. Be sure the locale is set on the machine (check the "Language settings for the system" in Control Panel's Regional Options)

it is likely that you need to set the Control Panel's Regional Options "You locale (location):" field to Japanese.  Windows 2000: If this field is not available, you need to check it in the "Language settings for the system" section.

Be sure to set the Fonts correctly, so you can display Japanese fonts.  Do this from Internet Explorer by picking "Tools:Internet Options", General tab, pick "Fonts...", and change "Language script:" to "Japanese".  For English systems this should be set to "Latin based".

On Windows, if the English version of the Java Plug-in (JPI) is installed instead of the International version, NodeView and CDPView will cause Internet Explorer to immediately disappear without a message.

Configuring Netscape Browser/Java Plug-in For Japanese HP-UX

Not Supported.  Browse from an HP-UX 11.x or Windows platform.

HP-UX 11.X

Netscape 4.75
Java 1.2
Java Plug-in 1.2

All of NNM's Java-based Web Interface works on Japanese HP-UX 11.0. The following setup of Japanese Netscape 4.75 is required for supporting Japanese:

Language Setting - Add Japanese[ja] in the Language section.
Encoding Setting - Change Encoding Setting to Japanese (Auto-Detect) and set this as the Default Encoding.

Java Plug-in (JPI)  Installation

Be sure to run /opt/java/plugin/package with i18n option and with LANG=C else you will get a message "/opt/java1.2/plugin/package[77]: Multi-byte character is not correct". For example, install the JPI with
    $LANG=C /opt/java/plugin/package i18n
in the home directory.  This will then allow you to run 'cd $HOME/.netscape/java; ./ControlPanel' without a java.lan.NullPointerException..

Supported NFS Packages for Remote Consoles to Windows NT/Windows 2000

These are the 3^rd party NFS packages that have been tested for use with NNM Remote Consoles.

• WRQ NFS 6.2
• Intergraph DiskAccess 5.0
• HummingBird NFS Maestro 7.0
• FTP Interdrive 7.0

Supported PC-based X Window Emulators

The following PC-based X Window emulators are supported.

• WRQ ReflectionX 7.0 (Version 6.2 causes window sizing problems)
  Windows 2000 requires version 8.0.5 or newer.
• Hummingbird Exceed 6.x or 7.x

This procedure describes how to start a font server on a HP-UX 10.XX/11.XX system and how to access the font server from the "remote display" system.  The steps look similar to set up a font server on a Solaris system. Note: the font server doesn't necessarily have to be the system running Network Node Manger.

What you need to do on a the HP-UX system to start the font server:

1. edit the /etc/rc.config.d/xfs and set RUN_X_FONT_SERVER=1
2. run as root: /sbin/init.d/xfs start

What you need to do on the "remote display" system:

1. log in as the user who wants to run ovw
2. run: xset  + fp tcp/<UNIX_hostname>:7000
3. run: xset fp rehash
4. run: xset -q    # to check the new font path
5. rlogin to the Unix box and run ovw -display .......

This can be done in a shell script.  To make the font search path permanent, you need to look at the Xserver configuration possibilities.

Mixing NNM Versions in a Distributed Environment

When using HP OpenView Remote Consoles, the server and the clients must all be the same version.  When running in a DIDM configuration (Manager of Managers), the collection stations may be a lower version than the management station.

Supported Versions of Microsoft SMS

Network Node Manager (Windows only) supports integration with Microsoft System Management Server (SMS) versions 1.2 and 2.0.  If the SMS Administrator software is installed on your NNM management system, the Configuration:SMS Properties and Configuration:SMS Administrator menu items appear. On any ovw submap, simply select a node that is an SMS client (running the SMS client software) and view the SMS properties.

Installation Overview

This guide will help you install HP OpenView Network Node Manager version 6.1 or later and, optionally, HP OpenView Customer Views for NNM on a computer using the Windows NT operating system or Windows 2000 operating system.

There are six tasks to complete during the installation process:

• Match your system's setup to the NNM minimum requirements.
• Complete any necessary pre-installation steps.
• Install the NNM software.
• Run the NNM software.
• Obtain a permanent password for your NNM software.
• Configure NNM to access the HP OpenView Web interface.

Once you have successfully installed NNM, refer to the last section in this guide, for "where-to-go-next" information on configuring and using your NNM product.

Task 1: Checking System Requirements

Before starting, you or your system administrator should check that your system meets the minimum hardware and software requirements listed below. (Note that the installation program will automatically check the amounts of RAM and free disk space for you):

Refer to the Release Notes for system requirements information. You can access the Release Notes from the CD. The Release Notes are in the README.html file

From the left pane of the Release Notes, double-click on Supported Configurations.

Task 2: Completing Pre-Installation Steps

To ensure that all products installed on your system run compatibly and efficiently with NNM, there are several preparatory steps you need to do before you actually install the NNM product itself.

General Configuration

1. If your system has other HP OpenView products installed on it (such as Perfview or IT/Operations), refer to the HP OpenView Network Node Manager Migration Guide. This guide describes which HP OpenView products are compatible with the version of NNM that you are now installing.

2. If your system has any third-party OpenView applications installed on it, check to see that they have been tested with NNM 6.1 or later. The current version of most of these third-party applications have been tested to work on NNM 6.1 or later. The following World Wide Web URL lists the application names and versions that run on each of the supported HP OpenView platforms. Also found at this URL are supplementary instructions for installing these third-party applications with NNM 6.1 or later.

   http://ovweb2.external.hp.com/solutions/technical

3. Make sure that you have the required Service Pack installed.

4. Install the products described in the remainder of this task section. Some of these products must be installed before you install NNM, while others are optional or not relevant to your network's environment.
   • Paging File setup...depends on your network environment
   • TCP/IP Service installation...required
   • Microsoft SNMP Agent installation...required
   • IPX Service installation...optional
   • DHCP setup...depends on your network environment
   • Web browser installation...required
   • Web server installation...required
   • Microsoft data access components check...required
   • Microsoft Terminal Services...optional
   • Windows NT Service Pack reinstallation...required

Paging File Setup

If you will be managing more than 250 nodes on your system, you should increase the initial size of your system's paging file. This paging file controls the amount of available virtual memory.

Windows NT operating system:

1. In the Start menu on the Windows NT operating system task bar, select the Settings:Control Panel item.
2. In the Control Panel, double-click on the System item.
3. In the System Properties dialog box, select the Performance tab.
4. In the Virtual Memory box, select the Change... button. You will see the following display:

   Initial size (MB)   ____
Maximum size (MB)   ____

5. Enter your new settings. Calculate an additional 3 MB of paging file size for each set of 250 nodes you need to manage. Select the Set button each time you change a drive's paging file size.
6. Select the OK button.
7. In the System Properties dialog box, select the Close button.
8. In the System Settings Change dialog box, either:
   • Select the Yes button to establish the new paging file size by restarting the Windows NT operating system.
   • Select the No button to go on to the next pre-installation task, install the TCP/IP Service.

Windows 2000 operating system:

1. In the Start menu on the Windows 2000 operating system task bar, select the Settings:Control Panel item.
2. In the Control Panel, double-click on the System item.
3. In the System Properties dialog box, select the Advanced tab, then select the Performance Options... button.
4. In the Performance Options box, select the Change... button. You will see the following display:

   Initial size (MB) ____
Maximum size (MB) ____

5. Enter your new settings. Calculate an additional 3 MB of paging file size for each set of 250 nodes you need to manage. Select the Set button each time you change a drive's paging file size.
6. Select the OK button.
7. In the System Control Panel Applet dialog box, select OK button to restart your computer in order for the changes to take effect.
8. In the Performance Options dialog, select OK button.
9. In the System Properties dialog box, select the OK button.
10. In the System Settings Change dialog box, either:
    • Select the Yes button to establish the new paging file size by restarting the Windows 2000 operating system.
    • Select the No button to go on to the next pre-installation task, install the TCP/IP Service.

TCP/IP Service Installation

TCP/IP services must be installed before the NNM product.

Windows NT operating system:

1. In the Start menu on the Windows NT operating system task bar, select Settings:Control Panel.
2. In the Control Panel, double-click on the Network icon.
3. In the Network dialog box, select the Protocols tab. Look at the list. If TCP/IP Protocol does not appear, do the following:
   1. Select the Add... button.
   2. Select the TCP/IP Protocol item.
   3. Select the OK button.
4. When prompted, enter the path to the I386 directory, such as

   drive_letter:\I386

5. In the Network dialog box at the Protocols tab, highlight the TCP/IP Protocol item and select the Properties... button.
6. In the Microsoft TCP/IP Properties dialog box, verify the following:
   1. At the IP Address tab, verify that the subnet mask of your management station is correct.
   2. At the DNS tab, check the Domain field. This field must contain the Domain Name System (DNS) domain related to your IP address, not to the Windows NT operating system domain. An example of a valid DNS domain is hp.com.
   3. Also at the DNS tab, verify that a TCP/IP domain has been specified in the DNS Service Search Order field.
   4. At the WINS Address tab, verify that the Enable DNS for Windows Resolution option has a check mark next to it.
7. Next, verify that the node name from your DNS server and the DNS name configured in the Windows NT operating system both match. In the Microsoft TCP/IP Properties dialog box, do the following:
   1. At the IP Address tab, note the IP address value shown.
   2. At the DNS tab, note the Host Name and Domain field values shown there.
   3. Open a separate DOS window. At its prompt, type

ping nodename

      where nodename is the Host Name shown at the DNS tab. Verify that the IP address which was pinged matches the configured IP address shown at the IP Address tab.
   4. At the next DOS prompt, type

ping nodename.dns_domain

where dns_domain is the Domain value shown at the DNS tab. Verify that the IP address which was pinged matches the configured IP address shown at the IP Address tab.
   5. Do steps 7c and 7d on another computer to validate that your DNS is working correctly.
8. In the Microsoft TCP/IP Properties dialog box, select OK.
9. In the Network dialog box, select Close.
10. In the Network Settings Change dialog box, either:
    • Select the Yes button to establish your TCP/IP-related changes by restarting the Windows NT operating system.
    • Select the No button in order to go on to the next task, installing the Microsoft SNMP Agent software.

Windows 2000 operating system:

1. In the Start menu on the Windows 2000 operating system task bar, select Settings:Control Panel.
2. In the Control Panel, double-click on the Network and Dial-Up Connection icon. (You must be connected to the network before proceeding to the next step.)
3. In the Network and Dial-Up Connection dialog box, right-click the Local Area Connection icon and click on Properties. Look at the list. If Internet Protocol (TCP/IP) does not appear, do the following:
   1. Select the Install... button.
   2. Select the Protocol item.
   3. Select the Add button.
   4. Select Internet Protocol (TCP/IP), then OK button.
4. If prompted, insert the CD and click OK. (This step depends on how your machine was originally set up.)
5. In the Local Area Connection Properties dialog box at the General tab, make sure the Internet Protocol (TCP/IP) check box is selected, then select the Internet Protocol (TCP/IP) item and select the Properties... button.
6. In the Internet Protocol (TCP/IP) Properties dialog box, verify/enter the following items:
   1. Make sure that the Use the following IP address option button is selected. Enter a valid IP address.
   2. Enter a valid subnet mask and verify that the subnet mask of your management station is correct.
   3. Enter a valid default gateway and verify that the gateway of your management station is correct.
   4. Make sure that the Use the following DNS server addresses option button is selected. Enter a valid preferred DNS server address and if applicable an alternate DNS server address.
   5. Select the Advanced button, and verify the IP Settings tab fields.
   6. Select the DNS tab, verify that DNS server addresses have been specified in the DNS Server addresses, in order of use field.
   7. Select the Append these DNS suffixes (in order) option button. Add the appropriate DNS suffixes, then complete the DNS suffix for this connection, box and select the check box for Register this connection's addresses in DNS.
   8. At the WINS tab, verify that the Enable LMHOSTS lookup check box is selected and the option button for Enable NetBIOS over TCP/IP has been selected. Add a valid WINS address in the WINS addresses, in order of use: box
   9. Click OK in the Advanced TCP/IP Settings dialog box. Click OK in the Internet Protocol (TCP/IP) Properties dialog box. Click Close in the Local Area Connection Properties dialog box.
7. Next, you must configure a primary Domain Name System (DNS) domain suffix related to your IP address (not the Windows 2000 operating system domain). An example of a valid DNS domain is hp.com.
   1. Right-click on My Computer and select Properties. In the System Properties dialog box, select the Network Identification tab.
   2. Select the Properties button, then select the More... button. In the DNS Suffix and NetBIOS Computer Name dialog box, enter a valid Primary DNS suffix of this computer in the box. Select the Change primary DNS suffix when the domain membership changes check box.
   3. Click OK in DNS Suffix and NetBIOS Computer Name dialog box, click OK in Identification Changes dialog box, click OK in the Network Identification dialog box to acknowledge the restart, and finally click OK in the System Properties dialog box. Note the settings of the machine for verification in step 8. Click Close in the Local Area Connection Properties dialog box.
   4. In the System Settings Change dialog box, either:
      • Select the Yes button to establish the new settings by restarting the Windows 2000 operating system.
      • Select the No button to go on to the next pre-installation task, install the SNMP Service.
8. Next, verify that the node name from your DNS server and the DNS name configured in the Windows 2000 operating system both match.
   1. Open a separate DOS window. At its prompt, type
      
ping nodename

      where nodename is the system name. Verify that the IP address that was pinged matches the configured IP address noted earlier.
   2. At the next DOS prompt, type

ping nodename.dns_domain

where dns_domain is the primary DNS suffix entered in step 7. (If you chose not to restart you system in step 7, this step will produce a time-out message.) Verify that the IP address that was pinged matches the configured IP address noted earlier.
   3. Do steps 8a and 8b on another computer to validate that your DNS is working correctly.

Microsoft SNMP Agent Installation

The Microsoft SNMP Agent (SNMP Service) must be installed before the NNM product.

Windows NT operating system:

1. In the Start menu on the Windows NT operating system task bar, select Settings:Control Panel.
2. In the Control Panel, double-click on the Network applet.
3. Select the Services tab.
4. Select the Add... button.
5. Select the SNMP Service item.
6. Select the OK button.
7. When prompted, enter the path to the I386 directory, such as

   drive_letter:\I386

8. In the Microsoft SNMP Properties dialog box, select OK.
9. In the Network dialog box, select OK.
10. In the Network Settings Change dialog box, either:
    • Select the Yes button to establish your SNMP-related changes by restarting the Windows NT operating system.
    • Select the No button to go on to the next task, configuring IPX.

Windows 2000 operating system:

1. In the Start menu on the Windows 2000 operating system task bar, select Settings:Control Panel.
2. In the Control Panel, double-click on the Add/Remove Programs applet.
3. In the Add/Remove Programs dialog box, select the Add/Remove Windows Components button.
4. The Windows Components wizard appears. Scroll down and select Management and Monitoring Tools. Click Details and select the Simple Network Management Protocol check box.
5. Select the OK button.
6. Click Next and wait while the wizard configures components.
7. When prompted, insert the Windows 2000 operating system CD and click OK.
8. In the Windows Components wizard, click Finish and remove the CD.
9. In the Add/Remove Programs dialog box, click Close.

IPX Service Installation

The NWLink IPX/SPX Compatible Transport (IPX) network software is an optional component of the Windows NT/2000 operating system, which you can install if you need to discover and monitor IPX nodes.

Windows NT operating system:

1. In the Start menu, select Settings:Control Panel.
2. In the Control Panel, double-click on the Network icon.
3. In the Network dialog box, select the Protocols tab.
4. Select the Add... button.
5. Select the NWLink IPX/SPX Compatible Transport item.
6. Select the OK button.
7. When prompted, enter the path to the I386 directory, such as

   drive_letter:\I386

8. In the Network dialog box, select OK.
9. In the Network Settings Change dialog box, select the Yes button to establish your IPX changes by restarting the Windows NT operating system.

Windows 2000 operating system:

The NWLink IPX/SPX Compatible Transport (IPX) network software is an optional component of the Windows 2000 operating system, which you can install if you need to discover and monitor IPX nodes.

1. In the Start menu, select Settings:Control Panel.
2. In the Control Panel, double-click on the Network and Dial-Up Connection icon.
3. In the Network and Dial-Up Connection dialog box, right-click the Local Area Connection icon and click on Properties. Look at the list. If NWLink IPX/SPX/NetBIOS Compatible Transport Protocol does not appear, do the following:
   1. Select the Install... button.
   2. Select the Protocol item.
   3. Select the Add button.
   4. Select NWLink IPX/SPX/NetBIOS Compatible Transport Protocol and click OK.
   5. In the Local Area Connection dialog box, click Close.

DHCP Setup

Users of the Dynamic Host Configuration Protocol (DHCP) need to ensure that their NNM management station is assigned the same IP address each time it runs NNM.

You can specify a range of IP addresses that your network is configured to assign dynamically for mobile devices. NNM keeps the map clean and the Alarm Browser list free of unnecessary messages about devices within this address range as they are repeatedly attached and detached from your network. See Managing Your Network with HP OpenView Network Node Manager for more information.

Web Browser Installation

Several of the NNM features are web-based, and require a web browser to be installed on the same system where NNM is installed.

The Java-based graphical interfaces require the Java plug-in (JPI).

Refer to the Release Notes for supported web browsers and JPI installation information. You can access the Release Notes from the CD. The Release Notes are in the README.html file.

From the left pane of the Release Notes, double-click on Supported Configurations.

To install the browser, follow the instructions that came with it. Be sure to configure any web proxies according to the browser's instructions.

Web Server

A web server product must be installed on the same system where NNM is installed.

Windows NT operating system:

You must install the web server that comes with Windows NT 4.0 Option Pack. Refer to the following Microsoft web site for information on web servers:
http://www.microsoft.com/ISN/prod_tech.asp

Windows 2000 operating system:

To verify that a web server product is installed, do the following:

1. In the Start menu, select Settings:Control Panel.
2. In the Control Panel, double-click on the Add/Remove Programs applet.
3. In the Add/Remove Programs dialog box, select the Add/Remove Windows Components button.
4. The Windows Components wizard appears. Scroll down to the Internet Information Services. If this box is already selected, then the web server is already installed. If the web server is not listed, then do the following steps:
   1. Select the Internet Information Services (IIS) check box.
   2. Click Next and wait while the wizard configures components.
   3. When prompted, insert the Windows 2000 operating system CD and click OK.
   4. In the Windows Components wizard, click Finish and remove the CD.
   5. In the Add/Remove Programs dialog box, click Close.

Microsoft Data Access Components Check

The Network Node Manager Database requires ODBC components from the Microsoft Data Access Components product. In particular, two of the DLLs must be of the same version for NNM to be able to connect to the database. The DLLs are %SystemRoot%\system32\odbcint.dll and %SystemRoot%\system32\odbc32.dll.

Windows NT operating system:

To verify these DLLs are the same version, compare the version numbers by doing the following.

1. In the Start menu on the Windows NT operating system task bar select the Settings:Control Panel item.
2. In the Control Panel, double-click on the ODBC item.
3. In the ODBC Data Source Administrator dialog box, select the About tab.
4. Compare the version numbers shown in the Version column for the files odbcint.dll and odbc32.dll.

If the files are the same version, then no further action is necessary.

If the files are not the same version, you must reinstall the Microsoft Data Access Components product. You can download the latest version of these components from: http://www.microsoft.com/data/download.htm

Windows 2000 operating system:

1. In the Start menu on the Windows 2000 operating system task bar select the Settings:Control Panel item.
2. In the Control Panel, double-click on the Administrative Tools icon.
3. In the Administrative Tools dialog box, double-click on Data Sources (ODBC).
4. Select the About tab. Compare the version number for the files odbcint.dll and odbc32.dll.

If the files are the same version, then no further action is necessary.

If the files are not the same version, you must reinstall the Microsoft Data Access Components product. You can download the latest version of these components from: http://www.microsoft.com/data/download.htm

Microsoft Terminal Services--Optional

The Microsoft Terminal Services software is an optional component of the Windows 2000 operating system. Install this software if you want to connect to NNM on a Microsoft terminal server from a remote workstation through a terminal server client.

Windows 2000 operating system:

1. In the Start menu on the Windows 2000 operating system task bar, select Settings:Control Panel.
2. In the Control Panel, double-click on the Add/Remove Programs applet.
3. In the Add/Remove Programs dialog box, select the Add/Remove Windows Components button.
4. The Windows Components wizard appears. Scroll down and select Terminal Server Services.
5. Select the OK button.
6. Click Next and the wizard guides you through the installation.

Note

If you install Microsoft Terminal Services in Application server mode, and if you do not use the Add/Remove installation program to install NNM, then to ensure that NNM installs correctly, you need make sure that the Application install mode is enabled on the server. To do this, use the change user command. Refer to the Microsoft documentation for information on this command.

Windows NT Service Pack Reinstallation--Required

Once you have finished installing all the required services and any optional/relevant software products, you must reinstall the latest Windows NT Service Pack. This is necessary because some portions of the service pack file were removed while you were installing the other services listed earlier in this task section.

Refer to the Release Notes for supported configurations. You can access the Release Notes from the CD. The Release Notes are in the README.html file.

From the left pane of the Release Notes, double-click on Supported Configurations.

Task 3: Installing Network Node Manager

If you purchased HP OpenView Customer Views for NNM, you received two CDs. Each CD is installed separately. Follow the procedure below.

Windows NT operating system:

1. If you are upgrading from a prior version, be sure that NNM is not running, and that no HP OpenView processes are running.

2. Insert the NNM CD into the CD-ROM drive. The Install Shield setup wizard program starts automatically. If it does not,

1. From the Start menu on the Windows NT operating system task bar, select Settings:Control Panel.
2. Select Add/Remove Programs.
3. In the Add/Remove Programs Properties dialog box, at the Install/Uninstall tab, select Install... .

Refer to the Both Windows NT and Windows 2000 operating systems section for more steps.

Windows 2000 operating system:

1. In the Start menu on the Windows 2000 operating system task bar, select Settings:Control Panel.

2. In the Control Panel, double-click on the Add/Remove Programs applet.

3. In the Add/Remove Programs dialog box, select the Add New Programs button.

4. Insert the NNM product disk into the CD-ROM drive. Click on CD or Floppy button.

5. The Install Program from floppy disk or CD dialog box appears. Click Next.

6. Verify that the correct path is showing, and click Next.

Refer to the Both Windows NT and Windows 2000 operating systems section for more steps.

Both Windows NT and Windows 2000 operating systems

The Install Shield wizard begins and guides you through all the necessary steps in the installation process.

1. In the Setup Options dialog box, choose the NNM installation you want to do (the following table describes each installation type):
   

   Installation Type	NNM Components Installed	Description about Installation Type
   Typical	- executable program files - background graphics - online user manuals
   Remote Console	See the manual, A Guide to Distribution and Scalability for Network Node Manager, for instructions on doing this installation.	Your system will: - have only HP OpenView Windows processes on it - connect to a management server running the NNM common databases and background processes
   Compact	- executable program files
   Custom	Choose from: - executable program files - background graphics - contributed applications - SNMP MIBs - SNMP RFC papers - technical white papers	You can specify which NNM components you want to install.

2. Choose the installation type you want. The wizard then displays several graphics showing the progress of the installation.

3. If errors occur during the installation, the wizard will ask if you want to view the setup log file.

4. When the Setup Complete dialog box appears, the wizard has finished the installation. You are presented with the following options:
   • Display the NNM Release Notes
   • Start NNM immediately
   If you are also installing HP OpenView Customer Views for NNM, do not choose "Launch NNM." NNM should not be running when you install HP OpenView Customer Views for NNM. Choose the options you would like, then select Finish.

5. Remove the NNM CD from the CD-ROM drive.

6. If you also purchased HP OpenView Customer Views for NNM, install it now.
   1. Be sure that NNM is not running.
   2. Insert the HP OpenView Customer Views for NNM CD into the CD-ROM drive. Follow the installation procedures outlined for the NNM installation. You will not be prompted to choose an installation type.

Installing NNM using Microsoft's System Management Server (SMS)

This section provides instructions on how to install HP OpenView NNM using Microsoft's System Management Server (SMS). The setup.pdf and setup.iss files at the root level of the NNM CD enable NNM to meet Microsoft BackOffice Certification requirements. This sections assumes that you are familiar with the general functionality of SMS.

Description of the files:

setup.pdf		The package definition file for the NNM product
setup.iss		Sample response file for the NNM silent installation. This file used together with setup.pdf can provide unattended installation through SMS.

Note

If the flow of execution for your desired installation does not match the flow of execution when the sample setup.iss file was created, the silent installation will fail. Generally, you will need to create your own setup.iss file for your specific system configuration. Please refer to the bullet item below (How to create a setup.iss file) for more details.

• How to create a setup.iss file:
  1. Run setup.exe -r from Start->Run to install NNM with the -r option. The -r option causes setup.exe to automatically generate a response file (setup.iss) for the NNM silent installation. The setup.iss file is the record of your input to the installation prompts. After the interactive installation finishes, the setup.iss file is stored in the Windows folder (for example, C:\WINNT).
  2. Copy the newly created setup.iss file from the Windows folder to the same directory as the setup.exe file. This will replace the setup.iss sample file and will be used together with the setup.pdf file provided to complete the silent installation.
• Miscellaneous notes about SMS installations:
  
  When the sample setup.iss file was created, NNM was installed in the D:\Openview directory. Since NNM SDK was installed after NNM runtime, the Install Shield log file name was D:\OpenViewDeIsL1.isu for NNM runtime, and D:\OpenViewDeIsL2.isu for the NNM SDK. If you are installing NNM in another directory, or have different Install Shield log files (*.isu), you need to change the setup.pdf files correspondingly to reflect the location of NNM installation, and the Install Shield log file so that the automated uninstall through SMS can run correctly.

Task 4: Running Network Node Manager

If you did not automatically launch NNM at the end of the installation process, you can use the following procedure to do so now.

1. First, start the background processes that support the NNM native graphical user interface (GUI), HP OpenView Windows. From the Start menu on the Windows NT operating system task bar, select Programs:HP OpenView:Network Node Manager Admin:NNM Services-Start.
2. Next, start HP OpenView Windows. Select Programs:HP OpenView:Network Node Manager.
   
   You will see the HP OpenView welcome banner, followed by an NNM Root submap window with a default map in it.
3. Each time you start the NNM GUI, it will encourage you to register your NNM product if you have not already done so. You have 60 days from the date of installation to complete this registration process (described in Task 5).
4. Note that some of the newer NNM features are web-based, meaning they will not run within the native HP OpenView Windows GUI. To use these features, see Task 6 for instructions on how to configure NNM to run within the HP OpenView Web environment.

Note

When running Customer Views for NNM, you should modify the IP Map configuration to set the persistence level to ALL LEVELS (Map Properties menu, Configure IP Map dialog box, OnDemand:All Levels). When these configuration items are not set as recommended, you may see irregularities in the status presentation of network resources with the Customer View submaps. This is characterized by symbols that are presented with a status of "Unknown" while, within the submap hierarchy, the node has some other, known status value.

Task 5: Registering Your Network Node Manager Product

Your NNM product was shipped with a license that includes a temporary, "Instant-On" password. This password allows you to use the product for 60 days after you install it. Once you have installed NNM, optionally, HP OpenView Customer Views for NNM, you should register them with Hewlett-Packard as soon as possible in order to obtain a permanent password.

A permanent password is required if you want to run NNM on a management station or collection station. An additional password is not required to run NNM on a remote console.

One permanent password is required for NNM and a second one is required if you purchased and installed HP OpenView Customer Views for NNM. You need to follow these steps for each of these product components.

There are three steps to do in this task:

• Gathering information needed in the License Request Form.
• Completing this form and sending it by any of several methods to a Hewlett-Packard Password Delivery Center (HP PDC).
• Installing into your NNM product the permanent password that the HP PDC sends back to you.

Step 1: Gathering Information for the License Request Form

You will need to locate several pieces of information in order to fill out the License Request Form. This information appears in two places: on the Entitlement Certificate shipped with NNM and HP OpenView Customer Views for NNM and in an online dialog box (described in Step 5 below).

1. On your Entitlement Certificate, find the two numbers listed below and write them down:

   For NNM:

   HP order number _____________________________
   HP product number ___________________________

   For HP OpenView Customer Views for NNM, if installed:

   HP order number _____________________________
   HP product number ___________________________

2. If NNM
   • is already running and displaying a dialog box which asks, Request your password now?, select OK.
   • is already running, but no dialog box is showing, run the ovnnmPassword utility. Go to either:
     • The Start menu and select the Programs:HP OpenView:Network Node Manager Admin:License Password item.
     • The Options menu and select the License Password item.
     • The Start menu and select Run, then type ovnnmPassword.
   • is not currently running, run the ovnnmPassword utility. Go to either:
     • The Start menu and select the Programs:HP OpenView:Network Node Manager Admin:License Password items.
     • The Start menu and select Run, then type ovnnmPassword.
3. The License Password dialog box appears. This box has three options:
   • Current Password lists any passwords already assigned to the NNM product you are currently running.
   • Request Password takes you to the next step in requesting a permanent password.
   • An empty field box lets you enter a permanent password into your NNM product's files.
4. Select the Request Password button.

5. The Request Password dialog box appears. This box will display your IP address. Write it below:

   IP address _________________________________

Step 2: Completing and Sending the License Request Form

In this step, you first need to choose the method for sending your license request to the HP PDC. Once you select a method, you will be given the correct License Request Form to complete. There are four ways to send your License Request Form:

• By using the online HP PDC web site.
• By sending electronic mail (e-mail) to the HP PDC.
• By faxing a form to the HP PDC.
• By telephoning the HP PDC.

The web site is the quickest method, as it will return to you a permanent password immediately after you send in your request form. The e-mail, fax, and telephone methods will deliver a permanent password to you within 24 hours.

1. The Request Password dialog box should still be on screen. Select either the Web button to go to the web site, or the Form button to request your license by e-mail, fax, or telephone.

   If this dialog box is not on your screen, you can either run the ovnnmPassword utility again and then select the appropriate button; or you can go directly to the web site by typing the following URL in your web browser's Location field:

   http://www.webware.hp.com

2. Fill out the License Request Form that is displayed. (Note: if you are using the web method, write down the Session ID number displayed in the top right corner of the Password Delivery Service window. This number will be helpful should you need to contact the HP PDC about your password.)

3. To send your completed License Request Form to an HP PDC:
   • At the web site, follow the instructions shown there.
   • By e-mail, save the form as a file and then use your mail program to send it to the appropriate location shown in the following table.
   • By fax, print out the form and then fax this printout to the appropriate telephone number shown in the following table.
   • By telephone, print out the form to refer to, and call the appropriate telephone number shown in the following table.
   
   

   Your Geographic Region	E-mail Address Fax Number Telephone Number			Hours of Operation (local time)
   North & South America	americas_password@cnd.hp.com Fax: (USA) +1 (801) 431-3654 Telephone: (USA) +1 (801) 431-1597			8 a.m. - 8 p.m. (EST)
   Asia/Pacific	asia_password@cnd.hp.com Fax inside Japan: (03) 3227-5238 Fax outside Japan: +81 (3) 3227-5238 Telephone inside Japan: (03) 3227-5264 Telephone outside Japan: +81 (3) 3227-5264			9 a.m. - 5 p.m. (JST)
   Europe/Africa	europe_password@cnd.hp.com Fax: (Holland) +31 55-543-4645 Telephone: (Holland) +31 55-543-4642			8 a.m. - 5 p.m. (UK)

   
   
4. The HP PDC will send you your permanent password by the same method you requested it; occasionally, a different method might be used in case of problems, such as a fax machine being turned off or an e-mail message being mis-sent.

   If you have not received your permanent password within 24 hours, contact the HP PDC at the telephone numbers shown in the preceding table.

5. If you have HP OpenView Customer Views for NNM installed, repeat these steps to obtain your password for it.

Step 3: Installing the Permanent Password into NNM

The final step in this task is to install the permanent password into NNM. If you have HP OpenView Customer Views for NNM installed, you need to perform this task twice, once for each of the passwords that you received. There are two ways to do this.

If your "Instant-On" temporary password is still valid, use the following method:

1. Start NNM, if it is not already running. The License Password dialog box will appear.

2. If you received your permanent password from the web site, move the window containing the password certificate to one side of your screen so you can see it as well as the License Password dialog box.

3. From the dialog box, cut and paste, or type, the permanent password (and any string enclosed in double quotation marks appearing after the password) in the blank field.

4. Select Apply. A dialog box appears, confirming your password's installation.

5. If you have HP OpenView Customer Views for NNM installed, repeat these steps for your second password.

If your "Instant-On" temporary password has expired and you cannot start up NNM, use the method below instead.

1. Run the ovnnmPassword utility. Go to either:
   • The Start menu and select Programs:HP OpenView:Network Node Manager Admin:License Password.
   • The Start menu and select Run, then type ovnnmPassword.
2. The License Password dialog box appears. Type the permanent password (and any string enclosed in double quotation marks appearing after the password) in the blank field.

3. Select Apply. A dialog box appears, confirming your password's installation.

4. If you have HP OpenView Customer Views for NNM installed, repeat these steps for your second password.

Task 6: Configuring Network Node Manager for the Web

In Task 6, you will configure NNM so that you can also run it within the HP OpenView Web environment, via the HP OpenView Launcher GUI. Doing so will enable you to use the NNM features that are web-based. (In Task 4, you had configured NNM to work only via its native HP OpenView Windows GUI.)

Running NNM on the Web

1. Install, if necessary, your web server and web browser products.

2. If NNM is running, exit it.

3. Restart the NNM background processes. From the Start menu on the Windows NT operating system task bar, select Programs:HP OpenView:Network Node Manager Admin:NNM Services-Start.

4. Restart the HP OpenView NNM GUI. From the Start menu, select Programs:HP OpenView:Network Node Manager.

5. Start up, if necessary, your web browser product.

6. To run NNM within the HP OpenView Web environment via the HP OpenView Launcher GUI, use either method below:
   • If NNM is running on your system, select the Tools:HP OpenView Launcher item from the NNM menu bar. The Launcher window will appear.
   • If NNM is running on a system other than yours, open up a web browser on your system. In the browser's Location field, specify one of the following URLs:
     • (For a system running HP-UX/Solaris)

       http://hostname:8880/OvCgi/ovlaunch.exe

     • (For a system running Windows NT/2000 operating systems)

       http://hostname/OvCgi/ovlaunch.exe

       where hostname is the full domain name of your web server (such as mymachine.myco.com).

   If You Have NNM Installed, but no Web Server Product yet...

   If your NNM system does not yet have a web server product, see Web Server. Reinstall NNM after installing a web server. The reinstallation of NNM will properly configure it to use your web server product.

   Uninstalling Network Node Manager or Customer Views for NNM

   If you need to remove Network Node Manager or HP OpenView Customer Views for NNM from your computer, follow these steps.

   1. From the Start menu, select Programs:HP OpenView:Network Node Manager Admin:NNM Processes-Stop
   2. Once the dialog box confirms that the processes have stopped, from the Start menu select Programs:HP OpenView:Network Node Manager Admin:Uninstall HP OpenView Customer Views or Uninstall Network Node Manager.

   Where to go Next...

   Once you have installed and licensed your NNM product, you will want to configure it to best meet your needs. Refer to Managing Your Network with HP OpenView Network Node Manager for guidance about configuring NNM. The following table lists several sources that can help you get started using NNM. A more comprehensive list of information sources is provided in Chapter 3 of the printed manual, Managing Your Network with HP OpenView Network Node Manager.

   
   

   Type of Information	Specific Sources
   Hewlett-Packard Support	Go to the HP OpenView web site at the following URL: http://www.openview.hp.com/
   User Documentation	These are available in printed format, online format, or both. For document descriptions, refer to Chapter 3 of the printed manual, Managing Your Network with HP OpenView Network Node Manager. To access these documents online, in the NNM menu bar select the Help:Online Manuals item.
   Other Online Documentation	Online Help System: In the NNM menu bar, select the Help:Online Help item. Release Notes: These are in the Start menu on the Windows NT operating system task bar, select Programs:HP OpenView:HP OpenView Online Documentation:NNM Release Notes . Get Acquainted with HP OpenView Network Node Manager: Training for NNM Operators: This tutorial is on the CBT CD-ROM included with your NNM product.

Copyright © 2001, Hewlett-Packard Company. All rights reserved.

Network Node Manager 6.2 Runtime Known Problems and Workarounds

For the Windows NT^® 4.0/Windows ^® 2000 Operating System

General Information

Listed below are solutions and workarounds  to problems that have been encountered while using Network Node Manager 6.2 (NNM).

Please also visit the Release Notes addendum at http://ovweb.external.hp.com/nnm/NNM6.2/relNoteUpd/relNoteUpdate.htm for any more recent updates or workarounds.

There is also a troubleshooting section below.

Known Problems

Below are the known problems and workarounds for the following modules:

• Installation
  • HP Openview VantagePoint Operations (VPO, formerly ITO) and NNM Installation Notes
• Licensing
• Known Problems with Web Browsers
• Java-based Web Interface
  • HP OpenView Launcher
  • Network Presenter
  • Report Configurator/Report Presenter
  • SNMP Data Presenter
  • Alarm Browser
  • MIB Browser
  • ECS Configuration Management GUI
• NodeView/CDP View
• Data Warehouse
  • ODBC Mismatch Warning
• Remote Consoles
• Allowing Enough Color Resources
• SNMP Agent Issues
• Internationalization (I18N)/Japanese
• General Troubleshooting

Installation

Window NT 4.0

Be sure to re-install your latest NT service pack after installing any Microsoft components or you will get messages about mismatched ODBC DLLs or the SNMP extension agent will have an exception.  Not re-installing the latest service pack can cause any of the following errors:

• The ODBC resource DLL(C:\WINNT\System32\odbcint.dll) is a different version than the ODBC driver manager (C:\WINNT\System32\ODBC32.dll). You need to reinstall the ODBC components to ensure proper operation.
• The procedure entry point SnmpSvcGetEnterpriseOID could not be located in the dynamic link library snmpapi.dll.
• SsBOpen failed, file 'solid.db', error = 32, retries = 0


Windows 2000 Multi-User Interface (MUI)

Network Node Manager will not install on Windows 2000 with the MUI (Multi User Interface) AKA Multi-Language Pack when the local is set to Japanese. The install wizards display unreadable characters and eventually just exits. The Japanese localized version of Windows 2000 works fine.  The MUI works fine in English and the other locales like French.


HP OpenView VantagePoint Operations (VPO, formerly ITO) and NNM Installation Notes

Dynatext obsoleted

When migrating the NNM component of VPO version 5.3 or 6.0 to NNM 6.2, the obsolescence of Dynatext will leave the "Help->Online Manuals" in place but none of the Dynatext files will exist. When you access "Help->Online Manuals" from the VPO user interface after the NNM 6.2 upgrade, you will get the following error message:
    /usr/bin/sh: dynatext: not found.
Please instead use the PDF version of the VPO manuals. The PDF files are installed into: /opt/OV/doc/C/OpC/.

New OpenView events in NNM 6.2 are unmatched in the VPO Message Browser

New OpenView events (or traps) in NNM 6.2 do not match VPO SNMP trap templates. These will appear in the VPO Message Browser as unmatched SNMP traps in the SNMP message group. OV events with specific trap numbers 58720267 (OV_DataColl_Data), 58982419 (OV_ConnectedIfChg), 58982420 (OV_ConnectedPortGrpChg)and 58982421 (OV_ConnectedPortNumChg) are known to exhibit this behavior.

Migrating the NNM component of VPO 5.3 or VPO 6.0 to NNM 6.2

This update is performed using NNM 6.2's "install" script in the normal manner. If the NNM Data Warehouse is using the Oracle RDBMS instead of the NNM embedded database, then the Oracle software must be updated, if necessary, to a version supported by NNM 6.2. The Oracle update must be performed before the NNM update.

How to install VPO 5.3 or 6.0 on top of NNM 6.2 for HP-UX

For the upgrade of NNM to VPO, a special bundle without NNM is available. HP does not recommend installing the ITOEngOraAll bundle on top of NNM, so please use ITOEngOraAllUp or ITOEngOraMinUp for the upgrade. When ITOEngOra*Up is first installed, no error message should be printed during the installation.

1. When using swinstall UI, "Mark for Install" all VPO components you wish to install such as ITOEngOraAll and ITOEngDoc.
2. Select "Options" then "Change Options..." to bring up the option checklist.
3. Un-check the "Enforce dependency analysis errors in agent" option in the option checklist.
4. Select OK and continue with the installation.

Note: During install you will get several ERROR messages similar to the following messages. You may safely ignore these messages.

ERROR: Skipped (in analysis) OVPlatform.OVMIN,r=B.06.10.00

How to install VPO 5.3 or 6.0 on top of NNM 6.2 for Solaris

For the upgrade of NNM to VPO, a special bundle without NNM is available. HP does not recommend installing the ITOEngOraAll bundle on top of NNM, so please use ITOEngOraAllUp or ITOEngOraMinUp for the upgrade. When ITOEngOra*Up is first installed, no error message should be printed during the installation.

1. Login as user root and cd to the directory where the VPO install bundle is located (usually /cdrom/cdrom0)
2. Copy the install script to /tmp and edit it.
   > vi /tmp/install
3. Search for the swinstall options.
   > /SWOPTIONS
4. Go to the end of the SWOPTIONS line and just before the end quote add:
   -x enforce_dependencies=false
   
   The results could look like this:
   SWOPTIONS="-x loglevel=2 -x write_remote_files=true -x enforce_dependencies=false"
5. Save your changes and continue with the installation by running your modified "/tmp/install" script.

NOTE: During install analysis you may receive several ERROR messages similar to the following message. These messages can be safely ignored.

ERROR: A later revision (one with a higher revision number) of fileset "OVPlatform.OVWIN-BGROUND,r=B.06.10.00" has already been installed.
Either remove this fileset or change the "allow_downdate" option to "true".

Using an NFS mounted CD drive for installation:

When exporting a remote CD drive to be used for installing NNM, you must specifically give 'root' access to the drive. Use a line similar to the following on the machine that has the CD drive installed on it:

• HP-UX
  in /etc/exports
  <mount_point_of_CD> -ro,root=<machine_name_1[:machine2]>
• Solaris
  in /etc/dfs/dfstab
  share -F nfs -o root=<machine_name> <mount_point_of_CD>

Licensing

Running ovnnmPassword (or any other Java application) from Solaris while redirecting the display to a PC running WRQ's Reflection X will cause the Java Runtime Environment (JRE) to crash.  This is a known problem with Java as documented in http://developer.javasoft.com/developer/bugParade/bugs/4079697.html. Reflection X has problems with Sun's JDK 1.1.1 because it looks for fonts that our x server doesn't supply. The workaround is to go into RX Settings | Fonts | Options and enable Allow Font Substitution and Allow Font Scaling.  Of course, if you have a font server on the Sun box, that would be best to configure it and then configure RX to use it in RX Settings | Fonts where you would add the font server to Font Path. You can click on Help in the Font Category for more information about how to use a Font Server.

Requesting Evaluation Licenses for ECS Designer

Use the forms in the $OV_CONF/OVLicense/nnm/forms/C directory to make password requests for the "HP OpenView ECS Designer for NNM and ITO" product. The forms in the $OV_CONF/ecs/forms/C directory are for the standalone ECS Designer product only and should not be used.

Known Problems with Web Browsers

The online manuals cannot be read with Netscape 6.0 and Acrobat reader.  There is an incompatibility with the two.  Please obtain a newer software version or directly open the .pdf files with Acrobat, or use Netscape 4.7x.

Note that there are several defects which are fixed by the newer browsers, but other defects which are introduced by other browsers.  This is especially true with Netscape 4.7x vs. Netscape 6.x.  In general, it is best to try from Internet Explorer on Windows NT/Windows 2000 to determine if the problem is browser related.

Java-based Web Interface - HP OpenView Launcher

• First ensure that you have the latest browser.  See supported configurations for more information on which browsers are supported.

If are still having problems starting the launcher, you may have a configuration problem with your web browser.

Can't get the Java based web Launcher (ovlaunch.exe URL) to come up

• Use the correct URL.
• Windows NT/2000 management station web access:
  http://<MACHINENAME>/OvCgi/ovlaunch.exe
• UNIX management station web access:
  http://<MACHINENAME>:8880/OvCgi/ovlaunch.exe
• Be sure Java/Java Script is enabled
• On Netscape 4.7x or greater:
  Pick Edit:Preferences...;  expand the Advanced tree control; check Enable Java and Enable Java Script
• On Internet Explorer 5.01 or greater:
  Pick View:Internet Options..., pick the [Advanced] tab, go to category Java VM and be sure that "Java JIT compiler enabled" and "Java console enabled (requires restart)" are both checked.
• Be sure you are not using a proxy server
  NNM uses sockets for web connections for the Network Presenter, when configuring ECS, and running jovgraph.  These do not work through a proxy server.  Either turn off your proxy server, or be sure it is disabled for local access.
  • On Netscape 4.7x or greater:
    Pick Edit:Preferences...; expand the Advanced tree control, select Proxies and click Direct Connection to the internet.  Expert users can also adjust the parameters in the "Manual proxy configuration".
  • On Internet Explorer 5.01 or greater:
    Pick View:Internet Options..., pick the [Connection] tab, and check the 'Bypass proxy server for local (Internet) addresses'.  Expert users can use the 'Advanced...' option to adjust the parameters.

 Netscape lock file error message

If you try to bring up more than one instance of Netscape on Solaris or HP-UX, you may get a dialog box stating:

 "Netscape has detected a /home/user/.netscape/lock file.
This may indicate that another user is running Netscape."

Please ignore this message.

Do Not Close Launcher Window

Do NOT close the Launcher window, itself, when launching applications. Some applications use the frames within the Launcher window for executing web scripts. If the Launcher window is closed, it will cause the application that was launched from the window to close. This is particularly true when launching the HP OpenView Network Presenter. The Launcher window may be iconized to remove its presence instead of being closed.

Java-based Web Interface - Network Presenter

(NSMfc25765)
Network Presenter from Netscape6 on Japanese Solaris exited when expanding a node in scoping pane.  The workaround is to use Netscape 4.76 or Internet Explorer from Windows.

(NSMfc25810)
Japanese strings in Report Config's Modify/View windows are garbled.  The workaround is to use Netscape 4.76 or Internet Explorer from Windows.

(NSMfc25965)
Japanese strings corrupted in Network Presenter with Netscape 6.0.  These include the title "Internet", in the title bar, in the upper left option button, and in the scoping pane.  The workaround is to use Netscape 4.76 or Internet Explorer from Windows.

Java-based Web Interface - Report Configurator/Report Presenter

(NSMfc25809)
The Report Configuration window does not display properly on Solaris Netscape 6.01A.  The work-around is to view the page with Internet Explorer on Windows.

(NSMfc25938
The Report Configuration and Report Presenter windows occasionally hang if resized on Solaris Netscape 6.01A.  The work-around is to view the page with Internet Explorer on Windows or do not attempt to resize.

(NSMfc25990)
The Report Configuration wizard does not display the "Node", "Interface", and "Sys Object Type" labels properly on Solaris Netscape 6.01A.  The work-around is to view the page with Internet Explorer on Windows.

Java-based Web Interface - SNMP Data Presenter

If using a proxy server, and the DNS server running on the proxy server cannot resolve an NNM data presenter hostname, the graphic lines for the tree structure cannot be located, and will appear as generic icon symbols. If this happens, disable use of the proxy server, clear the browser caches, and reload the page. If the problem persists, modify the http configuration file on the http server to provide the fully qualified name of the http server:

• http server running on UNIX systems:
  The configuration file is /opt/OV/httpd/conf/httpd.conf, and the entry to be modified is the ServerName entry. After saving the new configuration, you must restart the http server. This is accomplished with ovstop followed by ovstart.
• http server running on Windows NT/2000 systems:
  Ensure that your web server provides a fully-qualified hostname for your http server.

(NSMfc25766)
The SNMP Data Presenter scoping window does not display properly on Solaris Netscape 6.01A (it should show "Network Activies", "System", etc).  The work-around is to view the page with Internet Explorer on Windows.

Java-based Web Interface - Alarm Browser

When the Web Alarm Browser is connecting to an NNM  management station running on Windows NT/2000, printing only works with a local printer connected to that Windows NT based management station. The printer must be configured on one of the following ports LPT1(PRN), LPT2, or LPT3.

(NSMfc25767)
With Netscape 6.0 the Alarm Browser will go away by picking File: Save on Server-> Selected...
The workaround is to use Netscape 4.76

Java-based Web Interface - MIB Browser

(NSMfc25764)
With Netscape 6.0 the Web-based MIB Browser cannot expand the MIB tree properly. The workaround is to use Netscape 4.76 or Internet Explorer from Windows.

Java-based Web Interface -  ECS Configuration Management GUI

(NSMfc25769)
With Netscape browsers on HP-UX or Solaris, the [Modify...] button does not open Modify dialog box.  The work-around is to use a Windows-based Internet Explorer browser.

Java-based Web Interface - NodeView/CDPView

Changing labels in ovw will not affect the label seen in NodeView or CDPView.  This is because the labels come from topology, and ovw stores labels locally.

Data Warehouse

When using databases other than the embedded database, the user needs to manually instantiate the data warehouse schemas using ovdwsetup.ovpl before using the data warehouse.

Using Oracle:

All export tools are enabled for ODBC.  To use Oracle, sql*net must be installed and configured.  A default datasource has been configured in the /etc/opt/OV/share/conf/analysis/system_odbc.ini file, OVoracle.  To switch over, change the "ServerName" parameter in that file to your server as defined in tnsnames.ora.
Then run:

"ovdwsetup.ovpl -rdb OVoracle -type oracle -u <DBuser> -password <pass>", where <DBuser> is your oracle user and <pass> is that user's password.  Oracle user OSauthentication is no longer supported.

-> To configure $ORACLE_HOME for use by the NNM Data Warehouse tools, you can use the "env" parameter on ovdwsetup.ovpl to place the value of ORACLE_HOME in the ovdwenvs.conf file. For example:

/opt/OV/bin/ovdwsetup.ovpl -env "ORACLE_HOME=/opt/oracle/product/7.3.3" \ -type oracle -rdb OVoracle

Oracle SID may be misconfigured on HPUX and Solaris systems

On HPUX and Solaris systems, the file listener.ora may be misconfigured to have the Oracle SID set to "openview" even if the Oracle SID is not "openview". Rerunning ovdbsetupo3.sh will report this as an error if  $ORACLE_SID is not "openview". To correct this, edit listener.ora to the name to be the value of $ORACLE_SID.

The file can be located at:

HPUX 10.X/HPUX 11.X: /etc/listener.ora
SOLARIS 2.X: /var/opt/oracle/listener.ora

Unresolved references in ovdwquery or ovacomm failing

The configuration of the Data Warehouse to use Oracle 7.3.4 on HPUX 10.20 needs to rebuild Oracle client library libclntsh.sl. This operation requires that Oracle fileset Pro*Cobol be installed. To ensure that the library can be rebuilt, verify that the file $ORACLE_HOME/precomp/lib/cobsqlintf.o exists on the system. If it does not, then install Pro*Cobol from the Oracle CD prior to configuring the database.

If upgrading NNM or if ITO is installed, then it is possible that an attempt to configure the Data Warehouse has been done. For ITO users, the symptom is that the ITO daemon ovacomm fails, as reported by ovstatus, with a message reporting that it received a signal 6. This signal implies that there are unresolved references, and these are due to libclntsh.sl not being correctly rebuilt. NNM processes, such as ovdwquery, will also fail with unresolved references.

To validate that configuration has been done, check for the existence of the file $OV_CONF/ovdbconf. If this file exists, then it is recommended that libclntsh.sl be rebuilt. The steps are:

1. Install Oracle fileset Pro*Cobol from the Oracle CD if necessary.
2. Run ovstop to stop all daemons.
3. If /etc/listener.ora exists, check for the list SID_NAME=openview. If this is not the Oracle SID, then edit the list to have the correct Oracle SID.
4. Run ovdbsetupo3.sh and answer the prompts. There will be errors for exiting tablespaces, but these can be safely ignored.
5. Afterwards, run ovstart. If ITO is installed, then ovacomm should work.
6. For NNM, run ovdwquery to validate that access to the database exists.

Using ovbackup and the NNM Data Warehouse

If you are using ovbackup.ovpl and are using the NNM Data Warehouse, when the ovbackup.ovpl command is executed, it will also instruct the Embedded Database server to initiate the online backup. In order to allow a roll-forward recovery the default backup schedule must be deactivated. The process for doing this is:

1. copy the $OV_DB/analysis/default/solid.ini file to $OV_DB/analysis/default/solid.ini.old file.
2. Edit the $OV_DB/analysis/default/solid.ini file.
3. Comment out the "At=<time> backup" entry, by inserting a ";" at the beginning of the line. An example would be:
   ;At=01:00 backup
4. Save the $OV_DB/analysis/default/solid.ini file.

The embedded database will now be backed up only when the ovbackup.ovpl command is run. If use of ovbackup.ovpl is stopped at a future this, the default backup should be reinstated by copying the $OV_DB/analysis/default/solid.ini.old back to $OV_DB/analysis/default/solid.ini.

Restarting the Data Warehouse after a reboot on Windows NT/2000

When using SQL Server, it is important to stop OpenView with the ovstop command prior to rebooting. Failure to do this may cause ovdbcheck to fail when OpenView restarts. The reason for this is because SQL Server is still recovering from the reboot when ovdbcheck tries to reconnect. To workaround this problem, simply wait for SQL Server to finish its recovery, then issue another ovstart.

Reinstall Service Packs

You must reinstall your Windows NT service pack after adding any Microsoft Components such as Microsoft Peer Web Services, or you will see the following error (or an SNMP error).

ODBC Version Mismatch dialog:

You may get an "ODBC Driver Manager" pop-up window for a version mismatch for various ODBC utilities such as:
        The ODBC resource DLL (C:\WINNT40\System32\odbcint.dll) is a different
     version than the ODBC driver manager (C:\WINNNT40\System32\ODBC32.dll).

You need to reinstall the ODBC components to ensure proper operation. This happens if you install *any* application which supplies ODBC components, not necessarily just NNM.  The only way to prevent  this pop-up is to reinstall your last Service Pack. NNM does NOT include any Windows NT ODBC components. This mismatched DLL problem is a known issue with Windows NT.  Further information can be retrieved from Microsoft Article PSS ID Number: Q170769.

Remote Consoles

For Japanese Windows NT/2000 Remote Consoles connecting to HP-UX or Solaris Management Stations, the 3rd party NT NFS product must be able to resolve the Japanese_Japan.932 symbolic links in the registration, symbols, and conf subdirectories. If the ovw menus and symbols on the Remote Console are in English, this means that the symbolic links are not working correctly. For the third party NFS product Disk Access, you need to enable symbolic links from the Disk Access applet in the Control Panel, not from the Administrator Utility.   The default for Disk Access is to not enable symbolic links.

Allowing Enough Color Resources

No known problems on Windows NT/2000. Using Netscape 4.6 or greater:
Netscape may use most of your color palette, causing NNM to have problems displaying colors properly. To correct the problem caused by Netscape, use the -install option:

Open the file  /etc/opt/OV/share/conf/ovweb.conf
Change the line:
    Browser: /usr/local/bin/netscape %s
to:
    Browser: /usr/local/bin/netscape -install %s

This instructs Netscape to allocate its own independent color palette, freeing NNM and Dynatext to use a separate default color palette. Other applications may also use a disproportionate number of colors causing the same effect.

SNMP Agent Issues

NNM management station running on Windows NT/Windows 2000 (interaction with Microsoft's SNMP service)

When you install NNM, the Microsoft SNMP Agent will be effectively disabled by causing it to listen for incoming SNMP requests at an unused Non-Standard port instead of port 161. During installation, NNM modifies the %SystemRoot%\system32\etc\services  file. This will allow Microsoft's snmp.exe to continue to run, and to allow other applications which depend on the Microsoft agent to properly install, but no SNMP requests will be directed to Microsoft's SNMP service.

The SNMP Research Emanate SNMP Agent (snmpdm.exe) and adapter (wpaagt.exe) will instead be used to process the SNMP requests. Microsoft SNMP Service installation is required so that the Microsoft extension agents are installed (all SNMP agent extension DLL's are still used, only the Microsoft main agent is not used).

NOTE: All information entered in the "Microsoft SNMP Properties" dialog will be ignored. All configuration MUST be done through the \<install_dir>\conf\SNMPAgent\snmpd.conf file. This information includes SNMP trap destinations and community names.

NNM management station running on Solaris 2.5 (interoperability of "snmpdm" and "snmpdx")

NNM installation in Solaris 2.6 will kill "snmpdx" (Solstice Enterprise Relay Agent), if running, and will restart it on an unused Non-Standard port.

The start-up script for "snmpdm" (Emanate Master Agent) will set the environmental variable SR_SNMP_TEST_PORT to 161 and start "snmpdm" in port 161.

The following changes should be done manually for "snmpdx" to co-exist with "snmpdm" on Solaris 2.6:

• Starting "snmpdx" will now fail, even if the machine is rebooted since "snmpdm" will first occupy port 161. To overcome this, you should start "snmpdx"  with the option "-p <port_number>" to make it start at an unused Non-Standard port <port_number>, instead of 161. You can do this by modifying the "snmpdx" start-up script i.e. "/etc/init.d/init.snmpdx".
• "naaagt" (Native Adaptor Agent) which is a subagent to "snmpdm", will route SNMP requests to "snmpdx". Refer to to the man page of "naaagt(1M)" for details on how to configure "naaagt" to forward SNMP requests to snmpdx.

NOTE: In Solaris 2.6, "snmpdm" should never be started on command line. You should either use "snmpdm" start-up script i.e. "/sbin/init.d/SnmpMaster" or the "/usr/sbin/snmpd" script to start "snmpdm".

Internationalization (I18N)

Using NNM in Japanese language mode on Solaris 2.6

HP OpenView Launcher and Network Presenter utilize the operating system's "iconv" libraries to convert data stored in the OV Launcher registration files and the OVW registration files into Unicode. This iconv library on Solaris 2.6 has a defect where it incorrectly converts the ASCII "~" and "\" characters when iconv is applied to Japanese data (Shift-JIS or EUC). This defect has been corrected by Sun Microsystems via Solaris patch ID "106613-01". You may need to install patch 106613-01 to your Solaris 2.6 if any of your Japanese (Shift-JIS or EUC) registration files (for OV Launcher or OVW), installed on Solaris 2.6, contain ASCII "~" or "\" characters.

Unsupported Java-based NNM features with Netscape 4.7x

The information below is needed for all users when using NNM's Java-based programs in Japanese language mode on all platforms.

(NSMfc12758)
The HP OpenView Launcher and Network Presenter Java-based NNM features are not supported on Netscape 4.6 on HP-UX, Solaris, and Windows NT/2000 in Japanese for both Shift-JIS and EUC locales. This is due to a Netscape defect, bug ID 316500. Until this defect is fixed, these two tools will not be supported on Netscape  under Japanese. The Java-based Alarm browser and ECS Configuration Management tool are unaffected by this defect and hence, can be used in Japanese mode under Netscape. However, they cannot be started from the Launcher. To start up the Web-based Alarm Browser without using the Launcher, enter one of the following URLs:
    http://<MACHINE>/OvCgi/ovalarm.exe (to access an NNM  management station running on Windows NT/2000)
    http://<MACHINE>:8880/OvCgi/ovalarm.exe (to access an NNM  management station running on UNIX)

To start up ECS Configuration Management tool without using the Launcher, enter one of the following URLs:
    http://<MACHINE>/OvDocs/C/ecs/ecscmg.html (to access an NNM  management station running on Windows NT/2000)
    http://<MACHINE>:8880/OvDocs/C/ecs/ecscmg.html (to access an NNM  management station running on UNIX)

It is hoped that a future version of Netscape will allow support of these tools.

Using ECS Configuration Management tool on Japanese Windows NT/2000

When the ECS Configuration Management tool is launched in Japanese on Windows NT/2000 using any WEB browser, the resulting display will be partially English and partially Japanese. The correlation specific information is displayed in English. However, the tool-specific information (correlation independent information) is displayed in Japanese. This problem will be corrected in a future patch. In the interim, there is no workaround.

Using ja locale on Japanese Solaris 2.X

NNM supports both ja and japanese locale for EUC codeset on Solaris. However, when LANG is set to ja, NNM tools will be partially English and partially Japanese. To correct this problem, do the following as root:

    cd /opt/OV/lib/nls/ja
    rm japanese
    mv * ../japanese/.
    cd /opt/OV/lib/nls
    rmdir ja
    ln -s /opt/OV/lib/nls/japanese /opt/OV/lib/nls/ja

Stop ovw, and restart NNM processes:
    ovstop
    ovstart
    ovw


Data Warehouse

There are a number fields in the Data Warehouse that contain localized data. These fields are:

• the "text" field in the nnm_event_cat table
• the "text" field in the nnm_event_sev table
• the "message" field in the nnm_event_detail table
• the "high_time" field in the nnm_event_thresh table
• and the "low_time" field in the nnm_event_thresh table

As a result of the localized data in the nnm_event_cat table, the data in the "Alarm Category" column of the Alarms By Category report will be localized. In addition, the data in the "category" column of the "Alarms By Severity" detail report will be localized. As a result of the localized data in the nnm_event_sev table, the data in the "Alarm Severity" column of the Alarms By Severity report will be localized. In addition, the data in the "Severity" column of the "Alarms By Category" detail report will be localized. As a result of the localized data in the nnm_event_detail table, certain text in the message fields of both the Alarms By Severity and the Alarms By Category will be localized.

The "high_time" and "low_time" fields from the nnm_event_thresh table are not used in any of the reports provided with NNM. These fields are localized because they are populated from a localized version of the trapd.conf file by ovdwevent. The version of trapd.conf that is used as a data source is determined by the local set when ovdwevent is run.

Printing with Web-based Alarm Browser

The web-based alarm browser does it's printing through ovalarmsrv.  The printer connected to the machine running ovalarmsrv must support 2byte characters in order to print Japanese output.  There is no way to pass arguments to the printer, so the printer must have something similar to a '-japanese' option enabled by default to the lp command.

Printing Submaps on Unix with ovw

If you need to pass options to your printer so that it will print in landscape and Japanese, you can set the environment varialbe OVwLpOpts before running ovw, so that the time string at the bottom of the printed output will print properly.  For example, you can set:
    export OVwLpOpts="-olandscape -ojapanese"

Do Not Intermix Locales with the Topology/Map Databases

When NNM is first installed, the topology/map databases will contain labels in that locale.  Submap names are created in this locale, and should be accessed through that same locale.

You must plan which language will be used for NNM. Once a locale is chosen, it is very hard to change it. This is because NNM does not support mixed locale string in the topology and map databases. Once it is decided which locale is to be used, perform the following steps.

1. Set $LANG to the desired locale. (e.g. LANG=ja_JP.SJIS; export LANG)
2. Install NNM with exported LANG environment
3. Stop OV processes (ovstop)
4. Re-start OV process with desired LANG environment (ovstart)
5. Setup Bootup scripts. Edit /sbin/init.d/ov500 as follows (this example uses SJIS on HP-UX):
       'start')
           if .........
           case `uname` in
            ...........
           HP-UX)
               ECHO_CMD=$ECHO_CMD_HP
               OVHOME=/opt/OV
               PATH=/bin:/usr/bin:/etc:$PATH
               export PATH LANG=ja_JP.SJIS # Add following 2 lines
               export LANG                               # if want to set LANG=SJIS
               ;; 
6. Set the default WEB locale if you want to change locale from default:
   # ovchange_locale_mapping [-sjis | -euc]
   (Default locale)
   HP-UX ja_JP.SJIS
   Solaris ja

Troubleshooting

TIP: Look in the following directories for error log files and trace output. Look for the keyword "ERROR":

• Windows NT/Windows 2000:
  \<installdir>\log\*.* and \<installdir>\tmp\*.*
• UNIX:
  $OV_SHARE_LOG, $OV_PRIV_LOG, and $OV_TMP

Troubleshooting Installation

See Managing Your Network with NNM for information about starting with a well-configured network for best results.

If during installation NNM complains that your networking appears to be misconfigured, try the following. From a command prompt of the management system type:
     ipconfig /all
It will display your Windows NT/2000 TCP/IP config, including your hostname. Then type:
     nslookup <YOUR_IP_ADDRESS>
where <YOUR_IP_ADDRESS> is the address reported by ipconfig. If the hostnames reported by ipconfig and nslookup don't match, then NNM won't work. If either command fails to give you a hostname, then DNS is likely misconfigured or not available. Verify that the result of this nslookup matches the result of 'ovw -server'.

Troubleshooting Discovery

NNM will automatically start up and begin discovering and displaying your network within five minutes of installation. However, if your discovery is not working (such as an empty internet icon on the top level map) or you would like to validate your installation, see Chapter 5 in Managing Your Network with NNM for information about troubleshooting the Discovery process. The following may help you isolate any problems:

• Check for installation problems by looking in the setup.log file.
• Check that the HP OpenView services are running by looking at the 'Services' applet of the Control Panel. You should see the following services with Status 'Started' and Startup 'Automatic': HP OpenView Process Manager, SNMP EMANATE Adaptor for Windows NT, and SNMP EMANATE Master Agent.
• Validate that all daemons are running by running
       ovstatus -c
  (or run from Start:Programs->HP OpenView->Network Node Manager->NNM Services - Start)
• Validate that the SNMP agent is running: snmpwalk <nodename> system.  If it is having trouble starting (and the services indicate it will not start), try stopping the SNMP EMANATE Master Agent service, then run the following from a console window
       snmpdm -d -apall (on Windows NT/2000, the -d option may actually prevent output, so you may need to omit it)
  and examine the output when you run the snmpwalk command again.
• Validate that the MIB-II subagent is running:
       snmpwalk <nodename> ipAddrTable
  You should get a screen full of data
• Validate that the topology database thinks it has discovered nodes. Run
       ovtopodump -l
  You should see the "NUMBER OF MANAGED NODES:" field greater than 2. To see which nodes have been discovered, run:
       ovtopodump
• Validate that the Collection Station send from ovtopmd is functioning. Run:
       snmpwalk <nodename> .1.3.6.1.4.1.11.2.17.4.1
• Validate that the Collection Station send from netmon is functioning. Run:
       snmpwalk <nodename> .1.3.6.1.4.1.11.2.17.4.4

If NNM fails to discover all the nodes you expect to find in your local network, individually ping first your local node and then the missing nodes to verify connectivity (using the Fault:Ping" menu item). Validate that your node "knows" about these by selecting your management station icon and selecting the Configuration:Network Configuration->ARP Cache menu item. You should then see these new nodes in the ARP cache. Select your management station and select the Fault:Network Connectivity->Poll Node menu item to have the netmon process query your node again. The new nodes should then be added to the map.

Manually Seeding Discovery

If NNM fails to discover any nodes, you can manually seed discovery through the user interface or command line. See Chapter 5 of Managing Your Network with NNM and the netmon reference page in NNM's online help (or the UNIX manpage) for details.

This is done by adding a node at the internet level which supports SNMP.  Even if this node is not really a gateway, NNM will properly discover the device, create the necessary networks, and place it in the appropriate network.  Verify the node supports SNMP by running:
     rnetstat -I <nodename>
To manually add this node through NNM's user interface:

1. Open NNM's user interface.
2. Go to the top level submap and select the internet icon.  Double click on it to get to the internet submap
3. Pick Edit:Add Object  Select 'connectors' and 'gateway'
4. Give the name of the gateway.  Double click on 'ipmap'
5. Enter in the correct submap (important!) and the node name.  Hit [Verify] and [OK]

To manually add this node through a command line (you must know the correct subnet mask) run:

 echo <IPADDR> <NODENAME> | loadhosts -V -v -m <SUBNETMASK>

where <IPADDR> is the IP address of the node to add, <NODENAME> is the name of the node, and <SUBNETMASK> is the subnet mask for the network.  An example is:

 echo 192.18.1.1 myrouter | loadhosts -V -v -m 255.255.255.0

You can also manually seed discovery by using a seedfile.

After seeding discovery, you should see the map start displaying nodes based upon the information received from the node which supports SNMP, or see a list of nodes when running the ovtopodump command.

Troubleshooting Data Warehouse

Make sure the database is executing by running "ovstatus ovdbcheck".

You can verify that data exists in your data warehouse by using the ovdwquery command, such as:

• To test for topology data in your data warehouse:
  echo  select ip_hostname from nnm_nodes; |ovdwquery

• To test for event data in your data warehouse:
  echo  select message from nnm_event_detail; |ovdwquery

• To test for trend (snmpCollect) data in your data warehouse:
  echo  select descript_id from snmp_trend_dataset; |ovdwquery

You can use the ovdbdebug command to test whether your database is functional.

See Reporting and Data Analysis with NNM for more information.

Uninstallation Instructions

This document outlines the process to completely uninstall Network Node Manager from your system. Instructions are provided to remove the optional NNM Data Warehouse databases (if they exist). Manual removal instructions are also included.

Removing Network Node Manager on Windows NT or Windows 2000 systems

• You should use the uninstall icon provided in the Network Node Manager Program folder to remove NNM.

• To be completely sure you have removed everything from your Windows NT/2000 installation, perform the following steps, if appropriate. In most cases these will be cleaned up by the Uninstall. However, if you lost your \Program Files\HP OpenView\NNM directory, or accidentally removed \Program Files\HP OpenView\NNM\OVNNMRT.isu, you may need to perform a manual removal using the following instructions. Also, you may not get a complete uninstall if you've done multiple subsequent installs without intervening uninstalls. This is because InstallShield only removes what was added by the last installation, not all previous installations.

  • Bring up the Services applet from the Control Panel. If they exist and are running, stop the following services:
  1. HP OpenView Process Manager
  2. SNMP EMANATE Adaptor for NT or Windows 2000
  3. SNMP EMANATE Master Agent
  • Bring up Task Manager and kill any of the HP OpenView processes which may be running, such as:
  1. any process beginning with "ov"
  2. any process beginning with "xnm"
  3. ipmap
  4. netmon
  5. pmd
  6. snmpCollect
  7. snmpdm
  8. wpaagt

  You can get the process list via Task Manager available by right clicking in a blank area on the task bar.

  • Clean out any registry entries by deleting certain keys from the registry. The registry can be accessed via Start:Run, then type RegEdit. Delete any of the following keys:
  1. Hive HKEY_CLASSES_ROOT:
  • \HKEY_CLASSES_ROOT\OVPerl
  • \HKEY_CLASSES_ROOT\TypeLib\{3E329641-EEF3-11CF-BC25-00AA00A7EAAE}
  • \HKEY_CLASSES_ROOT\TypeLib\{865A2A40-8D1B-11CF-8614-00AA006D1482}
  • \HKEY_CLASSES_ROOT\TypeLib\{A801FC03-6FA8-11D0-BB85-00AA00A7EAAE}
  • \HKEY_CLASSES_ROOT\TypeLib\{B9FF9851-9CD2-11CF-8622-00AA006D1482}
  • \HKEY_CLASSES_ROOT\TypeLib\{E3B3D260-B9D9-11CF-910D-00AA006D919A}
  2. Hive HKEY_LOCAL_MACHINE:
  • \HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView\Network Node Manager
  • Any of the following keys listed under \HKEY_CURRENT_USER\Software\Hewlett-Packard\OpenView:
  • OV_PATH
  • OV_SHARE_PATH
  • OVTL_LOG
  • OVTL_MIN_SEVERITY
  • OVTL_SUBSYSTEMS
  • OVTL_TRACE
  • OVTL_TRACE_KIND
  • \HKEY_LOCAL_MACHINE\SOFTWARE\SNMP Research\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Network Node Manager
  • Any of the following keys listed under \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths:
  • netmon.exe
  • ovactiond.exe
  • ovcapsd.exe
  • ovstart.exe
  • ovstatus.exe
  • ovstop.exe
  • ovtopmd.exe
  • ovtrapd.exe
  • ovw.exe
  • ovwdb.exe
  • pmd.exe
  • snmpCollect.exe
  • ovuispmd.exe
  • ovrequestd.exe
  • \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Help\NNMOnline.hlp
  • Any under \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services:
  • EMANATE
  • HP OpenView Process Manager
  • wpa
  • \HKEY_LOCAL_MACHINE\SOFTWARE\Classes\OVPerl
  • \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\OpenViewLog
  • \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\OpenViewTrace
  3. Hive HKEY_CURRENT_USER:
  • \HKEY_CURRENT_USER\Software\Hewlett-Packard\OpenView\Network Node Manager
  • Using File Manager, delete the subtree <DRIVE>:\Program Files\HP OpenView\NNM, where <DRIVE> is the drive to which you installed HP OpenView. If you were unable to delete everything, you will need to restart Windows NT/2000 and repeat this step. If using NT 4.0, be sure to use 'shift-delete' to really remove everything and not leave it in the recycle bin.
  • Remove miscellaneous files
  1. del \%SystemRoot%\system32\NMUnInst.dll
  2. del \%SystemRoot%\system32\NMUnInst.log
  • The following files were conditionally installed, and can be removed if you do not use them by another program. Be especially careful of the files in system32, since it is likely another program (such as Visual C++) is using them.
  1. del \%SystemRoot%\system32\mfc42.dll
  2. del \%SystemRoot%\system32\msvcirt.dll
  3. del \%SystemRoot%\system32\msvcrt.dll
  4. del \%SystemRoot%\system32\msvcrt40.dll
  5. del \%SystemRoot%\system\ctl3dv2.dll
  6. del \%SystemRoot%\system\mhsp200.vbx
  7. del \%SystemRoot%\system\nwipxspx.dll
  8. del \%SystemRoot%\system\rdmiip.dll
  9. del \%SystemRoot%\system\rdmiipx.dll
  10. del \%SystemRoot%\system\rdmim.dll
  11. del \%SystemRoot%\system\rdmim.ini
  12. del \%SystemRoot%\system\rdmisub.dll
  13. del \%SystemRoot%\system\spin.vbx
  14. del \%SystemRoot%\system\threed.vbx
  • Modify your \%SystemRoot%\system32\drivers\etc\services file. Remove entries for
  1. ovwdb
  2. ovtopmd
  3. ovuispmd
  4. ovembeddb
  5. pmdmgr
  6. ovspmd_req
  7. ovspmd_mgmt
  8. ovsessionmgr
  9. ovalarmsrv
  10. Restore the entry for snmp to be:
         snmp 161/udp snmp
      by changing the 8161 to 161
  • Restart Windows NT/2000. This step is recommended to clear out any environment variables or system registry entries which are left in memory

• Manual Data Warehouse Removal on Windows NT/2000
  

  ASSUMPTIONS:

  • This process has sections specific to an Oracle database or a SQL Server database used for the external data warehouse.
  • Following this process will remove the database that was created for the Openview data warehouse and subsequently configured by the ovdwconfig.ovpl script.
  • NNM has already been removed.

  Please click on the database type on which NNM's data warehouse was installed:

  Oracle
  SQL Server

  ---

  Oracle

  Note:  Because the database administrator has complete control over the creation of an instance for NNM's data warehouse, this document will use "SID" to represent this instance.  Please replace SID with the appropriate name.

  1)  Connect to the Oracle openview instance as system to determine where the openview database files reside. 

  • You can get a list of the database file by executing the following queries:
                select file_name from dba_data_files;
                select member from v$logfile;
                select name from v$controlfile;

  2)  Shutdown the instance created for NNM data warehouse.

  • From the Control Panel - Services determine if the OracleServiceSID service is started.  If it is, select the service and click on the stop button.   You will be asked to verify that the OracleStartSID service also be stopped.  Select OK.

  3)  Remove the openview database files as identified in step 1.

  4)  Remove the database parameter file, usually:

  \orant\database\initSID.ora

  ---

  This concludes the manual removal of the data warehouse on Oracle.

  ---

  SQL Server

  1)  From Enterprise Manager, delete the objects created for the OpenView data warehouse.

  • Right click on the database created for the NNM data warehouse. Select the Delete option.
  • If no other databases are located on the database devices on which the data warehouse database resided, you may also want to remove the associated database devices.

  2)  It is important that you take a backup of your master and msdb databases at this time.
       Any structural changes require a backup be performed so that recovery is possible.

  ---

  This concludes the manual removal of the data warehouse on SQL Server.