For the Windows NT® 4.0 Operating System
Congratulations on your purchase of HP OpenView Network Node Manager 6.0 (NNM) for the Windows NT® 4.0 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, and we hope this product exceeds your network management expectations. Please see the table of contents in the left frame for the topics that are included in these release notes or click here to bring up the frame version of the Release Notes.
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.
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.
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:
When you purchased your media and manuals, you purchased either an "HP OV NNM 6.0 ENTERPRISE" or "HP OV NNM 6.0 250" product. If you bought the "HP OV NNM 6.0 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:
\OpenView\conf\OVLicense\forms\nnm\C\server_move.txt
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:
For detailed descriptions of each correlation, bring up the ECS Config/Management GUI:
Additional correlations can be developed by purchasing and using the HP OpenView ECS Designer product.
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 following databases versions are supported with NNM 6.0:
To export NNM's topology, event, or SNMP collected data into the data warehouse, either:
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 OpenView\conf\analysis\sqlScripts directory. See tables_topo.solid (topology schema), tables_event.solid (event schema), or tables_trend.solid (SNMP collected data schema).
To help you generate meaningful reports, NNM ships with Microsoft Excel templates. These templates allow you to easily generate reports based upon the current information in NNM's data warehouse. You can modify the reports within Excel as needed. The Excel templates request data over the web, so Excel does not need to be running on the same machine as your management station. The Excel templates and a README file are located in OpenView\conf\analysis\excelTemplates\NNM. See README_excelTemplates.txt for more information.
The NNM's Report Presenter is available as a contributed application (not supported by HP). This tool serves as a framework for browsing and viewing HTML reports of data warehouse information. See OpenView\contrib\NNM\reportPresenter\README.txt (you must run a "Custom" install to get contributed program files) for more information.
New with Network Node Manager 6.0 is a 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:
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 the Dynatext version of 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 OpenView\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.
New with Network Node Manager 6.0, backing up NNM can be integrated into your regularly scheduled network backup scheme (such as when using HP OpenView OmniBack). The backup happens in the background while your team continues to monitor alarms on your network. NNM temporarily pauses all services (background processes) whose activities result in changes to the NNM databases (such as the ovw, ovwdb and ovtopmd databases), thus ensuring consistency among the NNM databases and minimizing the potential for database corruption.
After the synchronized files are copied to the backup directory, the services resume normal activity. Then the files that do not require services to be in a paused state are copied to the backup directory.
During the backup of synchronized information, your team’s maps are frozen in time, but the Alarm Browser’s list and all Data Collection & Threshold information stay current throughout the backup.
See Managing Your Network with NNM and the ovbackup.ovpl,ovrestore.ovpl,ovpause,and ovresume reference pages in NNM's online help (or the UNIX manpages) for more information.
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:
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.
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:
NOTE: Management server (Windows NT) for remote consoles (UNIX) is not supported.
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.
You need to buy a third party NFS product that runs on the Windows NT operating system and install it on each system to be an HP OpenView Remote Console. The following NFS packages are supported:
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.
See the ovwsetupclient(1M) manpage for instructions about configuring HP OpenView Remote Consoles.
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.
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:
Configure an SNMP SET-community name for each HP OpenView Collection Station:
On the central NNM management station:
See the xnmtopoconf reference page in NNM's online help (or the UNIX manpage) for more information.
There are two mechanisms that integrate NNM with Microsoft's Systems Management Server:
- Launch SMS from NNM's pull-down menus:
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 submap, simply select a node that is an SMS client (running the SMS client software) and view the SMS properties.- Access NNM submaps from within SMS (version 1.2 or newer):
- Copy the OVHERM.DLL from your SMS installation CD's \SUPPORT\ISV\HP\SETUP directory to the NNM management station's SMSADMIN\SITE.SRV\X86.BIN directory
- Register NNM with your SMS site server. From the command prompt run your SMS installation CD's \SUPPORT\ISV\HP\SETUP\HPDB.EXE without any arguments to see the proper command line arguments. Then run HPDB.EXE with those arguments.
The next time you start SMS Administrator while NNM is running, simply select a node in SMS's site database, and select the NNM icon in that node's list of properties. Clicking on the NNM icon displays the NNM submap containing that node.
You can improve the performance of your NNM management system in several ways:
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".
A very 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 operating system's swap performance by correctly configuring the initial paging file size, you will get better performance than if Windows NT 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.
The latest version of the HP OpenView Performance and Configuration guide is available
at:
http://ovweb.external.hp.com/nnm/NNM6.0/perfConfigGuide.htm.
NNM includes a library of detailed reference materials for your use. Some are provided in printed form, some are provided online in the DynaText collection, and some are provided in both formats. DynaText allows you to search multiple manuals, and print or view manuals in the NNM online library. The following manuals are provided with NNM.
To access the online manuals shipped with NNM, use the Help menu. When you choose Online Manuals, a Dynatext browser window appears. Choose the manual you want to view, and follow the instructions in the viewer. If you do not see the manual that you want, insert the installation CD-ROM and use the “Custom Installation” feature. Follow the directions in the dialog boxes to indicate that you want to install only the online manuals. Numerous additional HP OpenView online manuals are available at the following web sites:
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.
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:
To be completely sure you have removed everything, in the event your uninstall was unsuccessful, you can follow the manual removal instructions.
You can migrate directly from NNM 4.11, NNM 5.x or NNM 6.0 to NNM 6.01. Hewlett-Packard recommends that you backup your system and have the latest patches for your release before migrating to NNM 6.01.
The oid_to_sym file controls which symbol is used on NNM's maps for each SNMP
OID. Starting with NNM 5.01, the oid_to_sym file became language independent, so
it moved out of the "C" directory:
Old location: \OpenView\conf\C\oid_to_sym
New location: \OpenView\conf\oid_to_sym
See the ovconfadmin.ovpl reference page for more details about how the merge process works.
Network Node Manager 6.01 has been tested with the current version of many third-party OpenView applications. Most of the tested applications work on NNM 6.01 just as they do on NNM 4.11 and/or NNM 5.01. To view a complete list of which applications/versions run on which operating systems, go to http://ovweb2.external.hp.com/solutions/technical. Special instructions are also shown where applicable.
Copyright © 1990-1999 Hewlett-Packard Co., All Rights Reserved
Copyright © 1996 AirMedia, Inc.