CanogaView Smart Element Manager Version 1.0 Notes (HP-UX Platform) Contents: 1.0 - INSTALLING CANOGAVIEW SMART ELEMENT MANAGER 1.1 - System Requirements 1.2 - Root Permission 1.3 - Java Plug-In 1.3.0.01 1.4 - HP OpenView NNM Services Must be Running 1.5 - Trap Port 163 when Installed with HP OpenView NNM 1.6 - HP OpenView NNM 6.1 Patches 1.7 - HP-UX 11.0 Patches 1.8 - Installation Temporary Disk Space 1.9 - Installation Root Filesystem Disk Space 1.10 - Debugging Installer Problems 2.0 - POST INSTALLATION STEPS 2.1 - HP OpenView URL Setup for SNMP Agents 2.2 - Netscape Navigator Environment Variable MOZILLA_HOME 2.3 - Delete Directories if Desired 3.0 - STARTING CanogaView Smart Element Manager 3.1 - Netscape Navigator 3.2 - CanogaView Smart Element Manager Start Page 3.3 - Account Manager 3.4 - Security Manager 3.5 - TFTP Server 4.0 - STARTING CanogaView Smart Element Manager USING HP OPENVIEW NNM 4.1 - Setup Standalone Access if Desired 4.2 - Launch CanogaView Smart Element Manager from HP OV Symbol 5.0 - RUNNING CANOGAVIEW SMART ELEMENT MANAGER 5.1 - Default User Accounts 5.2 - Security Lock Out 5.3 - Starting and Stopping CanogaView Smart Element Manager Services 6.0 - UNINSTALLING CANOGAVIEW SMART ELEMENT MANAGER 6.1 - Uninstall Procedure ------------------------------------------------------------------------------------ 1.0 - INSTALLING CANOGAVIEW SMART ELEMENT MANAGER 1.1 - CanogaView Smart Element Manager Server System Requirements The CanogaView Smart Element Manager Server supports the following platforms: - HP workstation running HP-UX - Sun workstation running Solaris - PC workstation running NT 4.0, Windows 2000 or XP. The CanogaView Smart Element Manager Server is basically responsible for the following major features: - provides Web Server facilities for the CanogaView Smart Element Manager Web Clients - storage and management of the CanogaView Smart Element Manager applications and databases - SNMP support to Canoga Perkins SNMP Agents - TFTP Download facilities for device upgrade support As all CanogaView Smart Element Manager applets execute within a Web Browser (either Netscape or Internet Explorer), the browser must be capable of supporting the Java Plug-In or JVM (Java Virtual Machine). Any of the Web Client platforms listed below can be used in an heterogenous environment against any of the CanogaView Smart Element Manager Web Server platforms to support local, remote and multiple users. CanogaView Smart Element Manager Web Client supports either Netscape or Internet Explorer running on: - HP-UX - Windows NT, 98, 2000 or XP - Sun Solaris - Linux Before proceeding with the installation instructions located in the manual, please make sure that your system meets the minimum hardware and software requirements listed below. Minimum Hardware Requirements: - HP 9000 workstation, Series 700 or 800 - 128MB RAM (256MB or higher is strongly recommended) - Approximately 150MB Disk Space for runtime environment and 300MB of tmp space during the installation process. - CD-ROM Drive Minimum Software Requirements: - HP-UX version 11.0 - Web Browser supporting Java Plug-In: Netscape Navigator 4.77 - Java Plug-In 1.3.0.01 This version of the Java Plug-in requires Netscape Communicator Version 4.77 from HP. Previous versions of Netscape Communicator will not work. You must use HP's version of Netscape Communicator 4.77 with the Java Plug-in Version 1.3.0.01. Previous versions of Netscape Communicator and Netscape's own Netscape Communicator Version 4.77 will not work with the Java Plug-in Version 1.3.0.01. This version of Netscape may be downloaded from: http://www.hp.com/go/netscape - HP Openview Network Node Manager 6.1 (optional) 1.2 - Root Permission Since the CanogaView Smart Element Manager installer adds files to protected directories, you must have root permission when installing CanogaView Smart Element Manager. 1.3 - Java Plug-In 1.3.0.01 Required CanogaView Smart Element Manager requires the Java Plug-In 1.3.0.01, which is available from H.P. along with the Java 2 Runtime Environment Standard Edition. Unlike other versions of the Java Plug-In, this version does not come bundled with the Java Runtime Environment, but instead requires that the Java Runtime Environment be already installed. As of this writing, the Java Plug-In and the Java Runtime Environment may be downloaded from: http://www.hp.com/products1/unix/java/java2/sdkrte1_3/downloads/ license_rte_1-3-0-01.html In addition, This version of the Java Plug-in requires Netscape Communicator Version 4.77 from HP. Previous versions of Netscape Communicator will not work. You must use HP's version of Netscape Communicator 4.77 with the Java Plug-in Version 1.3.0.01. Previous versions of Netscape Communicator and Netscape's own Netscape Communicator Version 4.77 will not work with the Java Plug-in Version 1.3.0.01. This version of Netscape may be downloaded from: http://www.hp.com/go/netscape The first time each Web Client executes a CanogaView Smart Element Manager application, they will be automatically prompted to install the Java Plug-In for their platform. Optionally, you may add the Java Plug-In download files to your existing CanogaView Smart Element Manager installation, thereby making it possible for CanogaView Smart Element Manager web clients to download the required Plug-In file from the CanogaView Smart Element Manager Web Server. To add these files to CanogaView Smart Element Manager, you must run the separate Java Plug-Ins for CanogaView Smart Element Manager installer located on the installation CD. If these files are not installed, the user will be automatically linked to the www.canoga.com website where these files can be downloaded. The instructions for installing the Java Plug-In are displayed during the download process. The release notes for the Java Runtime Environment 1.3.0.01 indicate a potential problem with Java when running on the local display (i.e. the display attached to the workstation). On a workstation, when displaying to the local screen, a high speed connection called "Shared Memory Transport" is used for communication between applications and the X server. This type of connection can cause poor performance and crashes with Java. Shared Memory Transport can be disabled by changing the value of the DISPLAY environment variable. The DISPLAY variable is used to tell an application how to connect to an X server and which screen it should use. Typically, DISPLAY would default to ":0" or ":0.0" to indicate the local display. By instead setting DISPLAY to a value of the form "ip_address:0.0" (where ip_address is the IP address of the workstation), Shared Memory Transport may be disabled. If you find that this change improves Java performance, you may want to set the DISPLAY value in a file that is sourced automatically at boot time or when the user logs in (e.g. /.dtprofile for CDE). The instructions for installing the Java Plug-In are displayed during the download process. A text copy of the web page appears below: Download Instructions This version of the Java Plug-in requires Netscape Communicator Version 4.77 from HP. Previous versions of Netscape Communicator will not work. Download and install Netscape Communicator Version 4.77 from www.hp.com/go/netscape prior to performing the remaining installation steps. Note that you must use HP's version of Netscape Communicator 4.77 with the Java Plug-in Version 1.3.0.01. Previous versions of Netscape Communicator and Netscape's own Netscape Communicator Version 4.77 will not work with the Java Plug-in Version 1.3.0.01. The download consists of two depot files; one contains the Java Runtime Environment (JRE) and the other contains the actual Java Plug-in software. Both are required for the Java Plug-in to operate correctly. The Java Plug-in software provides the ability for Netscape Communicator Version 4.77 to run CanogaView Smart Element Manager's Java Applets within the Java Runtime Environment Version 1.3.0.01. Click here to download the Java Runtime Environment Version 1.3.0.01 from CanogaView Smart Element Manager Web Server. If you have a connection to the Internet, you can click here to download the Java Runtime Environment from Canoga Perkins Corporate Web site or here to download from H.P's Web site. Save the depot file to a temporary directory on a file system with at least 60 MB of free disk space when prompted. The Java Runtime Environment depot file is named rte_13001os11.depot. Click here to download the Java Plug-in Version 1.3.0.01 from the CanogaView Smart Element Manager Web Server. If you have a connection to the Internet, you can click here to download the Java Plug-in from Canoga Perkins Corporate Web site or here to download from HP's Web site. Save the depot file to a temporary directory on a file system with at least 1 MB of free space when prompted. The Java Plug-in depot file is named jpi13001.depot. Installation Instructions If you have a previous release of the Java Plug-in installed including Version 1.3.0BETA2, you must uninstall it using swremove. To do so: - Open a console window and start swremove by entering the command swremove& - In the list on the SD Remove - Software Selection window select the entry that reads: Name Revision Information B9098AA 1.3.0.Beta2 Java Plugin for HP-UX (700/800) - From the Actions menu, choose Mark For Remove - From the Actions menu, choose Remove(analysis...). - In the Remove Analysis window, click OK after the analysis is complete. Prior to installing the Java Plug-in software, you should insure that you have installed the full set of required patches needed for support of Java Runtime Environment Version 1.3.0.01. CanogaView Smart Element Manager has been test with the following patches: HP-UX 11.0 Support Plus Patch Bundles from December 2000 CD (HP part no. 5011-7888): - General Release Patch Bundle - Quality Pack Patch Bundle - Critical Patch Bundle HP-UX 11.0 OS patch PHCO_22314 After downloading the Java Runtime Environment and the Java Plug-in software from above, do the following to install the Java Runtime Environment: - Open a console window and start swinstall be entering the command swinstall& - If the Specify Source Path window does not automatically open, open it by choosing Change Source from the Actions menu. - In the Specify Source Path window, change the Source Depot Type option to Local Directory. - In the Source Depot Path field enter the full path to the downloaded Java Runtime Environment depot file. For example, if you save the Java Runtime Environment depot file into /tmp, enter /tmp/rte_13001os11.depot - Click OK. In the list on the SD Install - Software Selection window select the entry that reads: Name Revision Information B9789AA 1.3.0.01 Java 2 RT 1.3 for HP-UX (700/800) - From the Actions menu, choose Mark For Install - From the Actions menu, choose Install(analysis...). - In the Install Analysis window, click OK after the analysis is complete. Now the process has to be repeated to install the Java Plug-in software: Open the Specify Source Path window by choosing Change Source from the Actions menu. In the Specify Source Path window, change the Source Depot Type option to Local Directory. In the Source Depot Path field enter the full path to the downloaded Java Plugin-in depot file. For example, if you save the Java Plug-in depot file into /tmp, enter /tmp/jpi13001.depot Click OK. In the list on the SD Install - Software Selection window select the entry that reads: Name Revision Information B9098AA 1.3.0.01 Java 2 Plugin for HP-UX (700/800) From the Actions menu, choose Mark For Install From the Actions menu, choose Install(analysis...). In the Install Analysis window, click OK after the analysis is complete. Once the Java Runtime Environment and the Java Plug-in software installation is complete, do the following to allow Netscape Communicator Version 4.77 to find and load the Java Plug-in: - Netscape Communicator Version 4.77 locates its plug-in's through the NPX_PLUGIN_PATH environment variable. This environment variable must be updated to include the location of the Java Plug-in javaplugin.sl file. This environment variable should also include the path to Netscape Communicator's default plug-in directory. For example, if Netscape Communicator is installed into /opt/netscape and the Java Runtime Environment has been installed into /opt/java1.3 which are the default locations, then set the NPX_PLUGIN_PATH environment variable within the Bourne and Korn shells as follows: NPX_PLUGIN_PATH=/opt/java1.3/jre/plugin/PA_RISC:/opt/netscape/plugins export NPX_PLUGIN_PATH To ensure that this is set for future use, update .dtprofile or some other file that is used by your shell or desktop to initialize the environment. - Ensure that the CLASSPATH environment variable is set to some value. A bug has been found that causes Netscape Communicator to crash when the Java Plug-in is used and the CLASSPATH environment variable has not been set to anything. If the CLASSPATH environment variable already has some value, then this step can be skipped. If not, then simply set the CLASSPATH environment variable to be empty within the Bourne and Korn shells as follows: CLASSPATH= export CLASSPATH - Starting with Netscape Communicator 4.0, it is strongly recommended that environment variable MOZILLA_HOME be exported and set to point to theNetscape installation directory. This can be accomplished with the Bourne and Korn shells, for example, with the commands: export MOZILLA_HOME MOZILLA_HOME=/path/to/Netscape/install/directory To ensure that this is set for future use, update .dtprofile or some other file that is used by your shell or desktop to initialize the environment. - Start Netscape Communicator or restart Netscape Communicator if it is already up. Shutdown and start Netscape a second time. This is necessary because of a intermittent bug with Netscape Communicator in which Mime types are not loaded properly by Netscape. - Verify that Netscape Communicator has properly load the Java Plug-in. To do this, use the Help:About Plug-ins menu item within Netscape. The window that this brings up should show that the Java Plug-in 1.3.0.01 is present. 1.4 - HP OpenView NNM Services Must be Running If you install CanogaView Smart Element Manager on a computer with HP OpenView Network Node Manager (NNM) and you select the option to integrate CanogaView Smart Element Manager with NNM, the NNM services must be running during the installation. In addition, if the NNM user interface is running, the Event Configuration application must not be displayed. You will be reminded of this during the installation. Also note that the NNM user interface must be restarted in order to see the new symbol icons for Canoga Perkin's SNMP Agents (DMM, 9135, ...) that are already on the map. 1.5 - Trap Port 163 The default installation options installs the CanogaView Smart Element Manager Trap Service on port 163 to ensure that there is no conflict with any other network management software. At this time, when integrating CanogaView Smart Element Manager with NNM, the CanogaView Smart Element Manager Trap Service must be configured to listen for traps on port 163. Failure to do so will result either in Trap Service failing to start or no SNMP Agent traps being processed by CanogaView Smart Element Manager. Therefore, when integrating with NNM, specify port 163 during the installation process; otherwise port 162 could be used. If necessary, the CanogaView Smart Element Manager Trap Service trap port can be changed after the installation. Edit file "service.conf" in the CanogaView Smart Element Manager installation directory using a text editor. Look for the text "-trapport" in the entry for the Trap Service. Change the number following "-trapport" to the desired port number. After saving the changes, you must stop CanogaView Smart Element Manager services and restart them for the change to take effect. 1.6 - HP OpenView NNM 6.1 Patches This release of CanogaView Smart Element Manager has been tested with NNM 6.1, with the following patches installed: PHSS_23221 PHSS_23212 PHSS_23210 PHSS_23158 PHSS_22955 PHSS_22953 PHSS_22747 PHSS_22660 PHSS_22578 PHSS_22424 As of this writing, NNM patches may be downloaded from: "http://ovweb.external.hp.com/cpe/patches/nnm/6.1/s700_800_11.X.html". 1.7 - HP-UX 11.0 Patches This release of CanogaView Smart Element Manager has been tested on HP-UX 11.00, with the following patches installed: HP-UX 11.0 Support Plus Patch Bundles from December 2000 CD (HP part no. 5011-7888): - General Release Patch Bundle - Quality Pack Patch Bundle - Critical Patch Bundle HP-UX 11.0 OS patch PHCO_22314 1.8 - Installation Temporary Disk Space CanogaView Smart Element Manager installers require a significant amount of temporary disk space when they are running. If you experience problems installing which appear to be due to /tmp running out of space, try exporting and setting environment variable IATEMPDIR. Set this value to a directory on a filesystem with sufficient free space to override the default temporary directory /tmp and attempt to reinstall CanogaView Smart Element Manager. Note that the characters IA denote the Install Anywhere software product. 1.9 - Installation Root Filesystem Disk Space CanogaView Smart Element Manager installers create a directory named IA_Installers in the root directory (/) when run. This directory holds expanded installer files that are used during the course of the installation. If you experience problems installing which appear to be due to a lack of space in the root filesystem, work around the problem using a symbolic link. First delete the /IA_Installers directory, if present. Create a directory in a filesystem with sufficient disk space, then create a symbolic link in the root directory named "IA_Installers" to point to the new directory (e.g. "ln -s /some/new/dir /IA_Installers") and then attempt to reinstall CanogaView Smart Element Manager. 1.10 - Debugging Installer Problems If the CanogaView Smart Element Manager installer will not run to completion, it may be possible to determine the cause of the problem by examining installer output messages. To do this, the installer must be started from a terminal window instead of from from the install.htm web page. Insert the CanogaView Smart Element Manager installation CD into the CD-ROM drive and mount it according to the directions in the CanogaView Smart Element Manager Installation Manual. Change to the /cdrom directory (i.e. execute command "cd /cdrom"). Next, find all files named "install.bin" that exist in the /cdrom directory heirarchy by executing command: "find . -name "install.bin" -print". The output of this command will be the paths to all install.bin files below the current directory. In this list of file paths, find the install.bin path that matches the type of installation you are trying perform; directories in the path names indicate the product, install type (full or upgrade), and platform. For example, the install.bin path for a full CanogaView Smart Element Manager installation on HP-UX looks like this: ./nms/Full/Hpux/InstData/Unix/Solaris/install.bin Note that the directory name before the "InstData" directory indicates the target platform (i.e. "Hpux"), not the lowest level directory that install.bin exists in (i.e. "Solaris"). Now execute install.bin with the following command line: LAX_DEBUG=true where "" is the path to the desired install.bin file exactly as it was displayed in the "find" command output. When the installer stops due to a problem, the last messages displayed in the console window may indicate the cause of the problem. For example, a message may appear that indicates the computer's display adapter is not capable of displaying the miniumum required number of colors. If the cause of the problem cannot be determined, copy and save these messages for use by Canoga Perkins technical support. 2.0 - POST INSTALLATION STEPS These steps should be followed after installing CanogaView Smart Element Manager and prior to starting or launching the CanogaView Smart Element Manager applications. 2.1 - HP OpenView URL Setup for SNMP Agents When integrating with NNM, this version of CanogaView Smart Element Manager does not configure NNM to set the Management URL attribute for the DMM, 9135/40 and 9135G objects. The Management URL must be specified to be able to access a SNMP Agent's View from the NNM web interface. As a workaround, this URL may be configured manually as follows: 1. Select a DMM, 9135/40 or 9135G symbol on a NNM submap. 2. Select "Object Properties" on the Edit menu. 3. Double-click on "General Attributes". 4. Set attribute "isHTTPManaged" to "True". 5. Set attribute "ManagementURL" to one of the following depending on the SNMP Agent type: Note 1: These are case sensitive. Note 2: Replace "nms_server_host" with the hostname or IP address of the server on which you installed the CanogaView Smart Element Manager software. Note 3: Replace "agent_ip_addr" with the appropriate SNMP Agent's IP address. Note 4: the "\" character before the "=" character in the above URL. It has been discovered that you must escape (with a backslash) certain special characters when entering them in a Management URL. The "=" and "&" characters are two that must be escaped; there may be others. If you have problems saving or accessing a manually entered URL, check for characters that may need to be escaped. DMM: "http://nms_server_host:8080/nms/jsp/ DomainView.jsp?IP_CONTEXT=agent_ip_addr" 9135: "http://nms_server_host:8080/nms/jsp/ Dev91xxView.jsp?IP_CONTEXT=agent_ip_addr" 9135G: "http://nms_server_host:8080/nms/jsp/ Dev91xxgView.jsp?IP_CONTEXT=agent_ip_addr" 9140: "http://nms_server_host:8080/nms/jsp/ Dev91xxView.jsp?IP_CONTEXT=agent_ip_addr" 2.2 - Netscape Navigator Environment Variable MOZILLA_HOME Starting with Netscape Navigator 4.0, it is strongly recommended that environment variable MOZILLA_HOME be exported and set to point to the Netscape installation directory. This can be accomplished with the Bourne and Korn shells, for example, with the commands: export MOZILLA_HOME MOZILLA_HOME=/path/to/Netscape/install/directory It is recommended that these commands be added to a file that is sourced automatically when the machine is booted or the user logs in (e.g. /.dtprofile for Common Desktop Environment (CDE)). 2.3 - Post Installation - Delete Directories if Desired The IA_Installers and its contents are not needed after the installation completes; they may be safely deleted if desired. 3.0 - STARTING CANOGAVIEW SMART ELEMENT MANAGER 3.1 - Netscape Navigator Start Netscape Navigator and open the following URLs to access CanogaView Smart Element Manager pages. Save the URLs as Netscape bookmarks to allow easy access in the future. NOTE: Replace "nms_server_host" in the following URLs with the hostname or IP address of the computer on which you installed the CanogaView Smart Element Manager software. 3.2 - CanogaView Smart Element Manager Start Page http://nms_server_host:8080/nms/html/nms.html Select "Start" on the initial CanogaView Smart Element Manager web page, and enter either "guest" or "admin" for both the Username and Password. 3.3 - Account Manager http://nms_server_host:8080/nms/jsp/UsersConfig.jsp 3.4 - Security Manager http://nms_server_host:8080/nms/jsp/AppsConfig.jsp 3.5 - TFTP Server Change to the directory where you told the installer to install links, then execute: ./TFTP_Server 4.0 - STARTING CANOGAVIEW SMART ELEMENT MANAGER USING HP OPENVIEW NNM 4.1 - Setup Standalone Access if Desired Follow the procedures in section 3.0 to launch the standalone interface to CanogaView Smart Element Manager or to access any of the CanogaView Smart Element Manager utilities. 4.2 - Launch CanogaView Smart Element Manager from HP OV Symbol You may launch CanogaView Smart Element Manager from HP OV using any of the 3 following methods. Launch a CanogaView Smart Element Manager Domain, 9135/40 or 9135G View by selecting one of these symbols in the NNM native interface, then selecting Tools->Web Browser->Management Page. Login as documented above. -OR- Launch CanogaView Smart Element Manager via the NNM web interface. Open URL: "http://nms_server_host:8880/OvCgi/ovlaunch.exe" NOTE: Replace "nms_server_host" with the hostname or IP address of the computer on which you installed the CanogaView Smart Element Manager software. On the HP OpenView Launcher window, open the "IT Resources and Applications" item on the Object Views tab. Double-click on "CanogaView Smart Element Manager". -OR- Launch a CanogaView Smart Element Manager Domain View via the NNM web interface. From the HP OpenView Launcher window, run the NNM Network Presenter (open "Networks" on the Object Views tab and double-click on "IP Network", or open "NNM" on the Tools tab and double-click on "Network Presenter"). Drill down the map display or use the tree control until a DMM, 9135/40 or 9135G symbol is visible. Select the symbol, then select Tools-> Web Browser->Management Page. Note: There must be a non-web based version of NNM running for each map that is to be available via the NNM web interface. For example, if you have a single instance of NNM running with map "default" open, only this map will be accessible via the web interface. 5.0 - RUNNING CANOGAVIEW SMART ELEMENT MANAGER 5.1 - Default User Accounts Two user accounts are installed with the system: "guest" and "admin" with passwords "guest" and "admin" respectively. The "guest" user is assigned "observer" access and the "admin" user is assigned "supervisor" access. 5.2 - Security Lock Out For security reasons, this version of CanogaView Smart Element Manager will administatively "lock out" any user account after the third consecutive unsuccessful login attempt. The locked out account may be reenabled via the Account Manager applet. 5.3 - Starting and Stopping CanogaView Smart Element Manager Services CanogaView Smart Element Manager services start automatically after the installation completes and also when the computer boots. If for any reason the services need to be started manually, you may do so with the command: "nohup /sbin/init.d/csem start" Services may be manually stopped with: "/sbin/init.d/csem stop" 6.0 - UNINSTALLING CANOGAVIEW SMART ELEMENT MANAGER 6.1 - Uninstall Procedure 1. Close your web browser. IMPORTANT: If installed, Java Plug-Ins for CanogaView Smart Element Manager must be uninstalled before CanogaView Smart Element Manager itself is uninstalled. To uninstall Java Plug-Ins for CanogaView Smart Element Manager, change to the "JavaPlugIns/UninstallerData" subdirectory of your CanogaView Smart Element Manager installation directory. Execute command: "./Uninstall_JavaPlugIns" 2. Change to the "UninstallerData" subdirectory of your CanogaView Smart Element Manager installation directory. Execute command: "./Uninstall_nms" Note that the uninstaller will not remove files that the installer did not install on your hard drive, nor will it remove files that were modified since the installation. To get rid of these files after running the uninstaller, simply delete your CanogaView Smart Element Manager installation directory.