HP Network Node Manager Software II

uc341s b.00

Setup guide
Use of this material to deliver training without prior written permission from HP is prohibited.

HP Network Node Manager Software II

uc341s b.00

Setup guide
Use of this material to deliver training without prior written permission from HP is prohibited.

 Copyright 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. This is an HP copyrighted work that may not be reproduced without the written permission of HP. You may not use these materials to deliver training to any person outside of your organization without the written permission of HP. Java is a U.S. trademark of Sun Microsystems, Inc. Microsoft, Windows, MS Windows, Windows NT, and Windows 2000 are U.S. registered trademarks of Microsoft Corporation. Oracle is a registered U.S. trademark of Oracle Corporation, Redwood City, California. UNIX is a registered trademark of The Open Group. Export Compliance Agreement Export Requirements. You may not export or re-export products subject to this agreement in violation of any applicable laws or regulations. Without limiting the generality of the foregoing, products subject to this agreement may not be exported, re-exported, otherwise transferred to or within (or to a national or resident of) countries under U.S. economic embargo and/or sanction including the following countries: Cuba, Iran, North Korea, Sudan and Syria. This list is subject to change. In addition, products subject to this agreement may not be exported, re-exported, or otherwise transferred to persons or entities listed on the U.S. Department of Commerce Denied Persons List; U.S. Department of Commerce Entity List (15 CFR 744, Supplement 4); U.S. Treasury Department Designated/Blocked Nationals exclusion list; or U.S. State Department Debarred Parties List; or to parties directly or indirectly involved in the development or production of nuclear, chemical, or biological weapons, missiles, rocket systems, or unmanned air vehicles as specified in the U.S. Export Administration Regulations (15 CFR 744); or to parties directly or indirectly involved in the financing, commission or support of terrorist activities. By accepting this agreement you confirm that you are not located in (or a national or resident of) any country under U.S. embargo or sanction; not identified on any U.S. Department of Commerce Denied Persons List, Entity List, US State Department Debarred Parties List or Treasury Department Designated Nationals exclusion list; not directly or indirectly involved in the development or production of nuclear, chemical, biological weapons, missiles, rocket systems, or unmanned air vehicles as specified in the U.S. Export Administration Regulations (15 CFR 744), and not directly or indirectly involved in the financing, commission or support of terrorist activities. Printed in USA HP Network Node Manager Software II Setup guide May 2008

NNM 7.53 Installation Instructions

For NNM 1, NNM 2, and Operator Training
(UC340S, UC341S, B3305S) Mimic setup instructions at end

Hardware Requirements
Each student requires two systems or students will have to cooperate for the distributed exercises. Windows 32 bit Processor RAM Free Disk Space DVD Drive
Intel Pentium 4 equivalent or higher

HP-UX PA-RISC
HP 9000 workstation, Series 700 or 800

HP-UX Itanium
HP Itanium (ia64)

1GB or more 8GB on one NTFS drive X (not required for class) 1GB

1GB or more 8GB X (not required for class) 1GB

1GB or more 8GB X (not required for class) 1GB

Virtual Memory/Swap Space

Environment Requirements

MIMIC server running current simulations (see end of this document) for uc341 NNM 7.51 server installed and running the NNM 7.51 demo which students can browse to Variety of switches and routers to discover. SNMP community set to public or instructor informed of alternate community string(s) In the USVL, access to the OV Sandbox DNS Name resolution for all devices, including connecting devices Windows DNS Name Resolution where the IP hostname as configured on the DNS server and the host name configured in Windows must match. Use lower case for the letters in the Windows nodename configuration! HP recommends that the DNS and NetBios computer names match. NNM uses the DNS name when starting OV applications. The Windows tools expect a NetBios

machine name when initializing client/server connections. If the DNS and NetBios names do not match and you want to launch Windows tools while NNM is running, change one of them before installing Network Node Manager. If textual names on the discovered networks are desired, supply these names in the %SystemRoot%\system32\drivers\etc\networks file. Put lowercase nodename entry in hosts file.

Access to the internet and browsers configured correctly for it

Software Requirements:
Windows 32 bit OS Version The following Windows versions are supported: (Tested 2003 SP1 Enterprise)

HP-UX PA-RISC HP-UX 11.23 (tested) or 11.31

HP-UX Itanium HP-UX 11.23 (tested) or 11.31

Microsoft Windows 2003 operating system with Service Pack 1 or 2

Standard Edition Enterprise Edition Web Edition (Service Pack 1 only) Microsoft Windows Server 2003 R2 Standard Edition Enterprise Edition Microsoft Windows XP with Service Pack 2

Microsoft Windows 2000 with Service Pack 4

Professional Server Advanced Server Note: Terminal Services and Remote Desktop are supported in all the supported environments.

Web Browser Internet Explorer 6.0 (SP1) (tested) Internet Explorer 7.0 Netscape Navigator 7.1 Mozilla 1.6 Java Plug-In (1.4.2 tested) 1.4.2 1.5

Mozilla 1.4.00.01 on 11.23 (tested 1.7.12); Mozilla 1.7.13 on 11.31 1 1.23: 1.4.2.05 1.5 1 1.31: 1.4.2.10 1.5

Mozilla 1.4.00.01 on 11.23 (tested 1.7.12); Mozilla 1.7.13 on 11.31 1 1.23: 1.4.2.05 1.5 1 1.31: 1.4.2.10 1.5 One of the following window managers must be installed: Common Desktop Environment (CDE) X Windows and OSF/Motif HP-UX 1 1.31 requires the OVSNMP Emanate Agent

Supporting Software

Acroread Microsoft Internet Information Server (IIS), version 4.0 or greater Microsoft TCP/IP services must be installed and running. Microsoft SNMP services must be installed on the workstation. They do not have to be running.

One of the following window managers must be installed: Common Desktop Environment (CDE) X Windows and OSF/Motif HP-UX 1 1.31 requires the OVSNMP Emanate Agent

UNIX Installation Instructions

No patches are required for HP-UX 1 1.23 or 1 1.31 The NNM management station must be running an SNMP agent. SNMP configured with a community name of public for class.

Procedures
1. 2. 3. 4. o Install and configure web browser. Enable Java and JavaScript. Accept all cookies. Download and install the Java Plug-In and Run Time Environment. Connect to http://www.hp.com/go/java and download the software. Follow the instructions carefully. Set the kernel parameters. Set nkthread first. Kernel Parameters for NNM Extended Topology

If you enable NNM Extended Topology (NNM Advanced Edition), the following kernel parameters are required. NOTE: These kernel parameters are 32-bit parameters. The maxusers and ncallout kernel parameters are obsoleted on HP-UX 11iv2 and 11iv3. The nfile kernel parameter is private and deprecated in HP-UX 11iv3. max_thread_proc = 1024 nfile = 8192 maxdsiz = 1073741824 (1 GB) maxfiles = 2048 maxfiles_lim = 2048 maxusers = 256 ncallout = 6000 nkthread = 6000 nproc = 2068 shmmni = 500 shmseg = 250 semmns = 300 semmnu = 250 semume = 250 If a previous version of NNM (before 7.5) is installed, remove it completely. Install NNM 7.53 from the CDs or installation depot available at http://managementsoftware.hp.com/products/nnm/download.html. a. b. Log in as root to the system on which you wish to install NNM (hereafter referred to as the NNM management station). Insert the Network Node Manager CD-ROM 1 into the CD-ROM drive. Note that all platform-specific versions of NNM software are shipped on separate CD-ROMs. Determine the device filename of your CD-ROM drive. Be sure to use the block device filename, and not the character (raw) device filename. Mount the CD-ROM. The name of the mount directory is not important to the installation process. For example, on an HP-UX system, issue the command: /etc/mount /dev/dsk/c0t2d0 /cdrom f. Change your current directory to the directory where you mounted the CDROM: cd /cdrom g. Run the NNM installation command, ./install
4

5. 6.

c. d. e.

h.

An installation program appears on the screen. It displays messages about the various NNM components being installed. The program also prompts you to answer specific questions about the type of NNM installation you want. Install all manuals and manpages. Automatically start discovery. Insert the second CD and again run ./install.

i. j. k. 7. 8.

Modify the .profile for root to use universal pathnames and to set the PATH variable to include the OpenView executables. Verify NNM. a. b. c. Set up environment variables by typing /opt/OV/bin/ov.envvars.sh. Start all the background processes by typing /opt/OV/bin/ovstart -c. The ovstatus -c command provides status information about the various OpenView background processes started by ovspmd. Verify that the HP OpenView Launcher is working. From the NNM menu bar, select Tools:HP OpenView Launcher. Verify your Java Plug-In is working by selecting Tools:Neighbor View to see the graph that requires the Java Plug-In. Each login .dtprofile needs to contain

d. Start the user interface by typing $OV_BIN/ovw e. f. 9.

If you see Netscape errors in the terminal window, do the following: a.

export MOZILLA_HOME=/opt/netscape export XAPPLRESDIR=/usr/lib/X11/app-defaults export CLASSPATH=/opt/netscape/java/classes/cpPack1.jar (Netscape 4.61) or export CLASSPATH=/opt/netscape/java/classes/java40.jar (older versions)

10. Install the lab files for the course into the $OV_CONTRIB/OVTraining directory as appropriate. 11. Copy the NNM7labs.tar.gz file into the /tmp directory. 12. For B3305 (NNM for Operators) ONLY: Run the command setupExtTopo.ovpl and enable all options.

Other UNIX Setup

All systems should be able to print to the classroom printer. All systems should have a second user account called openview with password openview.

Windows Installation Instructions

Procedures
1. 2. 3. If a previous version of NNM (before 7.5) is installed, completely uninstall it. Set Paging File size. Install and configure the Microsoft TCP Services. a. b. c. d. Install the services from the Windows Control Panel. In the Microsoft TCP/IP Properties dialog box, verify the following: At the IP Address tab, verify that the subnet mask of your management station is correct. 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. Also at the DNS tab, verify that a TCP/IP domain has been specified in the DNS Service Search Order field. At the WINS Address tab, verify that the Enable DNS for Windows Resolution option has a check mark next to it. 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: At the IP Address tab, note the IP address value shown. At the DNS tab, note the Host Name and Domain field values shown there. 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. 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 that was pinged matches the configured IP address shown at the IP Address tab. Do the ping steps on another computer to validate that your DNS is working correctly.

e. f. g.

h. i. j.

k.

l. 4. 5.

Install Microsoft SNMP services from the Windows control panel. Install Mozilla and enable Java and JavaScript. Accept all cookies.

6. 7. 8. 9.

Install Internet Explorer and enable Java and JavaScript. Accept all cookies. See if a Web Server is installed and if not, install Option Pack 4. Install Service Pak. Install NNM 7.53 a. b. c. d. e. f. a. b. c. d. e. f. g. h. Log in as administrator to the system on which you wish to install HP NNM (hereafter referred to as the Management Station). Insert the first HP OpenView Network Node Manager CD-ROM into the CDROM drive. Run the setup command on the installation media. Use the default destination drive. Do a Custom installation and select all available options for installation. Insert second CD when requested. Set up the NNM environment variables by typing \Program Files\HP OpenView\bin\ov.envvars.bat. The ovstart-c command starts the OpenView subprocess monitor background process, ovspmd. The ovstatus -c command provides status information about the various OpenView background processes started by ovspmd. Verify that ovw user interface starts. Verify the version number in the splash screen or Help:About. Verify that the HP OpenView Launcher is working. From the NNM menu bar, select Tools:HP OpenView Launcher. Install and verify your Java Plug-In is working by selecting a device symbol and selecting Tools:Views:Neighbor View. Verify acroread by selecting Help:Online Manuals and opening one of the manuals. Verify lab files are installed in \Program Files\HP OpenView\NNM\contrib\OVTraining. Install update lab files from HPEd.

10. Verify NNM (and install Java Plug-In)

11. For B3305 (NNM for Operators) ONLY: Run the command setupExtTopo.ovpl and enable all options.

Other Windows Setup

All systems should have a second account called openview with password openview. Add the following to the desktop icons: MS DOS window, Services applet from Control Panel, Notepad, File Explorer. File explorer should not hide file extensions. Set the preferred browser to MS Internet Explorer.

Instructor System
The Instructor system should be an HP-UX system. A Windows Server may also be used, but not a Windows Workstation. 1. Provide the instructor with the following: a. b. A paper map of the physical layout of the room showing node names, IP addresses, and connector devices. The IP address of a system elsewhere on the site that can be used as a seed for added discovery. Ideally this would be a gateway with standard SNMP community names. The ability to send and receive email.

c.

MIMIC Server Setup

MIMIC Software
You must acquire and install the MIMIC software package for Windows from Gambit. For the latest system requirements, please check the Gambit Communications website at: http://www.gambitcomm.com/site/support/ . The MIMIC package is licensed to the specific system on which you install it, so consider this a dedicated box. You must be able to simulate up to 50 devices. You may be able to use a temporary MIMIC license. Send credit card information (Master or Visa card; Amex card will need go through paypal) to Gambit. The fax number for credit card orders is 1-603-889-5005. The rental cost is USD200, and is for 50 agents sim only licenses, for 10 days. The contact at Gambit is Sally Zhao, and it's a good idea to mention her name when submitting an order. Sally's contact info is below: Sally Zhao International Business Gambit Communications, Inc. Phone: 1-973-538-5089 (Time Zone EST) Mobile Phone: 1-917-805-3488 E-mail: sally@gambitcomm.com or sallyzhao@att.net

These simulations* require MIMIC 8.31 plus a patch, or later. There are two ways to install the patch. In a non-firewall environment, open mimicview and select Wizard:Update. If you get a message that the socket is unavailable, use the patch distributed from EFT and uncompress the single file, mgmt.pm into <mimic_install_dir>\perl\Mimic. *(Actually, to run the uc341 class just as with its a.00 release, you do not need to upgrade Mimic. The upgrade and patch are required for perl scripts. The simulations themselves continue to work just fine.)

Perl
Install Microsofts Active Perl from the Windows Resource Kit into C:\Perl.

Simulations
These simulations are intended to overwrite and provide a superset of the uc341 simulations and the uc344 simulations. One package to cover both courses. 1. 2. Stop any simulations and exit mimicview. If you have a set of simulations from uc341, rename the directory just for safety. Rename the directory C:\nnmet20_mimicsims to C:\z.751.nnmet20_mimicsims. Unzip the self-extracting HPESmimicSetup.exe. It will place files in C:\HPESmimicSetup. Go to the directory C:\HPESmimicSetup and unzip all self-extracting .exe files there. They will automatically place (overwrite) files in C:\nnmet20_mimicsims. One set of files goes to C:\opt (for historical reasons).

3. 4.

Configure System Environment Variables

1. 2. 3. 4. 5. 6. 7. Right click the My Computer icon on the desktop and select Properties. Select the Advanced tab within the System Properties Window. Select the Environment Variables button. Within the System Variables Section, select the New button. Within the Variable Name box, type (exactly): MIMIC_PRIV_DIR Within the Variable Value box, type (exactly): C:\nnmet20_mimicsims Repeat, creating d. e. Variable Name: MIMICHOME Variable Value: type here the name of the home directory containing the Mimic bin directory, such as C:\Apps\Mimic.620. Be sure to use the directory name into which your MIMIC version installed.

Mimic executables will be executed out of %MIMICHOME%/bin. It is important this (MIMICHOME) variable be set for correct execution of the labs. (Do not add /bin to the variable as you set it in system properties that is how the scripts refer to their directory.) 8. Select the OK button three times (and you save the new variables and exit the System Properties window).

Modify SNMP Services Port Configuration

1. Locate the Services configuration file typically located in the following folder (some systems may have it in a different location:
C:\WINNT\system32\drivers\etc\SERVICES

2.

Using an editor (for example, wordpad.exe), edit this file and change the snmp service port to 164 as indicated below:
snmp 164/udp snmp # SNMP Research wpaagt.exe service

3. 4. 5. 6. 7. 8. 9.

Save and exit this file editor. The snmp services must be stopped and re-started. Start the Control Panel: click the Microsoft Start button, then select Settings, then Control Panel. Select Administrative Tools. Select Services. Scroll down until you see SNMP Service. Right click the SNMP Service and select Restart.

10. Do not install NNM on the Mimic system. 11. When completed, the Services panel should show Started and Automatic.

Verify
12. Start mimicview. 13. Select File:Open, and open the diamond_vlan_lab.cfg file. 14. Select Run:Start to start the simulation. Wait until all devices/agents turn green. 15. In the Windows file explorer, browse to C:\nnmet20_mimicsims\labs\poller. 16. Double-click simNodeDown.bat. When that has worked, double-click simNodeUp.bat. 17. Clear the simulation by selecting Run:Stop (do not save any agent changes) and File:New. 18. You are now ready to begin class.

10

Updates from the NNM 7.51 simulations

When you run uc341s.b.00 with these simulations you will notice the following differences:

Lab A, step 15, 2 nodes that previously appeared minor now appear normal. When APA is the poller, the systems are normal rather than minor. (But it takes a long time).

The APA lab had the instructor stop an agent to simulate a down node. That is not very realistic since APA queries the neighbor devices, and they still say their connecting interfaces are operationally up. There are 2 new scripts available to you (which will be documented for use with uc341s.a.01) to better simulate a downed node. Have the students watch 5505-school_1, rather than 6509-school_1. Run C:\nnmet20_mimicsims\labs\poller\simNodeDown.bat. When you are ready to repair the failure run simNodeUp.bat.

11

12