StormTracker EMS 2.3 Installation Instructions Document Number EMS-A2-GN10-00 July 2002 Contents Overview... 2 Basic StormTracker EMS Functionality... 2 Oware and StormTracker EMS... 2 Supported Systems... 3 Solaris Installation Server and Client... 3 Installing as Root... 3 Installing as Non-Root... 8 Solaris Client Installation... 11 Uninstalling in Solaris... 13 Non-Root Uninstall... 13 Root Uninstall... 15 Windows 2000 Installation... 17 Windows 2000 Server Installation... 17 Windows 2000 Client Installation... 20 Windows 2000 Reinstallation... 20 Uninstalling in Windows 2000... 20 This document describes the installation procedures for the StormTracker Element Management System, version 2.3. For complete details on how to use StormTracker EMS, please refer to the StormTracker EMS 2.3 User s Guide, Document No. EMS-A2-GB20, which is contained on the StormTracker EMS 2.3 CD or can be downloaded from the Paradyne web site at www.paradyne.com. 1
Overview StormTracker EMS provides the technology needed to deliver and manage network services and resources. Each component of the StormTracker EMS provides a specific area of functionality, and the various components can be combined to provide you with exactly the functions you require. Basic StormTracker EMS Functionality All StormTracker EMS components provide a set of common functions, including: Network device discovery Device management Data Collection Logical and physical topological data views StormTracker EMS is a complete, end-to-end solution that lets you quickly and easily manage all facets of a new-world network. Using StormTracker EMS, you can monitor every aspect of your next-generation network and ensure: Reduction in time to resolve trouble tickets Detection, monitoring, configuration, and alteration of your network Rapid problem analysis, regardless of the origin Reduction in operation costs Oware and StormTracker EMS The following sections describe how to install Oware (the console for the application server and mediation agent software that must operate in the background for StormTracker EMS) and StormTracker EMS on Solaris operating systems. Both software components install together. The following are some preliminary items of importance: Installation inserts the correct file name in the owappserver.properties and owdatabase.properties files. Although, in previous versions, *.properties files contained host name entries that default to localhost, your Oware server should NEVER be named localhost. While Oware can automate preserving your database information, it does NOT preserve *.properties files. The best practice is to back up these files, in addition to your database, before installing Oware. If you have just uninstalled, you must reboot before reinstalling. Ensure that hard and soft file descriptor limits are set to 1024. It is recommended that your System Administrator implement this as installation procedures may vary slightly, based on system and network configuration. 2
Supported Systems Server: Windows 2000 Sun Solaris 2.6 / Solaris 7 Client: Windows 2000 Sun Solaris 2.6 / Solaris 7 Solaris Installation Server and Client You must install a portion of Oware as super-user (root) because the installation must modify or write files where Solaris requires root permissions. Once this portion is done, you can perform the balance of the installation or removal process as the database admin user. File Manager is not recommended for use in the installation process. NOTE: Solaris installation procedures will vary slightly depending on system setup, local office procedures, and patches installed. Solaris Install Script Backwards Compatibility: The current version of install.sh is not compatible with earlier versions. Remove earlier installations using the owclean.sh script before installing the new version. Installing as Root The first time you install Oware, you must install it as root. When you are logged in as root, the installation performs additional checks (for example, verifying the Solaris patch level). It also offers additional installation options, for example installing a server startup script. Oware requires installation as root only the first time you install the software or when you move the database components to a new location. Although you can install as root on other occasions, you must make the initial installation as root. The installation script tells you the action to be taken and lets you accept or bypass the change. If you accept the change, the installation saves a backup copy of the file and announces the saving location. If you bypass the change, you must change it manually before you can run the second phase of the install process; see Installing as Non-Root on page 8. NOTE: Before running the installer, establish the database admin user and group accounts if they do not already exist. You can use any valid user (other than root) and group names. 3
Root installation may modify the following system files: /etc/system Checks and upgrades key values, if needed. /etc/services Adds the database daemon entry. /etc/inetd.conf Adds the database daemon entry. /etc/.oscnnnnnn Writes the database environment information to this file. /etc/rc2.d/s76oware Installed. Below are the command line installation instructions and scripts that you will see during the installation process. It is recommended that the default selections be entered. Remember, File Manager is not recommended. Procedure To perform a root installation: 1. Insert the CD into the computer. (Solaris typically mounts the CD as /cdrom/cdrom0.) 2. From the Console, type the following commands: cd cdrom/cdrom0 ls cd install ls cd solaris ls./install.sh NOTE: If you do not specify an installation directory, the install selects /opt/dorado. The installation root directory is the only command line option for install.sh. The installation obtains all other required information interactively. Usage: install.sh [installation root directory] Where: [installation root directory] is the starting point for this installation. 3. Follow the instructions displayed by the install.sh. If /etc/system is modified, the script asks you if you want to reboot after installation. If the installation modifies /etc/intetd.conf or /etc/services, the scripts ask you if you want to restart the inet daemon at the end of the root installation. CAUTION: To properly install Oware you must have administrator rights to your database as well as being at root. 4
The following is a transcript much like what you will see during a Solaris root installation: ===== Welcome to redcell installer for release 2.3.3, build ===== Copyright (c) 2002 by Dorado Software, Inc. No environment found in /etc/.dsienv 4. Enter a directory. The installation root directory appears to be /opt/dorado Use this directory? NOTE: If you select no, you will be prompted to enter another path. This part of the installer script (install.sh) performs the pre-installation functions requiring root user privileges. Install.sh will explain what changes will be made and give you a chance to bypass the changes before any modifications are made. If you allow the changes, your original files will be backed up first and the name of the backup file will be displayed. A detailed history of actions will be recorded in the install log. The file name for the install log will be announced when it is created 5. Enter a function. Select function i - Install software r - Remove software Selection?[i]: i Enter type of install: Client Install Application Server Database Server Full Install (default) Begin recording system information End recording system information Checking patches for SunOS, release 5.7 Looking for required patch 106980, rev 13 Found installed patch 106980, rev 16 Looking for required patch 107081, rev 22 Found installed patch 107081, rev 33 Looking for required patch 107636, rev 05 Found installed patch 107636, rev 08 Looking for required patch 108376, rev 08 Found installed patch 108376, rev 24 End patch check 5
6. Install application server startup script. Install application server startup script /etc/rc2.d/s76oware? 7. Install mediation agent startup script. Install mediation agent startup script /etc/rc2.d/s77oware? Selection?[y]: Pinging db host 'Paradyne-ems' -- please wait (db host is station name) ems is responding 8. Ensure that users and groups have been provisioned by your system administrator, then enter user name to be used. Selection?[NotSpecified]: emsuser emsuser OK Backing up /export/home/dorado/.env as /export/home/dorado/backup/.env.20020117114812 9. Enter group name to be used. Selection?[NotSpecified]: sysadmin staff OK Backing up /export/home/dorado/.env as /export/home/dorado/backup/.env.20020117114812 No changes needed to /etc/system 10. Modify /etc/inetd.conf. Modify /etc/inetd.conf? Selection?[y]: Backing up /etc/inetd.conf as /export/home/dorado/backup/inetd.conf.20020117114812 Added oscssd entry to /etc/inetd.conf entry = 'oscssd stream tcp nowait root /export/home/dorado/oware3rd/versant/5.2.2/sun4/bin/ss.d in.oscssd' NOTE: If some files necessary for the installation are not found, you will be prompted to install them. 6
Checking database properties file '/etc/.osc050202' /etc/.osc050202 not found Install /etc/.osc050202? Selection?[y]: /etc/.osc050202 installed OK Backing up /export/home/dorado/.env as /export/home/dorado/backup/.env.20020117114812 Backing up /export/home/dorado/.env as /export/home/dorado/backup/.env.20020117114812 11. Modify /etc/services. Modify /etc/services? Selection?[y]: Backing up /etc/services as /export/home/dorado/backup/services.20020117114812 12. Disable bootp. Enable bootp? Selection?[n]: Backing up /export/home/dorado/.env as /export/home/dorado/backup/.env.20020117114812 To finish the system installation, log in as emsuser and run install.sh again. CAUTION: inet daemon restart (kill -1) is needed for new /etc/inetd.conf values to take effect. 13. Restart system. Restart now? Selection?[y]: # exit NOTE: The AppServer must run for at least 15 minutes following initial installation. 7
Installing as Non-Root This phase installs program files, does setup functions and loads or upgrades the database load, as appropriate. Below are the command line install instructions and scripts that you will see during the installation process. It is recommended that the default selections be entered. Procedure To perform a non-root installation: 1. Insert the CD into the computer. (Solaris typically mounts the CD as /cdrom/cdrom0.) 2. From the Console, type the following commands: cd cdrom/cdrom0 ls cd install ls cd solaris ls./install.sh Environment found 3. Confirm directory for installation (If you select no, you will be prompted to enter another path). The installation root directory appears to be /opt/dorado/logs Use this directory? This part of the installer script (install.sh) performs all installation following the root setup functions: install.sh created installation log file install_log.20000908084302 install.sh will explain what changes will be made and give you a chance to bypass the changes before any modifications are made. A detailed history of actions will be recorded in the install log (this name is uniquely specified). 4. Select function. i - Install software r - Remove software or database Selection?[i]: i Install support software? 8
Unpacking files from /cdrom/oware/solaris/oware3rd.tar into /Paradyne This will take a while...... files successfully unpacked 5. Install program files. Selection?[y]: Unpacking files from /cdrom/ems_2109/install/solaris/apps.tar into /export/home/dorado This will take a while...... files successfully unpacked Loading oware environment Running loaddb Please wait. This will take a few minutes NOTE: Installation progress can be monitored by the following command: tail -f /export/home/dorado/logs/install_log. 20020117172236 This is a fresh installation Creating databases Running loaddb Running /export/home/dorado/owareapps/redcell/core/setup/ install This utility is installing CDE support for oware. You have the option of running the application from the Front Panel, the Workspace Menu, or both. 6. Select menu option: A) Add icon to Front Panel B) Add item to Workspace Menu C) Modify both the Front Panel and Workspace Menu D) Do not make any changes to the Desktop Selection? [c]: Front Panel updated. The Desktop has been updated successfully. You will need to login again to see the changes. Checking owenv... The following unresolved entries exist in owenv show_path - /export/home/dorado/oware3rd/lib/snmp.jar is 9
UNKNOWN show_path - /export/home/dorado/oware3rd/lib/snmp2.zip is UNKNOWN show_path - /export/home/dorado/oware3rd/tlink is UNKNOWN show_path - /export/home/dorado/oware3rd/tlink/lib is UNKNOWN show_path - /export/home/dorado/oware3rd/tlink/lib/tlink.jar is UNKNOWN show_path - /userclasspath is UNKNOWN Verify and correct these entries before starting redcell Checking owenv... done install complete 7. Install application server and mediation agent. Install application server and mediation agent? Unpacking files from /cdrom/oware/solaris/oware.tar into /Paradyne This will take a while...... files successfully unpacked Backing up /Paradyne/oware/lib/owappserver.properties as / Paradyne/backup/owappserver.properties.20000908084302 8. Install database server program files. Unpacking files from /cdrom/ems_2109/install/solaris/db.tar into /export/home/dorado/oware3rd This will take a while...... files successfully unpacked Backing up /export/home/dorado/oware/lib/owdatabase.properties as /export/home/dorado/backup/owdatabase.properties. 20020117172236 9. Start the application. Selection?[y]: Starting application server Starting agent mapper When you are finished with the agent mapper, close it. 10
10. Type y to continue with startup. Selection?[y]: Starting mediation agent Check /opt/dorado/logs for startup results 11. To start StormTracker EMS, type startredcell at the command line while in the /export/home/dorado/oware/bin directory. You may also type redcell at the command line while in the /export/home/dorado/owareapps/redcell directory. 12. Press Enter to continue. Reinstalling the Database To reinstall the database without doing a full system installation, follow the steps above, but when running install.sh, choose to remove software. Answer y when asked whether you want to remove the database. Answer n to all other questions about removing program files. You may then invoke install.sh again and answer n to all questions about installing files. The script will then begin to reinstall the database. Solaris Client Installation Procedure To perform a client-only installation on Solaris: 1. Perform a normal installation on the client system. When the installer asks about starting the application, answer n to terminate the installer. NOTE: The user name you provide during installation on client machines should be a valid user login on the server too. The client account does not need to have a password on the server. 2. Edit the oware/lib/owappserver.properties and oware/lib/owdatabase.properties files on the client. 3. If the client user account is not the same name as the database administrator on the server, run ownewclientuser on the server to add the client username to the list of authorized database users. 4. Run ow start ems on the client machine. 11
Using the Solaris inittab to Maintain Oware Processes The UNIX process control initialization routine init spawns processes. Its primary role is to create processes from information stored in the /etc/inittab file. You can add an entry to /etc/inittab to start the Application Server or Mediation Agent at startup and restart it every time it terminates or is killed by a user. CAUTION: Adding the Application Server and/or Mediation Agent to inittab prevents you from ever completely shutting down the processes, since they will always attempt to re-spawn. The /etc/inittab file consists of entries that are position-dependent and have the following format: id:rstate:action:process id: A one or two-character identifier. We suggest using ma for Mediation Agent, and as for Application Server. rstate: Represents the different init levels that this process should run (2 through 4 are suggested values). action: Should be respawn so init restarts the process when it terminates. process: The programs and the arguments it runs. Procedure 1. The init process is a sysadmin process. Therefore, you must log in as root to interact with it. 2. To use init, add the following lines to the /etc/inittab file: sa:234:respawn:/dorado/oware/bin/startappserver ma:234:respawn:/dorado/oware/bin/startmedagent <hostname> These examples assume that the startappserver and startmedagent scripts are installed in the /dorado/oware/bin directory. Replace this with the correct path, if necessary, and replace hostname with the name of the Application Server host. 3. Reread the inittab file by typing the following command: init Q 4. Change init levels from 3 to 2 and back again (this makes it process the line in the new file): init2 init3 5. For more information about inittab, execute the following command from the terminal window: man inittab 12
Uninstalling in Solaris You can also uninstall with install.sh. The uninstall procedure is the reverse of the installation. Removing the software can be performed as a root or non-root user, but it is recommended that you uninstall as non-root first, then uninstall as root. You may remove the files (database, program files, and data) as the database admin user with install.sh. If you are removing to get a clean installation, you do not need to run the root user portion of the script unless you plan to install the software into a different set of directories than the initial installation. You must run install.sh as root to completely remove the installation in system files. Non-Root Uninstall Procedure To perform a non-root uninstallation: 1. Insert the CD into the computer. (Solaris typically mounts the CD as /cdrom/cdrom0.) 2. From the Console, type the following commands: cd cdrom/cdrom0 ls cd install ls cd solaris ls./install.sh Environment found 3. Confirm directory for installation (if you select no, you will be prompted to enter another path). The installation root directory appears to be /opt/dorado Use this directory? This part of the installer script (install.sh) performs all installation following the root setup functions: install.sh created installation log file /Paradyne/logs/ install_log.20000908084302 install.sh will explain what changes will be made and give you a chance to bypass the changes before any modifications are made. A detailed history of actions will be recorded in the install log (this name is uniquely specified). 13
4. Select remove software or database option. i - Install software r - Remove software or database Selection?[i]: r Oware was removed from the menu successfully. owenv removed from /emsuser/.dtprofile successfully. 5. Delete application files. Remove redcell application files 6. Delete database data files. Remove database data files? 7. Delete data base server program files. Remove data base server program files? Removing data base server program files Run install.sh again when you are logging in as root if you wish to completely remove the database installation. 8. Delete application server and mediation agent files. Remove application server and mediation agent files? Removing application server Application server and mediation agent successfully removed 9. Delete support software Run install.sh again when you are logged in as root if you wish to completely remove the installation. 14
Root Uninstall The following is a transcript much like what you will see when removing the software using a Solaris Korn shell. You will start install.sh, but select the remove software option. NOTE: When you uninstall as root, you also uninstall the Oware environment. Procedure To perform a root uninstallation: 1. Insert the CD into the computer. (Solaris typically mounts the CD as /cdrom/cdrom0.) 2. From the Console, type the following commands: cd cdrom/cdrom0 ls cd install ls cd solaris ls./install.sh Environment found 3. Confirm directory for installation (if you select no, you will be prompted to enter another path). The installation root directory appears to be /opt/dorado Use this directory? This part of the installer script (install.sh) performs the pre-installation functions requiring root user privileges install.sh will explain what changes will be made and give you a chance to bypass the changes before any modifications are made. If you allow the changes, your original files will be backed up first and the name of the backup file will be displayed. A detailed history of actions will be recorded in the install log. The file name for the install log will be announced when it is created. install.sh - created installation log file /opt/dorado/logs/install_log.20020117114730 Confirm environment file use (do not use this file if you want to completely uninstall). An environment file exists -- use it? (y,n) 15
Selection?[y]: n 4. Select Remove software option. Select function i - Install software r - Remove software Selection?[i]: r Removing data base data files in /opt/dorado/oware3rd/versant/db. Removing data base server files. Removing /etc/.osc050202 Removing oscssd entry from /etc/inetd.conf Entry successfully removed from /etc/inetd.conf Removing oscssd entry from /etc/services Entry successfully removed from /etc/services Removing app server files Removing rc2.d files You may want to save the installation root, logs, backup file and environment file for historical reasons or because you want to preserve the environment for a reinstallation. If you choose to retain these files, all other files and sub-directories will be removed. If you choose not to retain these files, they will be removed along with the installation root directory /opt/dorado. Select no when prompted to retain installation data. Retain installation root, logs, backup files, and environment? Selection?[y]: n Doing a complete removal of installation root '/opt/dorado' Done removing installation Uninstallation of all components complete. A daemon or machine restart may be required. CAUTION: inet daemon restart (kill-1) is needed for new /etc/inetd.conf values to take effect. 5. Select yes to restart. Restart now? 16
Windows 2000 Installation StormTracker EMS runs on Windows 2000. This is the only version of Windows currently supported. Custom Installation Options You have the option of installing portions of Oware to separate hosts by selecting desired options from the installation program dialog. The following are elements typically installed by themselves, using the Custom Installation option: Application Server Database Server Client Windows 2000 Server Installation The following procedure describes how to install StormTracker EMS on Windows 2000 servers. The server installs the client. Your installation may vary slightly, depending on whether you have previously installed this software on the computer, either as a client or server. Procedure To perform a server installation of Oware on Windows 2000: 1. Log in as an administrator, and insert the installation CD (you must be an administrator to install). 2. Click on Start > Run, then type [X:]\nt\Setup.exe, where [X:] is your CD drive letter. Or, double-click the setup.exe icon from CD root path. 17
3. Choose the installation destination (the default is C:\Dorado), then click on Next. 4. Choose the type of installation you want. In this case, select Server. 18
5. Click on Next after confirming your selection.this screen informs you of changes, and warns you if you are going to overwrite data. 6. You must reboot if you are prompted. You are prompted to reboot only for the initial database installation, or if you uninstalled and are reinstalling. 7. Build the Oware databases, then click on Next. 8. When the database seeding completes, click on Finish. 9. To confirm the completion of your installation, and to execute the software, click on Start. You can start Oware and StormTracker EMS components from the menu items under their respective icons. 19
Windows 2000 Client Installation The following procedure describes how to install on Windows 2000 clients. Your installation may vary slightly, depending on whether you have previously installed this software on the computer, either as a client or server. Procedure 1. Log in as an administrator, and insert the installation CD. 2. Click on Start > Run, then type [X:]\nt\Setup.exe, where [X:] is the CD drive letter. Or, double-click the setup.exe icon from CD root path. 3. Choose the installation destination (the default is C:\Dorado). Click on Next. 4. Choose the type of installation you want. In this case, select Client. 5. Enter a TCP/IP host name for the Appserver and for the DBServer. 6. Confirm the selection, and wait for the progress bar to reach 100%. 7. Click on Finish. You have successfully installed the Oware and StormTracker EMS. Click on Start to access the applications. Windows 2000 Reinstallation At this time, StormTracker EMS does not support the modify or repair function in the reinstall feature. CAUTION: If it is ever necessary to reinstall, ALWAYS uninstall first, then reinstall as other files may be overwritten. Uninstalling in Windows 2000 Procedure To uninstall StormTracker EMS in Windows 2000: 1. Access the Add/Remove Programs dialog in Control Panel. 2. Highlight StormTracker EMS, then click on Remove. 3. Reboot the computer to remove locked files (the uninstall program prompts this). 20
Warranty, Sales, Service, and Training Information Contact your local sales representative, service representative, or distributor directly for any help needed. For additional information concerning warranty, sales, service, repair, installation, documentation, training, distributor locations, or Paradyne worldwide office locations, use one of the following methods: Internet: Visit the Paradyne World Wide Web site at www.paradyne.com. (Be sure to register your warranty at www.paradyne.com/warranty.) Telephone: Call our automated system to receive current information by fax or to speak with a company representative. Within the U.S.A., call 1-800-870-2221 Outside the U.S.A., call 1-727-530-2340 Document Feedback We welcome your comments and suggestions about this document. Please mail them to Technical Publications, Paradyne Corporation, 8545 126th Ave. N., Largo, FL 33773, or send e-mail to userdoc@paradyne.com. Include the number and title of this document in your correspondence. Please include your name and phone number if you are willing to provide additional information. Trademarks StormTracker is a trademark of Paradyne Corporation. All other products and services mentioned herein are the trademarks, service marks, registered trademarks, or registered service marks of their respective owners. Copyright 2002 Paradyne Corporation. Printed in U.S.A. 21
!'" *EMS-A2-GN10-00*