Network Mediation Version 5.1 Setup Guide

Transcription

1 Network Mediation Version 5.1 Setup Guide Fourth Edition February 2010

2 Copyright and Trademark Information Disclaimer 2010 MetaSolv Software, Inc. All rights reserved. MetaSolv is a trademark registered in the United States of America by MetaSolv Software, Inc. All other trademarks contained herein are property of their respective owners. Any rights not expressly granted herein are reserved. Information contained herein is subject to change without notice. All references to future incorporation of new or enhanced product functionality, or to future release dates, are estimates only, and MetaSolv may change them at any time, without notice. Information in this document is subject to change without notice and does not represent a commitment on the part of MetaSolv Software, Inc. All references to new or enhanced product functionality, or to future release dates, are estimates only, and MetaSolv may change them at any time, without notice. The software and/or databases described in this document are furnished under a written license agreement or nondisclosure agreement. No part of this document, the software and/or databases may be used, reproduced or transmitted in any form or by any means, electronic or mechanical, including copying, photocopying, recording, or information storage or retrieval systems, for any purpose without the written permission of MetaSolv Software, Inc., except as specifically allowed in the written license or nondisclosure agreement. It is against the law to copy the software on any medium except as specifically allowed in the license or nondisclosure agreement. MetaSolv Software, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this manual. Use of any of this Software's functionality in a manner inconsistent with your license grant, whether or not protected by the Product ID, is a breach of the license agreement between your company and MetaSolv. Printed in U.S.A. MetaSolv Software, Inc Tennyson Parkway Plano, TX U.S.A

3 Contents Copyright and Trademark Information...ii Disclaimer...ii ii. About this Guide... vii Network Mediation...vii Audience...vii Acronyms... viii Text conventions... viii Documentation suite... x Global Customer Care... x 1. Pre-installation... 1 Review hardware and software requirements... 2 Guidelines for installing Solaris... 5 Verifying the Solaris installation Installation... 9 Installing the Network Mediation software... 9 Choosing a Network Mediation installation set Installing on a Solaris, AIX, or HP-UX IA64 server Installing the admin client on a Windows workstation Installing Network Mediation on a shared cluster file system Hardware and operating system requirements Installation and configuration Confirming the LDAP server daemon Managing the ProcessControl script ProcessControl monitoring capabilities ProcessControl operation UDCEnvironment nodemgr adminsvr...20 gui slapd Setting system monitoring options Disk status monitor Memory monitor CPU usage monitor Managing ports Changing the LDAP port number Managing mediation host security Managing the Network Mediation Administration Server firewall Administration Server port configuration Administration client port configuration Verifying the Network Mediation installation Configuring Node Manager memory limits Setup Guide iii

4 Configuring the nodemgr.var file Starting component daemons Running different Network Mediation versions Starting Network Mediation Starting on a UNIX workstation Starting on a Windows workstation Uninstalling Network Mediation Upgrading Chapter task list Preparing to upgrade Upgrade requirements Export and import capability Import log file...34 Upgrading to Network Mediation Exporting a configuration Importing a customized configuration Importing a configuration Verifying the Network Mediation configuration In case of trouble during an import Switching to a new LDAP installation Upgrading Network Mediation node chains Upgrading the Wireless GGSN/SGSN node chain Editing metasolv_mediation.conf Configuring new features Backing Up and Restoring Backup and restore options Standard configuration Complete system Backing up a standard system configuration Backing up a full installation Restoring Network Mediation Restoring a standard system configuration Restoring a full installation Preserving data when no backup exists NAR file backup and restore operations Preparing to restore NARs Restoring NARs Database Storage and Reporting Chapter task list Database Storage and Reporting architecture Oracle database Creating an Oracle user and dba group Installing Oracle Verifying the Oracle installation Loading the Network Mediation schema iv MetaSolv Software, Inc.

5 Configuring Oracle Configuring UNIX executables Configuring and using the Repository Manager Adding entries to the configuration table Installing the Oracle Client Modifying tnsnames.ora Installing the Oracle JDBC driver Configuring Oracle for automatic restart Verifying the Oracle automatic restart Crystal Reports Index... 1 Setup Guide v

6 vi MetaSolv Software, Inc.

7 About this Guide This document describes how to install and upgrade MetaSolv Network Mediation. Network Mediation MetaSolv Network Mediation is a carrier-class mediation application designed for multiservice, IP, VoIP and 3G wireless networks. Network Mediation delivers pre-integrated mediation solutions that provide all network-to-oss data collection, aggregation, and correlation required for billing, SLA management and performance management. In addition, Network Mediation: Enables rapid implementation with decreased cost and risk through pre-integrated solutions Delivers a convergent mediation solution for multi-vendor, multi-service networks Supports the differentiation of service offerings to attract and retain customers Drives information consistency across applications, ensuring that customer invoices match performance and SLA reports Offers carrier-grade scalability and reliability to prevent revenue losses caused by missing data Offers a Cartridge Development Kit (CDK) that enables the development of nodes to support new Network Elements (NEs), billings systems and other Operational Support Systems (OSS). Audience This document is intended for network operators and system engineers using a UNIX-based management station. Prior knowledge of Network Mediation software is not required. This guide assumes that you: Have a working knowledge of the UNIX operating system. Understand your network configuration and the equipment from which Network Mediation collects data. Have experience with windowing systems or graphical user interfaces (GUIs). Setup Guide vii

8 Acronyms The following acronyms and abbreviations are used in this document: AP CC CDK DC EP GUI IP LDAP NAR NPL OS XML Aggregation Processor Collection Cartridge Cartridge Development Kit Distribution Cartridge Enhancement Processor Graphical User Interface Internet Protocol Lightweight Directory Access Protocol Network Accounting Record Node Programming Language Operating System Extensible Markup Language Text conventions This document uses the following text conventions: angle brackets (< >) Indicate that you choose the text to enter based on the description inside the brackets. Do not type the brackets when entering the command. Example: If the command syntax is ping <IP_address>, you type ping viii MetaSolv Software, Inc.

9 bold text braces ({ }) brackets ([ ]) ellipsis points (... ) italic text screen text separator ( > ) Indicates command names, options, screen features, field names and user input. Example: Enter show ip {alerts routes}. Example: Use the dinfo command. Indicate required elements in syntax descriptions where there is more than one option. Choose only one of the options. Do not type the braces when entering the command. Example: If the command syntax is show ip {alerts routes}, type either show ip alerts or show ip routes, but not both. Indicate optional elements in syntax descriptions. Do not type the brackets when entering the command. Example: If the command syntax is show ip interfaces [-alerts], type either show ip interfaces or show ip interfaces -alerts. Indicate to repeat the last element of the command as needed. Example: If the command syntax is ethernet/2/1 [<parameter> <value>]..., type ethernet/2/1 and as many parameter-value pairs as needed. Indicates book titles and emphasis. Examples: Setup Guide; this task must be done. Indicates system output, for example, prompts and system messages. Example: Format = one IP address per line Shows menu paths. Example: Protocols > IP identifies the IP option on the Protocols menu. Setup Guide ix

10 vertical line ( ) Separates choices for command keywords and arguments. Enter only one of the choices. Do not type the vertical line when entering the command. Example: If the command syntax is show ip {alerts routes}, type either show ip alerts or show ip routes, but not both. warning note Documentation suite The Network Mediation base package documentation suite includes: Release Notes Setup Guide Output Specification Online Help integrated into the software The Network Mediation Planning Guide is also available but is distributed in a controlled manner. It is provided on a request basis only to MetaSolv Professional Services, sales engineers, customer support, partner systems integrators and sales channels. Users of this document require previous network engineering experience and knowledge of Network Mediation. Contact your MetaSolv sales representative to obtain the guide. The technical documents delivered with the Network Mediation Cartridge Development Kit (CDK) and CDK bundle include: CDK Developer s Guide CDK Node Programming Language (NPL) Reference Guide Global Customer Care MetaSolv Global Customer Care plans are designed to provide the best technical support to customers. Details of the plans are provided in the Global Customer Care Support Procedures. To reach the MetaSolv Help Desk, use one of the following methods: Internet: Log on and select Customer Support in the top menu banner. x MetaSolv Software, Inc.

11 Phone: Main Help Desk: Toll Free North America: Toll Free International: The Help Desk is open 9:00 A.M. to 5:00 P.M. EST, Monday to Friday excluding statutory holidays observed in Ontario, Canada. Setup Guide xi

12 xii MetaSolv Software, Inc.

13 1 Pre-installation This chapter outlines the pre-installation tasks you must perform before installing Network Mediation to ensure the system is properly configured. The topics in this chapter include: Review hardware and software requirements on page 2 Guidelines for installing Solaris on page 5 Verifying the Solaris installation on page 7 Setup Guide 1

14 Chapter 1: Pre-installation Review hardware and software requirements Table 1 lists the minimum hardware and software requirements for deployment of Network Mediation. For configuration information on demos and trials and more information about system requirements and engineering guidelines, see the Network Mediation Planning Guide. Table 1: Hardware and software requirements Hardware/Software Network Mediation application server Minimum Requirement For Solaris 8, 9, 10, or 10 (64-Bit) environment Sun server with two 400 MHz UltraSPARC II processors and 2 MB cache 1 GB RAM or 2 GB RAM for Wireless graphics accelerator card monitor tape drive for backup (optional) Note: For optimal Solaris performance, Oracle recommends the current Sunfire platform with four or more processors For AIX 5L environment IBM server with two 400 MHz processors and 2 MB cache 1 GB RAM or 2 GB RAM for Wireless graphics accelerator card monitor tape drive for backup (optional) For HP-UX IA64 11i Version 2.0 (B.11.23) environment HP-UX server with two 400 MHz processors and 2 MB cache 1 GB RAM or 2 GB RAM for Wireless graphics accelerator card monitor tape drive for backup (optional) 2 MetaSolv Software, Inc.

15 Table 1: Hardware and software requirements Hardware/Software Network Mediation admin server Minimum Requirement For Solaris 8, 9, 10, or 10 (64-Bit) environment Sun server with two 400 MHz UltraSPARC II processors and 2 MB cache 256 MB RAM 5 GB disk space For AIX 5L environment IBM server with two 400 MHz processors and 2 MB cache 256 MB RAM 5 GB disk space For HP-UX IA64 11i Version 2.0 (B.11.23) environment HP-UX server with two 400 MHz processors and 2 MB cache 256 MB RAM 5 GB disk space Setup Guide 3

16 Chapter 1: Pre-installation Table 1: Hardware and software requirements Hardware/Software Network Mediation admin client Minimum Requirement For Solaris 8, 9, 10, or 10 (64-Bit) environment Sun server with two 400 MHz UltraSPARC II processors and 2 MB cache 128 MB RAM 5 GB disk space For AIX 5L environment IBM workstation 128 MB RAM 5 GB disk space For HP-UX IA64 11i Version 2.0 (B.11.23) environment HP-UX server with two 400 MHz processors and 2 MB cache 128 MB RAM 5 GB disk space For Microsoft Windows NT 4.0, Windows 2000 or Windows XP Professional environment Pentium II, 400 MHz 128 MB RAM 5 GB disk space 4 MetaSolv Software, Inc.

17 Table 1: Hardware and software requirements Hardware/Software OpenLDAP server For Solaris 8, 9, 10, or 10 (64-Bit) environment Minimum Requirement Sun server with two 400 MHz UltraSPARC II processors and 2 MB cache 256 MB RAM 5 GB disk space For AIX 5L environment IBM server with two 400 MHz processors and 2 MB cache 256 MB RAM 5 GB disk space For HP-UX IA64 11i Version 2.0 (B.11.23) environment HP-UX server with two 400 MHz processors and 2 MB cache 256 MB RAM 5 GB disk space The Network Mediation application server, admin server, admin client, and the OpenLDAP server can reside on the same device. Guidelines for installing Solaris Before you install Solaris 8, 9, 10, or 10 (64-Bit), ensure you have root access. Then install Solaris using the Sun Solaris documentation. For more information, go to: During the Solaris installation, use the following guidelines: 1. In the Select Software window, select Entire Distribution plus OEM support and click Continue. Setup Guide 5

18 Chapter 1: Pre-installation You cannot install Network Mediation software on the basic core OS install SUNWCreq. As a result, the Entire Distribution plus OEM support, SUNWCXall is the only supported Solaris OS package for a Network Mediation installation. 2. Partition the OS disk according to Table 2. This table assumes the OS disk is 18.2 GB. Table 2: Customized partition table for Network Mediation Slice Partition Minimum size (MB) Recommended size (MB) Comment 0 / OS 1 /var OS 2 Overlap <leave as is> <leave as is> <leave as is> 3 /usr OS 4 /tmp OS 5 /opt 2048 Rest of disk ($) OS + third party software + other 6 swap Equal to 2 or 3 x the memory (RAM) on the standard hardware (1024 MB) 7 6 MetaSolv Software, Inc.

19 Verifying the Solaris installation After you install the Solaris operating system, you must verify: LC variables Software cluster Partition table layout To verify LC variables are commented out 1. Type cd /etc/default and press Enter to navigate to the /etc/default directory. 2. Edit the init file using a text editor such as VI. Delete or comment out any lines that begin with LC_ in the init file. To comment out a given line, add a # character at the beginning of the line. 3. Save and close the init file. 4. Type reboot and press Enter. To verify the software cluster is installed correctly, perform one of the following actions Start the admintool, and select browse and then software in the admintool menu. The installed software package displays in the first line. Open the /var/sadm/system/admin/cluster file. The installed software package is the first line of the file. To verify the partition table layout, use the following commands: cd / df -k The output of the df -k command resembles the partition table layout outlined in Table 2 on page 6. Setup Guide 7

20 Chapter 1: Pre-installation 8 MetaSolv Software, Inc.

21 2 Installation This chapter describes how to install Network Mediation and perform initial configuration tasks. The topics in this chapter include: Installing the Network Mediation software on page 9 Installing Network Mediation on a shared cluster file system on page 11 Confirming the LDAP server daemon on page 17 Managing the ProcessControl script on page 17 Setting system monitoring options on page 21 Managing ports on page 24 Changing the LDAP port number on page 24 Managing mediation host security on page 25 Verifying the Network Mediation installation on page 26 Configuring Node Manager memory limits on page 27 Starting component daemons on page 27 Starting Network Mediation on page 28 Uninstalling Network Mediation on page 30 Installing the Network Mediation software The Network Mediation software is distributed on a website so you can download and install it locally. Network Mediation requires 200 MB of available disk space in the /tmp directory during the installation process. The Network Mediation installation program installs one or more software components and creates an uninstall program and an autostart program for components in the /etc/rc2.d directory on Solaris, AIX, or HP-UX IA64 workstations. For more information, see Managing the ProcessControl script on page 17. Setup Guide 9

22 Chapter 2: Installation Choosing a Network Mediation installation set The Network Mediation installation program provides seven installation sets. You can install all the sets on Solaris, AIX, or HP-UX IA64 and you can also install the admin client on Windows. You must install LDAP to manage administrator and user accounts and login information. Note: For the first Network Mediation installation on a server, ensure you select the complete installation set, which includes LDAP. For any subsequent installations on the same server, you can choose the other installation options that do not include LDAP. The installation sets are: complete contains all components including LDAP standard contains all components excluding LDAP custom any combination of components node host admin server admin client Installing on a Solaris, AIX, or HP-UX IA64 server You can install all Network Mediation components on a Solaris 8, 9, 10, or 10 (64-Bit) server, AIX server, or HP-UX IA64 server. To install Network Mediation components on a Solaris, AIX, or HP-UX IA64 1. Open a command window. 2. To log on as root, type su and press Enter. 3. At the password prompt, type your root password. 4. To start the installation, type sh./install.bin and press Enter. InstallAnywhere extracts the files. The InstallAnywhere Wizard starts and the Introduction dialog box opens. 5. Click Next. The Choose Install Folder dialog box opens. 6. Specify a location for the Network Mediation files and click Next. You can install the Network Mediation files in any directory on a local disk, but MetaSolv recommends accepting the default directory, /opt/metasolvnetworkmediation511. The installation directory appears as <NM_HOME> in this document. The Choose Install Set dialog box opens. 7. Click the appropriate install option. 10 MetaSolv Software, Inc.

23 Installing Network Mediation on a shared cluster file system 8. Click Next. The installation process is complete. Installing the admin client on a Windows workstation The admin client is the only Network Mediation component that you can install on a Windows workstation. Windows NT, 2000 and XP are all supported. To install the admin client on a Windows workstation 1. Run the install.exe file. A window opens, informing you that InstallAnywhere is preparing to install the software. The InstallAnywhere wizard starts, and the Introduction dialog box opens. 2. Click Next. The Choose Install Folder dialog box opens. 3. Specify a location for the Network Mediation files. You can install the Network Mediation files in any directory on a local disk. It is recommended that you accept the default directory, C:\MetaSolvNetworkMediation511. The installation directory appears as <NM_HOME> in this document. 4. Click Next. The Choose Install Set dialog box opens. 5. Select Admin Client and click Next. The installation program installs the software. 6. Click Done. The installation process is complete. Installing Network Mediation on a shared cluster file system A shared cluster file system is the organization of multiple servers into a group to form a single logical server for the purpose of achieving high availability at the hardware and software level. With a cluster there is no single point of failure be, whether it be hardware, software, or network related. Note: This is an optional installation configuration. Hardware and operating system requirements Two homogenous, network systems with similar configurations in terms of resources such as CPU, memory, and so on (Sun Enterprise servers) Setup Guide 11

24 Chapter 2: Installation The high availability package and the associated hardware Devices that are accessible to both nodes A logical volume manager (LVM) to maintain unique device path names across the cluster nodes Volumes or disk suite objects on the multi host disks Third-party vendor mirroring for media failure protection Logical host name or floating IP address that can be bound to any of the primary and secondary nodes The drawing below shows an sample shared cluster file system configuration. Installation and configuration The following is high-level Sun Cluster installation procedure: 1. Install Solaris 10 following the recommended disk partitioning found in the Sun Cluster Software Installation Guide for Solaris OS under the section "System Disk Partition". a. Install the Solaris 10 OS as per the requirement, in our testing we have installed the Solaris 10 OS in a single Slice for 14 GB and Swap is usually twice the RAM capacity. 12 MetaSolv Software, Inc.

25 Installing Network Mediation on a shared cluster file system b. Create the following slices specific to Cluster and SVM: Create a slice named / globaldevices for 512Mb and one raw slice of 50Mb for SVM Note: Take care of SCSI initiator ID as we are using shared external disks in our setup. c. Install recommended patches and ensure that the following patches are installed ( , , , , , ). Patching level should be same on all nodes For detailed information refer Sun Cluster Software Installation Guide for Solaris OS from 2. Install the Sun Cluster software on each node using the Sun Cluster Software Installation Guide for Solaris OS procedure under the section name "How to Install Sun Cluster Framework and Data-Service Software Packages (Java ES installer)". As part of this setup the IP Multipath group is auto created. Use the installer script available in Sun cluster software for the installation of Cluster Software in each node For detailed information check 3. Configure the Sun Volume Manager (with Solaris 10 the Volume Manager is already installed) following the procedure outlined in the Sun Cluster Software Installation Guide for Solaris OS starting under the section name "How to Set the Number of Metadevice or Volume Names and Disk Sets". a. Create Disk Sets using metaset. b. Create State Database Replicas using metadb c. Concatenate and mirror the disks using metainit and metaattach. d. Build the new file system using newfs. e. Mount the mirrored slice using global option and add the entry in the vfstab. 4. 4Use Network Mediation install guide to install Network Mediation on the external disks under /mnt directory 5. Run the configue_cluster script under /mnt/<nm_home>/bin directory in the nodes other than primary node as follows:. / configue_cluster < Mediation install directory > {eg:. / configue_cluster /mnt/networkmediation511} 6. Configure the Sun Cluster Failover Data Service using the /usr/cluster/bin/scsetup command following the below steps: a. Select option 2 resource group and press enter b. Select option 1 create a resource group and press enter Setup Guide 13

26 Chapter 2: Installation c. It will ask "Is it okay to continue(yes/no) [yes]" - default is yes so just press enter d. Select option 1 Failover Group and press enter e. Give the name of the resource group as "nmfrg" f. It will ask for addition description type no and press enter g. It will ask for preferred node (yes /no) accept the default 'yes' and press enter h. Select the preferred node 1) servchenm1 2) servchenm2 select the option 1 and press enter i. It will ask for "Do you want to specify such a directory now (yes/no) [no]?" accept default and press enter j. Is it okay to proceed with the update (yes/no) [yes]? Accept default and press enter k. Command should complete successfully. You should get the following line "Commands completed successfully". l. Press enter to continue. m. Do you want to add any network resources now (yes/no) [yes]? Accept default and press enter n. Select the type of network resource you want to add: 1) LogicalHostname 2) SharedAddress o. Choose option 1) LogicalHostname and press enter p. How many LogicalHostname resources would you like to create [1]? Accept default and press enter q. What logical hostname do you want to add? Type servchenm3 and press enter r. Is it okay to proceed with the update (yes/no) [yes]? Accept default and press enter s. Command should complete successfully t. Press Enter to continue: u. Do you want to add any additional network resources (yes/no) [no]? accept default and press enter v. Do you want to add any data service resources now (yes/no) [yes]? accept default and press enter w. Select the type of resource you want to add: 14 MetaSolv Software, Inc.

27 Installing Network Mediation on a shared cluster file system 6) SUNW.gds:5 Generic Data Service for Sun Cluster Type option 6 and press enter x. What is the name of the resource you want to add? Type "nmds" and press enter y. This data service uses the "Port_list" property. The default "Port_list" for this data service is as follows: <NULL> Please check the man page for this resource type for more information on how the list should be set for this resource. Do you want to override the default (yes/no) [no]? Type yes and press enter z. Port number : Type and press enter aa. Is this a TCP port (yes/no) [yes]? accept default and press enter ab. Port number : Type and press enter ac. Is this a TCP port (yes/no) [yes]? accept default and press enter ad. Port number : Type 389 and press enter ae. Is this a TCP port (yes/no) [yes]? accept default and press enter af. Port number (Ctrl-D to finish): Ctrl-D to finish ag. This is the Port_list which you entered: 55105/tcp 55109/tcp 389/tcp Is it correct (yes/no) [yes]? Accept default and press enter Select a property you would like to set: Property Name Default Setting Desired Setting 1) Monitor_retry_count 4 2) Monitor_retry_interval 2 3) Probe_timeout 30 4) Child_mon_level -1 5) Start_command <Needs Setting> 6) Stop_command <Needs Setting> Setup Guide 15

28 Chapter 2: Installation Property Name Default Setting Desired Setting 7) Network_aware True 8) Stop_signal 15 9) Failover_enabled True n) Next > q) Done ah. Option: choose option 5 and press enter ai. Property value: /mnt/<nm_home>/bin/startnm aj. Option: choose option 6 and press enter ak. Property value: /mnt/<nm_home>/bin/stopnm al. Option: q and press enter am. Are you done setting properties (yes/no) [yes]? Accept default and press enter an. Is it okay to proceed with the update (yes/no) [yes]? Accept default and press enter ao. Commands completed successfully. ap. Press Enter to continue: aq. Do you want to add any additional data service resources (yes/no) [no]? accept default and press enter ar. Do you want to bring this resource group online now (yes/no) [yes]? Accept default and press enter as. Commands completed successfully. at. Press Enter to continue: au. Choose the option q) Done 7. Modify the LDAP URL, edit the file /mnt/<nm_home>/web/htdocs/ AdminServerImpl.properties, and look for the property called "com.nt.udc.admin.server.adminserverimpl.ldapurl". Replace the "ldap://localhost:389" with the virtual IP address Ex: "ldap:// :389". 8. Verify proper installation and configuration. To do so execute scconf pv and ensure that all primary resources are online. 16 MetaSolv Software, Inc.

29 Confirming the LDAP server daemon 9. Verify the status of the nodes, Device Groups and Resource Groups to execute scstat command and ensure that all are configured properly. 10) We should include the Virtual IPaddress in /var/opt/metasolvmediation/ metasolv_mediation.conf file e.g. : NodeMgr:/mnt/NM511:55109: :Y AdmnSvr:/mnt/NM511:55105: :Y LDAPSvr:/mnt/NM511:389: :Y Confirming the LDAP server daemon To confirm the LDAP server daemon has started, enter the following command on your Solaris, AIX or HP-UX IA64 installation: ps -ef grep slapd For information about creating Network Mediation administrator and user accounts, see the Network Mediation Online Help which you can access through the Administration Client. To further configure LDAP server functionality or redundant server operation, refer to the UNIX reference pages in the man subdirectories below the following LDAP installation directory: /<NM_HOME>/ldap/man The UNIX reference pages describe how to modify the slapd.conf file for additional OpenLDAP server functionality. Managing the ProcessControl script You use the ProcessControl script to start or stop Network Mediation components. ProcessControl also ensures that node status is preserved during a shutdown and restart of the node manager. During system installation, the directory /var/opt/metasolvmediation is created. In this directory, the configuration file metasolv_mediation.conf defines components that are running, the installation they run from, and the ports and IP addresses they use. This file allows ProcessControl to start multiple servers from multiple Network Mediation installations. The format of the ProcessControl script is: Setup Guide 17

30 Chapter 2: Installation <component>:<application directory>:<port>:<ip address>:<boot start> <component> <application directory> <port> <IP address> <boot start> Specifies the type of system component. Valid types include: AdmnSvr admin server NodeMgr node manager LDAPSvr LDAP server Specifies the directory where Network Mediation is installed. Designates the port on which the server component runs. The suggested port number range is between and Specifies the IP address for the host. Use this field to identify multi-home systems. Although the field itself is required, you do not have to enter a value. You can leave it blank. Indicates whether this component is started at system boot (Y/N). The following example is an excerpt from the ProcessControl file: LDAPSvr:/<NM_HOME>_a:389::Y AdmnSvr:/<NM_HOME>_a:55105::Y NodeMgr:/<NM_HOME>_a:55109::Y ProcessControl starts the LDAP server, admin server, and node manager in the directory <NM_HOME>_a on the appropriate ports when the system boots. The IP address field in all of these commands is left blank. Similarly, when the system is shut down, all servers listed in the configuration file are shut down. The first time you install Network Mediation, a default ProcessControl script is created. Subsequent installs do not overwrite or change the contents of this script. You must manually edit the file to add new components or change port numbers. ProcessControl monitoring capabilities In addition to its startup and shut down capabilities, you can also use ProcessControl to monitor server components to ensure they are still running or to restart the server. To run ProcessControl as a server monitor, add an entry to the host /etc/inittab file. For example, to start ProcessControl in monitor mode, add the following command in the host inittab file: NT:3:respawn:/etc/init.d/ProcessControl monitor 18 MetaSolv Software, Inc.

31 Managing the ProcessControl script ProcessControl periodically reads the configuration file and checks the processes of the server components that are running. If a component is not running, ProcessControl starts it. If ProcessControl stops running, Network Mediation automatically restarts it. ProcessControl operation ProcessControl operates by running the script specific to the type of server component specified within the configuration file. To enable shut down capabilities, you use the additional command line options in the server scripts to initiate the shut down or kill actions. To stop all running servers without shutting down the system, use the following command:./processcontrol stop To start all servers defined in the configuration file, use the following command:./processcontrol start The server scripts are listed below and their command options are described in the sections that follow. UDCEnvironment nodemgr adminsvr gui slapd sets the environment variables used by all scripts starts and stops the node manager starts and stops the admin server starts and stops the admin client starts and stops the LDAP server that provides user authentication UDCEnvironment nodemgr UDCEnvironment contains environment variables used by all of the server scripts. It provides you with a single location for setting the environment, class paths, and so on for the Network Mediation server components. You use this script to start and stop the node manager. The available command options include: Setup Guide 19

32 Chapter 2: Installation nodemgr [-d -f -F] [-p <port>] [-i <IP address>] nodemgr -s [-p <port>] nodemgr -k [-p <port>] -d Runs the node manager in the background with debug output redirected to <NM_HOME>/log/nodemgr_<port>.out. This command option is CPU intensive that is, it uses a large amount of the CPU during its processes. -f Runs the node manager in the foreground. -F Runs the node manager in the foreground with debug output. -p Uses the given port number. -i Specifies the IP address to be used. It is used for multi-home systems. -s Shuts down the node manager. -k Kills the node manager process. adminsvr If you run this script with no command options, the node manager starts in the background with no debug output. Use this script to start and stop the admin server. The available command options include: adminsvr [-d -f -F] [-x][-p <port>][-i <IP address>] adminsvr -s [-p <port>] adminsvr -k [-p <port>] -d Runs the admin server in background with debug output redirected to <NM_HOME>/log/adminsvr_<port>.out. -f Runs the admin server in the foreground. -F Runs the admin server in the foreground with debug output. -x Disables user authentication. -p Uses the given port number. -i Specifies the IP address to be used. It is used for multihome systems. -s Shuts down the admin server by its shut down method. 20 MetaSolv Software, Inc.

33 Setting system monitoring options -k Kills the admin server process. If you run this script with no command options, the admin server starts in the background with no debug output. gui Use this script to start and stop the admin client. The available command options include: gui [-d -f -F] -d Runs the admin client in the background with debug output redirected to <NM_HOME>/log/gui_<port>.out. -f Runs the admin client in the foreground. -F Runs the admin client in the foreground with the debug output. slapd If you run this script with no command options, the admin client starts in the background with no debug options. Use this script to start and stop the LDAP server that provides user authentication. The available command options include: slapd [-p <port>] slapd -k -p Starts the LDAP server on the given port. The default port is k Kills the LDAP server. Setting system monitoring options This section explains the system monitoring options for the nodemgr.cfg file. If you do not modify the nodemgr.cfg file, Network Mediation uses the default threshold values. The nodemgr.cfg file is located in the following directory: /<NM_HOME>/config/nodemgr You can customize nodemgr.cfg to manage your threshold options. Network Mediation monitors disk, memory and CPU usage levels. You can set a warning threshold and an error threshold for these areas. You must decide what action to take once the thresholds are crossed. Setup Guide 21

34 Chapter 2: Installation By default, Network Mediation generates a single alarm/trap for each fault condition, even if the fault condition occurs multiple times. To generate an alarm/trap for every fault occurrence, open the nodemgr.cfg file and change the SUPPRESS_MULTIPLE_ALARMS parameter value to "No". Disk status monitor The disk status monitor alerts you to potential disk issues so you can take action to avoid the occurrence of unrecoverable errors. Note: The disk status monitor only runs on Solaris workstations that have the Sun Solstice DiskSuite metastat command installed. You can add or modify the following parameters in the nodemgr.cfg file. Table 3: Disk status monitor parameters Parameter DISK_STATUS_CMD DISK_STATUS_POLLTIME Description The full path to the metastat command. Default is /usr/sbin/metastat Amount of time to wait between polling intervals. Memory monitor The memory monitor generates a warning or major alarm if memory usage exceeds a specific, configurable threshold. In addition to the threshold, you can configure the memory monitor to log memory usage statistics. You can add or modify the following parameters in the nodemgr.cfg file. Table 4: Memory monitor parameters Parameter LOG_MEMORY_USAGE MEMORY_MAJOR_THRESHOLD MEMORY_WARNING_THRESHOLD Description Set to Y to log memory usage statistics. Default is N. The level at which a major alarm is raised, as a percentage. Default is 85. The level at which a warning alarm is raised, as a percentage. Default is MetaSolv Software, Inc.

35 Setting system monitoring options Table 4: Memory monitor parameters Parameter MEMORY_SAMPLE_TIME MEMORY_SAMPLE_FREQ Description A time interval, in seconds, during which the memory usage must be above a specific threshold level before an alarm is raised. Default is 60. The number of polls that are taken during each sample period. Default is 4. For example, using the default values for memory sample time (60 seconds) and memory sample frequency (4), the memory usage polls would occur every 15 seconds (60 seconds divided by 4). In this case, an alarm would be generated if the memory usage level was above the specified threshold for 4 consecutive polls. CPU usage monitor The CPU usage monitor generates a critical or major alarm if the CPU usage level reaches a specific value, which you can configure. You can add or modify the following parameters in the nodemgr.cfg file. Table 5: CPU usage monitor parameters Parameter CPU_REDTHRESHOLD CPU_YELLOWTHRESHOLD CPU_SAMPLETIME CPU_SAMPLEFREQ Description The percentage of CPU in use that will generate a critical alarm. The default value is 90. The percentage of CPU in use that will generate a major alarm. The default value is 80. The period, in seconds, in which to poll a fixed number of times. How often to poll during the fixed period. For example, using the default values for CPU sample time (60 seconds) and CPU sample frequency (3), a poll will take place every 20 seconds (60 seconds divided by 3). Setup Guide 23

36 Chapter 2: Installation Managing ports Network Mediation uses specific ports to send data and to receive data from external devices and applications. Use the port information in Table 6 when you are planning the network and configuring routers and firewalls that communicate between Network Mediation components. Table 6: Port Uses Application Protocol Source Source Port Destination Destination Port GTP UDP GSN 1024 or higher Network Mediation 3386 Open FTP and FTP TCP MSC, Application Server or Network Mediation 20 or 21 Application Server or Network Mediation 20 or 21 SNMP UDP Network Mediation 161 EMS 162 RADIUS UDP GSN or RADIUS Server 1814 Network Mediation 1813 DBSR TCP Network Mediation 1521 Oracle database 1521 Changing the LDAP port number Use the following procedure to change the LDAP port number from the standard 389 to a non-standard port number, such as 400, which is used in this procedure. 1. Log on as root. 2. Enter the following command to verify whether Network Mediation processes are running: ps ef grep MetaSolv 3. If processes are running, stop them by executing the following command: <NM_HOME>/bin/ProcessControl stop 4. If LDAP is running, stop it by executing the following command: <NM_HOME>/bin./slapd k 5. Navigate to the following directory: /var/opt/metasolvmediation 24 MetaSolv Software, Inc.

37 Managing mediation host security 6. Open the file: metasolv_mediation.conf. 7. Add the following line to the end of the file: LDAPSvr:/opt/nmopenldap:400 : :Y 8. Replace all occurrences of 389 with 400 in the following files: <NM_HOME>/web/htdocs/AdminServerImpl.properties (1 occurrence) <NM_HOME>/bin/slapd (3 occurrences) <NM_HOME>/ldap/data/populateDir (1 occurrence) 9. As root, execute the following to create internal directory structures and populate data: <NM_HOME>/ldap/data/populateDir 10. Verify LDAP is running by executing the following command: ps -ef grep slapd 11. Verify an additional LDAP process is also running by executing the following command: /opt/nmopenldap/ldap/libexec/slapd 12. Start the Network Mediation processes by executing the following command: <NM_HOME>/bin/ProcessControl start 13. Start the Network Mediation GUI by executing the following command: <NM_HOME>/bin/gui The default user ID is Admin and the default password is admin. Managing mediation host security Each mediation host (also called node manager), contains a nodemgr_allow.cfg file in the <NM_HOME>/config/nodemgr directory. You can use this file to manage access to the mediation hosts. The file contains a list of IP addresses for the admin servers that are allowed to connect to the mediation host. Initially, the list only contains the word ALL, which allows all admin servers to connect to the mediation host. You can edit the list at any time to allow or disallow admin server access to the mediation host. Managing the Network Mediation Administration Server firewall A network firewall between the Network Mediation server(s) and the corporate intranet or external Internet can be configured after installation. The Network Mediation Administration client can connect with and operate the Network Mediation servers through this firewall. The firewall is configured by the port numbers defined in the following sections: Setup Guide 25

38 Chapter 2: Installation Administration Server port configuration Administration client port configuration These port numbers are defined during the installation process but can be modified to accommodate your particular firewall configuration. Also, Managing the ProcessControl script on page 17 outlines the Admin Server port number which can be configured. To change this port number, see the procedure Editing metasolv_mediation.conf on page 42. Administration Server port configuration The firewallportnumber.cfg file in the <NM_HOME>/config/adminserver directory contains the configurable port numbers for the firewall. The port number is suggested to be limited to the set of numbers between and The default port numbers in the configuration file are and To change the default firewall port number range values 1. Ensure that the Network Mediation components are not running. 2. Open the firewallportnumber.cfg file in the <NM_HOME>/config/adminserver directory. 3. Change the desired port number to a value between and Save and close the file. Administration client port configuration The firewallportnumber.cfg file in the <NM_HOME>/config/GUI directory contains the configurable port number range for the firewall. The default port number range values in the configuration file are to To change the default firewall port number range values 1. Ensure that the Network Mediation components are not running. 2. Open the firewallportnumber.cfg file in the <NM_HOME>/config/gui directory. 3. Change the port number range to values between and Save and close the file. Verifying the Network Mediation installation To verify the Network Mediation installation on your UNIX system, you can manually restart the application components, or you can reboot the entire system. For information about manually starting individual components, see Starting component daemons on page MetaSolv Software, Inc.

39 Configuring Node Manager memory limits Configuring Node Manager memory limits The upper and lower (or starting) memory sizes for the Node Manager can be changed by modifying the nodemgr.var file located in the <NM_HOME>/customization/ directory. The performance of the system can be affected by changing these settings, which by default are optimized for most Network Mediation applications. Configuring the nodemgr.var file To configure the nodemgr.var file: 1. Look in the <NM_HOME>/customization/ directory to see if the nodemgr.var file is present. On a newly installed system, the nodemgr.var file may not yet exist. If the file exists, go to Step 3; otherwise, go to next step. 2. Run the following command to create the file: $ cp <NM_HOME>/config/nodemgr/nodemgr.var.reference <NM_HOME>customization/nodemgr.var 3. Open the file with a text editor. 4. The NM_MAX_MEMORY variable defines the upper limit (in megabytes) that the node manager's JVM can allocate for its heap. Modify the NM_MAX_MEMORY parameter: The default setting is The valid range for a Solaris installation is from 500 to The valid range for an AIX installation is from 500 to The valid range for a HP-UX IA64 installation is from 500 to The NM_MIN_MEMORY variable defines the lower (or starting) limit (in megabytes) that the node manager's JVM will allocate for its heap. Its default setting is 512. The valid range for a Solaris installation is from 50 to The valid range for an AIX installation is from 50 to The valid range for a HP-UX IA64 installation is from 50 to Save the nodemgr.var file. 7. Shut down the Node Manager and restart the Node Manager for the changes to take effect. Starting component daemons You can verify your Network Mediation installation by manually restarting component daemons before you configure Network Mediation. To run any component that you installed, Setup Guide 27

40 Chapter 2: Installation you must first start it. Because you can install components on different UNIX workstations, you must start each component separately. To start a component daemon 1. Log on as root on the UNIX workstation on which the component daemon is installed. 2. Navigate to the location in which you installed the component daemon. For example, type cd /<NM_HOME>/bin and press Enter to navigate to the default location of the component daemons. 3. Enter the command./<daemon_name> and press Enter. The daemon names and matching Network Mediation components are as follows: adminsvr nodemgr slapd admin server node host LDAP server After you start all daemons, you can begin to use the Network Mediation software. See the Network Mediation Online Help for more information. Running different Network Mediation versions You can have a previous version of Network Mediation running simultaneously on the same machine with Network Mediation If you are using this scenario, ensure: Both products are installed in different directories. The admin server, node manager and other components are running on different ports. See Managing the ProcessControl script on page 17 for default port numbers and instructions on changing port numbers by editing the ProcessControl script. Starting Network Mediation This section describes how to start Network Mediation on UNIX and Windows workstations. When you log in to the Network Mediation admin client for the first time, use the default user ID and password, admin. MetaSolv recommends changing your password after installing Network Mediation and at regular intervals to ensure security. Starting on a UNIX workstation Network Mediation runs on Sun Solaris 8, 9, 10, or 10 (64-Bit), IBM AIX L5, and HP-UX IA64 11i Version MetaSolv Software, Inc.

41 Starting Network Mediation To start Network Mediation on a UNIX workstation 1. Log on to the UNIX workstation where you installed Network Mediation. 2. To ensure that online help displays, make sure that your PATH environment variable includes the directory where your browser executable resides. For example, a valid PATH variable might contain the following: /usr/openwin/bin:/sbin:/bin:/usr/sbin:/usr/bin: /usr/ucb:/usr/local/bin:/app/netscape/bin 3. Navigate to the directory where you installed the software components. For example, enter cd /<NM_HOME>/bin and press Enter to navigate to the default location of the component daemons. 4. Type./ProcessControl start and press Enter. ProcessControl starts the specified servers on the desired ports. 5. Type./gui and press Enter. The Welcome to MetaSolv Network Mediation window opens. 6. In the IP Address field, type the IP address of the admin server to which you need to connect. 7. In the Port field, accept the default port number. If the mediation host to which you want to connect resides on a UDP port other than the default, you can change the port number. 8. Enter your user ID and password. If you are the system administrator logging on to a newly installed Network Mediation system for the first time, type admin for the user ID and password. 9. Click Connect. The Network Mediation admin client window opens. Setup Guide 29

42 Chapter 2: Installation Starting on a Windows workstation The Network Mediation admin client runs on Windows NT, Windows 2000 and Windows XP Professional. To start Network Mediation on a Windows workstation: 1. From the Start menu, select Programs>MetaSolv Network Mediation 5.1.1>Start Admin Client. The Welcome to MetaSolv Network Mediation window opens. 2. In the IP Address field, type the IP address of the admin server to which you want to connect. 3. In the Port field, accept the default port number. Network Mediation detects the default port number for the admin server and displays the value in the Port field. If the mediation host you want resides on a UDP port other than the default, you can change the admin server port number. 4. Enter your user ID and password. If you are the system administrator logging on to a newly installed Network Mediation system for the first time, type admin for the user ID and password. 5. Click Connect. The Network Mediation admin client window opens. Uninstalling Network Mediation The following sections explain how to run the uninstall script on UNIX and Windows workstations. The uninstall process is simple but you must do some manual removal of files. Any files that you create or modify after installing Network Mediation remain on your workstation and must be removed separately. This safeguard prevents the accidental removal of modified files during an upgrade or reinstallation. Shut down all Network Mediation processes before uninstalling. To uninstall Network Mediation on a Solaris workstation 1. Log on to the Solaris workstation as the root user. 2. Type cd <NM_HOME>/UninstallerData to navigate to the location of the Network Mediation uninstall script. 3. Type./Uninstall and press Enter. The Uninstaller dialog box opens. On a UNIX workstation, you must wait briefly for the Uninstall button to become active. 30 MetaSolv Software, Inc.

43 Uninstalling Network Mediation 4. Click Uninstall. 5. When the uninstaller program finishes, click Quit. 6. Navigate to the install directory and remove any files and folders left in the subdirectory. To uninstall Network Mediation on an AIX workstation 1. Log on to the AIX workstation as the root user. 2. Type cd <NM_HOME> 3. Navigate to the install directory and use the rm command to remove all Network Mediation files and directories. To uninstall Network Mediation on a HP-UX IA64 workstation 1. Log on to the HP-UX IA64 workstation as the root user. 2. Type cd <NM_HOME>/UninstallerData to navigate to the location of the Network Mediation uninstall script. 3. Type./Uninstall and press Enter. The Uninstaller dialog box opens. On a UNIX workstation, you must wait briefly for the Uninstall button to become active. 4. Click Uninstall. 5. When the uninstaller program finishes, click Quit. 6. Navigate to the install directory and remove any files and folders left in the subdirectory. To uninstall Network Mediation on a Windows workstation 1. Navigate to C:\<NM_HOME>\UninstallerData. 2. Double-click on Uninstall.exe. 3. In the Uninstaller window, click Uninstall. 4. When the uninstaller program finishes, click Quit. 5. Navigate to C:\<NM_HOME> and remove any files and folders left in the subdirectory. Setup Guide 31

44 Chapter 2: Installation 32 MetaSolv Software, Inc.

45 3 Upgrading This chapter describes how to upgrade to Network Mediation Version while retaining all previous node chain configuration data. Upgrading from or is supported in this release. Note: If you are upgrading from 3.4.3, begin by upgrading to or and then return to follow the procedures in this chapter. To ensure a safe transition between versions, perform the upgrade procedure in the sequence detailed in this chapter. Chapter task list The topics in this chapter include: Preparing to upgrade on page 33 Upgrading to Network Mediation on page 35 Switching to a new LDAP installation on page 39 Upgrading the Wireless GGSN/SGSN node chain on page 41 Editing metasolv_mediation.conf on page 42 Configuring new features on page 42 Preparing to upgrade Before upgrading to Network Mediation 5.1.1, read the following sections: Upgrade requirements Export and import capability Import log file Upgrade requirements Network Mediation runs on a Sun Enterprise 250 (E250) or higher, running Solaris 8, 9, 10, or 10 (64-Bit). Network Mediation also runs on AIX 5.3 and HP-UX IA64 11i Version Setup Guide 33

46 Chapter 3: Upgrading 2.0. If you plan to install Network Mediation software on the same workstations that host your current Network Mediation system, the workstations must have hardware and software resources sufficient to support both Network Mediation versions simultaneously during the export and import process. The following table shows the estimated amount of disk space required for each Network Mediation component. Table 7: Disk space requirements for components Network Mediation component admin client, admin server, and node manager LDAP server Estimated required disk space 155 MB 36 MB For more information about system requirements, see Review hardware and software requirements on page 2. After you complete the upgrade procedure and start using the Network Mediation system, you can keep or remove the previous Network Mediation version and configured node chains. Export and import capability To upgrade to Network Mediation 5.1.1, you must capture the current system configuration in an export file, and import that file during the Network Mediation installation. During the import, Network Mediation upgrades the node configurations, provides default values for new parameters, and maps nodes as necessary. Import log file The import utility uses a log file to record and timestamp every transaction and error message generated during the import. Review the log file after running the import capability. 34 MetaSolv Software, Inc.

47 Upgrading to Network Mediation Upgrading to Network Mediation To upgrade from Network Mediation or 5.0.1: 1. Determine whether each workstation has the system resources to support Network Mediation Determine the IP address, port number, and name of the old version s admin server and its node managers. You can obtain this information from the Mediation Hosts window in the admin client. 3. Determine where you want to install the Network Mediation admin server, node managers, and functional nodes. Record the planned IP address, port number, and name of the admin server and its node managers. You can either use the default ports for your installation or change them in the metasolv_mediation.conf file, which is used by the ProcessControl script. ProcessControl starts the LDAP server, admin server, and node manager in the directory <NM_HOME> on the appropriate ports when the system boots. For more information, see Managing the ProcessControl script on page 17. The default port numbers for Network Mediation are: LDAP server 389 admin server node manager Determine how you want to map the admin server and node manager addresses, ports, and names of the old version to the Network Mediation admin server and node manager IP addresses, ports, and names. Table 8 shows how a table can simplify mapping from one version to another. Table 8: Admin server and node manager map table Network Mediation component or current assignments IP address Port no. Assigned name planned assignments IP address Port no. Assigned name admin server node manager Setup Guide 35

48 Chapter 3: Upgrading Table 8: Admin server and node manager map table Network Mediation component node manager node manager node manager node manager node manager or current assignments IP address Port no. Assigned name planned assignments IP address Port no. Assigned name 5. Install a Network Mediation admin server on at least one Solaris, AIX, or HP-UX IA64 workstation that you want as part of the final Network Mediation system. 6. Install a Network Mediation node manager on each Solaris, AIX, or HP-UX IA64 workstation that you want as part of the final Network Mediation system. Do not configure the node managers. The import process performs this task. 7. Install the Network Mediation admin client on a Solaris, AIX, HP-UX IA64 or Windows workstation that you want as part of the final Network Mediation system. 8. Install the OpenLDAP directory server. If you do not install the OpenLDAP directory server, Network Mediation administrators and users cannot log on to the system. 9. Start the Network Mediation admin server and node manager daemons. 10. Start the admin server and node manager daemons of the old version. 11. Export and import: a. Export the configuration of the old version. See Exporting a configuration on page 37. b. Import the configuration of the old version into Network Mediation See Importing a configuration on page View all node and node chain configurations in the Network Mediation client to verify that the upgrade utility duplicated all nodes and node chain configurations of the old version on the Network Mediation workstations. See Verifying the Network Mediation configuration on page MetaSolv Software, Inc.

49 Upgrading to Network Mediation Switch operations from the old version to Network Mediation See Upgrading Network Mediation node chains on page Edit the Network Mediation metasolv_mediation.conf file. See Editing metasolv_mediation.conf on page Configure and save any new features or settings that you require in the Network Mediation system. See the Network Mediation Online Help for instructions. 16. Keep or remove the software and node chain configurations of the old version. To remove the software, see Uninstalling Network Mediation on page 30. To remove the node chain configuration, delete the old Network Mediation or above installation-related directories. Exporting a configuration To export all Mediation host configurations: 1. Start the Network Mediation admin client. 2. From the Admin menu, choose Export Configuration. 3. Click on Browse and locate the directory where you want to save the configurations. Click Select. 4. The Export Customization box is checked by default: Keep this box checked if you want to export a.nmx customization file that includes the exported.xml file, a.log file, an adminserver_ip_port.jar file, and a version information.xml file. Uncheck this box if you only want to export the.xml file. 5. Click Export. To export selected Mediation host configurations: 1. Start the Network Mediation admin client. 2. From the Admin menu, choose Export Configuration. 3. Click on the Selected Mediation Hosts option button. 4. Check the boxes next to all the Mediations Hosts for which you want to export the configurations. 5. Click on Browse and locate the directory where you want to save the configurations. Click Select. 6. The Export Customization box is checked by default: Setup Guide 37

50 Chapter 3: Upgrading Keep this box checked if you want to export a.nmx customization file that includes the exported.xml file, a.log file, an adminserver_ip_port.jar file, and a version information.xml file. Uncheck this box if you only want to export the.xml file. 7. Click Export. Importing a customized configuration To import a customized configuration: 1. Start the Network Mediation admin client. 2. From the Admin menu, choose Import Customization. The Import Customization dialog box opens. 3. Click Browse and select the desired.nmx export file. The node managers display in the node manager mapping pane. 4. Select a node manager from the list and click Map. The Map dialog box opens. 5. Fill out the Name, IP address and Port number fields for the new node manager. For the Port number field, use the node manager default of or the port number used in Step 3 on page Repeat Step 4 and Step 5 for the rest of the node managers in the list. 7. After mapping all node managers, click Import. During the import customization process, Network Mediation upgrades nodes and provides default parameters for any new configuration options for the updated nodes. Once distribution is completed, you will be asked to restart the admin server and all node managers. Importing a configuration To import a configuration: 1. Start the Network Mediation admin client. 2. From the Admin menu, choose Import Configuration. The Import Configuration dialog box opens. 3. Click Browse and select the desired.xml export file. The node managers display in the node manager mapping pane. 4. Select a node manager from the list and click Map. 38 MetaSolv Software, Inc.

51 Switching to a new LDAP installation The Map dialog box opens. 5. Fill out the Name, IP address and Port number fields for the new node manager. For the Port number field, use the node manager default of or the port number used in Step 3 on page Repeat Step 4 and Step 5 for the rest of the node managers in the list. 7. After mapping all node managers, click Import. The new node managers are added and the corresponding nodes are created. Any errors are recorded in the upgrade log and displayed after the import. During the import process, Network Mediation upgrades nodes and provides default parameters for any new configuration options for the updated nodes. Verifying the Network Mediation configuration When you finish exporting and importing, verify that the nodes and node chain configurations with their current parameter settings were duplicated. Also verify that you can start the nodes and node chains. If any nodes were removed due to node obsolescence, you can upgrade the affected node chain configurations. For more information, see Configuring new features on page 42. Refer to the upgrade log file for the Node Destinations list and the Node ID Conversion Table to aid the verification procedure. In case of trouble during an import The import process uses a best effort approach where any successfully created node managers and nodes remain intact, even if errors occur during the import. If an import has errors or terminates abnormally, examine the following files: Console session history Import log You can find the import log file in the log directory of the installation directory. For example: <NM_HOME>/log/import_ _ log The import log file resides on the same machine as the admin client. If needed, call technical support and supply information from the console session history or the upgrade log file. Switching to a new LDAP installation If you are switching from an existing to a new LDAP installation, you must perform the following procedure after completing the installation and upgrade steps. Setup Guide 39

52 Chapter 3: Upgrading To change LDAP versions 1. On the host workstation running LDAP, locate the old slapd process in the installation directory. The following list shows the default installation directories MetaSolvNetworkMediation MetaSolvNetworkMediation MetaSolvNetworkMediation Execute the following command using the appropriate installation directory: # ps -eaf grep slapd root :11:37? 0:00 / <Install_Directory>/ldap/libexec/slapd -f / <Install_Directory>/ Kill the old LDAP process using the following command: # kill Run the populate directory script, using the following command: # /MetaSolvNetworkMediation511/ldap/data/populateDir This command uses the default directory of /MetaSolvNetworkMediation511. If you installed Network Mediation elsewhere, enter that directory instead. The following information displays: Starting slapd on TCP/IP port /MetaSolvNetworkMediation501/ldap/libexec/slapd -f / MetaSolvNetworkMediation501/ldap/etc/slapd.conf -p 389 Waiting 5 seconds for slapd to start... Populating the directory... Verifying entries... Directory populated successfully. 5. Verify slapd is running using the following command: # ps -eaf grep slapd root :04:02? 0:00 /MetaSolvNetworkMediation511/ldap/libexec/ slapd -f /MetaSolvNetworkMediation511/ldap/etc/slapd.conf You can now log on using the new LDAP installation. The default login user ID and password is admin. Data from the old LDAP system is not transferred into the new LDAP system. You must re-create users and passwords for the new LDAP system. 40 MetaSolv Software, Inc.

53 Upgrading Network Mediation node chains 6. When you are satisfied with the new LDAP installation, modify the host workstation startup scripts so the former LDAP server does not startup upon reboot using the following command: # rm /etc/rc2.d/s81slapd Upgrading Network Mediation node chains When you complete the export and import tasks, you can upgrade from the previous Network Mediation node chains to To upgrade node chains: 1. Configure the 5.1 CC to look for incoming records in a directory different from the one in which the or CC looks for records. 2. Configure the network devices to send records to the directory monitored by the 5.1 CC. 3. Start all nodes in the 5.1 node chain. 4. Verify data output from the 5.1 node chain. 5. Stop the or CC. 6. Verify the input directories of all nodes in the or chains to ensure all files are processed. 7. Stop all nodes in the or chain. Upgrading the Wireless GGSN/SGSN node chain To upgrade the GGSN/SGSN node chain from Network Mediation or to 5.1.1, complete the following procedure. Note that the upgrade occurs between two separate systems so there is no connectivity between the node chains. PDP sessions that are open during the upgrade may contain partial and duplicate records since the EP and AP cannot process these records. To upgrade the or GGSN/SGSN node chain: 1. Stop the old GGSN/SGSN CC, Session Sequencing EP and Session Aggregation AP. 2. Start all nodes in the 5.1 node chain, except the DC. Note: In 5.0, the GGSN/SGSN CC has been replaced by the GTP Prime Collection CC and the 3GPP Parsing EP. 3. Open the node configuration window for the old GGSN/SGSN CC and on the GSM3GPP tab, change the Receive Port number to 3396 and the Send Port number to Open the node configuration window for the old Session Sequencing EP and on the Sequencing tab, change the Expiry Interval to 2 minutes. Setup Guide 41

54 Chapter 3: Upgrading 5. Open the node configuration window for the old Session Aggregation AP and on the Aggregator tab, change the Flush Time to 300 seconds (5 minutes). 6. Open the node configuration window for the old DC and on the File Output tab, change the Output Push Time Unit to minutes and the Output Push Time Period to Start the old GGSN/SGSN CC, Session Sequencing EP and Session Aggregation AP to clear the chain and wait twenty minutes to ensure the old chain processes and outputs all data. 8. Verify the input directories of all nodes in the old chain to ensure all files are processed and then stop the chain. 9. Start the 5.1 DC. 10. Verify data output from the node chain. Editing metasolv_mediation.conf For Network Mediation 5.1.1, you must edit metasolv_mediation.conf to include the new directory path and ports for the node manager and admin server. To edit the metasolv_mediation.conf file, complete the following steps: 1. Go to the following directory: /var/opt/metasolvmediation 2. Open metasolv_mediation.conf. 3. In the section that contains the directory paths and port numbers, change the install directory to the current one and change the port numbers for the node manager and admin server. The following example shows the entries to be updated: NodeMgr:/<NM_HOME>:55109::Y AdmnSvr:/<NM_HOME>:55105::Y LDAPSvr:/<NM_LDAP_HOME>:389::Y 4. Save the file. Configuring new features Now that you have upgraded, you must configure any features that are new to Network Mediation For a list of new features, see the Network Mediation Release Notes. For configuration information, see the Network Mediation Online Help, which you can access via the Administration Client. 42 MetaSolv Software, Inc.

55 4 Backing Up and Restoring After installing or upgrading a Network Mediation system, perform one or both of the following backups as a safety measure: Standard configuration backup Complete system backup For information on complete system backups, refer to your operating system documentation. Repeat one or both of the backup procedures whenever you make incremental changes to the system configuration or rule files. If you have not backed up the system on a regular basis, you must reinstall and reconfigure a system corrupted by an operational error such as an AC power interruption or a disk full condition. Reinstalling and reconfiguring eliminates any chance of recovering and reprocessing mediation data transitioning through the system at the time of the operational error. The topics in this chapter include: Backing up a standard system configuration on page 44 Backing up a full installation on page 45 Restoring Network Mediation on page 46 Restoring a standard system configuration on page 47 Restoring a full installation on page 47 Preserving data when no backup exists on page 49 Preparing to restore NARs on page 51 Restoring NARs on page 51 Backup and restore options Standard configuration The standard backup procedure captures the configuration of an entire Network Mediation host, provided that you have not made any modifications to it other than those possible through the Network Mediation admin client. Setup Guide 43

56 Chapter 4: Backing Up and Restoring Perform this procedure as soon as you have fully configured Network Mediation to suit your requirements. Perform this procedure even if you have performed a complete system backup. When you complete a standard configuration backup, you can use the backup configuration directory to restore the Network Mediation system. You restore a Network Mediation system by replacing the damaged configuration directory with a copy of the backup configuration directory. In this circumstance, you restore the system with the same node IDs and data directory structure, and with user data retained in input, output, and scratch directories at the time of the operational error. If you require Network Mediation technical support, you can use to send a copy of your backup configuration directory to your MetaSolv Global Customer Care representative. This allows your support representative to see all the details of your system configuration. If you want to send a copy of your configuration directory, first use the UNIX tar command to create an archived version of that directory. In this way, you can send just one file to your support representative. Complete system The complete system backup procedure backs up the configuration of a Network Mediation host that you have modified extensively by a means other than the Network Mediation admin client. For example, you may want to perform this procedure if you modified rule files and applied software patches. You can perform this procedure as soon as you have fully configured Network Mediation. After you perform this procedure, you can use the resulting tar file to fully restore your customized Network Mediation system. You can use the restoration procedure to restore an existing system or to install the same Network Mediation system configuration on another host. Backing up a standard system configuration This procedure is for backing up node chain configurations, but not data. To back up a standard Network Mediation system configuration 1. Complete the following steps to stop all functional nodes in the system: a. In the admin client, select all nodes by left-clicking and drawing a box around them. b. Right-click and select stop node(s). 2. Navigate to the system installation directory. For example: cd /MetaSolvNetworkMediation Copy the directory config with a new name. 44 MetaSolv Software, Inc.

57 Backing up a full installation For example: cp -r config config8nov 4. Create an archive of the entire directory with a tar command. For example: tar cvf config8nov.tar config8nov 5. Store the backup copy in a location outside of the Network Mediation system. For example: mv config8nov.tar <new directory> 6. Complete the following steps to restart the nodes: a. In the admin client, select all nodes by left-clicking and drawing a box around them. b. Right-click and select start node(s). Backing up a full installation Ensure the disk partition in which your Network Mediation system resides has more than 70 percent of its total reserved space still available before you perform this task. This procedure backs up node chain configurations and data in transit but not processed data outside of the installation directory. To back up a full Network Mediation installation 1. Shut down the entire system using the following commands in the order shown: cd /<install directory>/bin./processcontrol stop 2. Create a copy of the installation directory. For example, if you originally installed Network Mediation under /MetaSolvNetworkMediation511, copy the entire directory using the following command: cp -r /MetaSolvNetworkMediation511 /MetaSolvNetworkMediation511tmp This operation may take a few minutes to finish. 3. Change to the duplicate installation directory using the following commands: cd /MetaSolvNetworkMediation511tmp 4. In the duplicate installation directory, remove the subdirectories input, output, and scratch using the following command: rm -r input output scratch Setup Guide 45

58 Chapter 4: Backing Up and Restoring This prevents the restoration of old and duplicate billing records when you are restoring a full installation. 5. Create an archive of the duplicate installation directory. For example: tar cvf /MetaSolvNetworkMediation511backup.tar / MetaSolvNetworkMediation511tmp This operation may take a few minutes to finish. 6. Store a copy of the tar file image of your Network Mediation system at a different location. 7. Remove the duplicate installation directory using the following command: rm -r /MetaSolvNetworkMediation511tmp 8. Restart Network Mediation. Restoring Network Mediation The following sections outline how to restore Network Mediation for full installations and standard and non-backed up configurations. Note: You must shut down all admin clients before performing a restore operation to ensure the restored configuration is accurate. Failing to shut down the admin clients before performing a restore operation can result in an overwrite of the restored configuration. If you customized any part of Network Mediation by a means other than the Network Mediation admin client and the system is corrupt, restore the system as a standard configuration. If that procedure does not restore the system, restore it as a full installation. If the disk partition in which Network Mediation resides is full, you must create, at the same level as the existing installation directory, enough space to restore your system. The amount of space that you create depends on whether you need to save data from the input, output, and scratch subdirectories. If you do not need to save data from the input, output, and scratch subdirectories, create at least three times the disk space normally occupied by your archived installation directory. If you need to save data from the input, output, and scratch subdirectories, create at least three times the disk space collectively occupied by your archived installation directory plus subdirectories input, output, and scratch. In the following sample system restoration, you must create space within the installation directory /MetaSolvNetworkMediation511. The archive file containing the installation directory is MetaSolvNetworkMediation511backup.tar. 46 MetaSolv Software, Inc.

59 Restoring Network Mediation Restoring a standard system configuration To restore a standard system configuration 1. Obtain the backup copy of your system config directory. 2. If you retrieved a tar file copy of the backup configuration directory, extract the configuration directory. For example: tar xvf config8nov.tar The file untars and the config8nov directory and structure is created. 3. Stop Network Mediation using the following commands in the order shown: cd /<install directory>/bin./processcontrol stop 4. Change to the system installation directory. For example: cd /MetaSolvNetworkMediation To remove the damaged configuration directory, type rm -r config and press Enter. 6. Copy the backup configuration directory into the system installation directory For example: cp -r config8nov config 7. Restart the Network Mediation system using the following commands in the order shown: cd /<install directory>/bin./processcontrol start Restoring a full installation Contact MetaSolv technical support if you need help restoring Network Mediation. To restore a full Network Mediation system that has been backed up 1. Shut down the entire system using the following commands in the order shown: cd /<install directory>/bin./processcontrol stop 2. Retrieve the backup tar file of your system installation directory. 3. Extract from the tar file the backup copy of your installation directory. For example: Setup Guide 47

60 Chapter 4: Backing Up and Restoring tar xvf /MetaSolvNetworkMediation511backup.tar The command recreates the duplicate installation directory, in this example, /MetaSolvNetworkMediation511tmp. 4. To save as much data as possible from Network Mediation, change to the existing installation directory. For example: cd /MetaSolvNetworkMediation If you determine the directory is not corrupt, copy the subdirectories input, output, and scratch into the duplicate installation directory. For example: cp -r input /MetaSolvNetworkMediation511tmp/ cp -r output /MetaSolvNetworkMediation511tmp/ cp -r scratch /MetaSolvNetworkMediation511tmp/ Duplicate records may occur because you do not know which records have already been sent to the billing system. 6. Delete or rename the corrupted installation directory. To delete, use the following command: rm -r /MetaSolvNetworkMediation511 To rename, use the following command: mv /MetaSolvNetworkMediation511 /MetaSolvNetworkMediation511data 7. Rename the restored installation directory. For example: mv /MetaSolvNetworkMediation511tmp /MetaSolvNetworkMediation Change to the bin subdirectory within the restored installation directory. For example: cd /MetaSolvNetworkMediation511/bin 9. To restart the system type./processcontrol start and press Enter. The system recreates the input, output, and scratch directories in your restored installation directory, unless you already copied them over. 48 MetaSolv Software, Inc.

61 Preserving data when no backup exists Preserving data when no backup exists MetaSolv does not support any procedure for restoring a Network Mediation system that has not been backed up. However, if you have no backup and you want to save as much existing NAR data as possible, MetaSolv recommends the following procedure. To preserve data 1. Stop all nodes in the system. 2. Restart one node at a time, beginning with the node at the end of the corrupted chain. A node may be unable to read corrupt NARs from its input directory and may stall during restart. After you finish observing the behavior of one node, stop it and move on to the next node in the chain. 3. To aid in your observation of node behavior, use the following command to watch mediation host CPU utilization for node processing: iostat int 1 Output resembles the following listing: maya% iostat int 1 tty sd0 sd1 sd2 cpu tin tout Kps tps serv Kps tps serv Kps tps serv us sy wt id The last column on the right represents the percentage of total CPU idle time. The lower the number in this column, the more CPU time is being used to service functional nodes running in the system. When a node stalls, the CPU idles more frequently, causing the idle percentage value to rise. 4. Periodically list or monitor the number of NAR files in the node input directory. For example, at the node input directory, enter one of the following commands: ls wc While a functional node runs, it consumes at least 50 percent of the CPU idle time on a dual processor machine. If the CPU percentage idle is near 100 percent and the number of NAR files in the input directory is not going down, then it is possible that the NAR file currently being read by the functional node from its input directory is corrupt. The NAR file currently being processed is the one with the oldest time stamp in its name. Setup Guide 49

62 Chapter 4: Backing Up and Restoring 5. Stop the node and use the commands rm or mv to remove the suspect NAR file from the input directory. 6. Restart the node and see whether the number of NAR files in the node input directory begins to go down. If the CPU idle percentage number decreases, then there is an increased level of CPU usage for node processing. If you do not observe this, then the NAR file you removed probably was not corrupt. In this case, stop the node, remove the entire contents of its scratch directory, and restart the node. The node resumes the processing NAR files from its input directory. If the node continues to stall, stop it, and remove the entire contents of its input directory. Restart the node and it resumes the processing NAR files from its input directory. 7. Repeat these actions for each node in the chain, as necessary, to identify corrupt NAR files and to restore system operation. Call MetaSolv technical support for further assistance restoring a Network Mediation system that has not been backed up. NAR file backup and restore operations If an adverse operational event, such as AC power interruption, mediation host failure, or a hardware or software error corrupts NAR data or prevents one or more processed NARs from being delivered to their destinations, you can restore and reprocess previously backed up NAR files. You can also engage safe mode on an E250 workstation NAR file backup is only available for certain nodes and is enabled through the node configuration window. During a NAR backup operation, the system moves each processed NAR file from the input directory to the backup directory of a node and changes the NAR file extension from.arch to.archbkup. When you restore a backed up NAR file, you change its file extension from.archbkup to.arch in the backup directory and move or copy the renamed file into the node's input directory. Then, the node processes the NAR file and returns it to the backup directory with the file's last-modification date or timestamp intact. The system processes NAR files according to their last-modification timestamp, starting with those having the earliest timestamp. How you restore a backup file determines when the file is reprocessed by the node and the length of time that the file remains in the backup directory after reprocessing. If you restore a NAR file by moving it from the backup directory to the input directory, the file's last modification time does not change. If you restore a NAR file by copying it from the backup directory to the input directory, the system creates a new file with a modification time set to the current system time. 50 MetaSolv Software, Inc.

63 Preparing to restore NARs If NAR processing order is important to the downstream mediation or operations and management (OAM) systems, move or copy the backup files, as needed. Preparing to restore NARs To restore NAR files backed up for a specific node, you must enable and configure the node's automated NAR file backup feature. 1. After you detect a problem with corrupted NAR data in the downstream mediation or OAM system, determine: The time the problem began The effect of the problem on your system The source of the problem if possible Before you restore any NAR files, make sure to identify and repair the source of the problem, so that the same problem does not reoccur. 2. Clean up any suspect downstream data. You may need to delete some or all of the affected data. 3. Determine which backup NAR files need to be restored by comparing the time the problem began to the timestamp contained in the name of each backup NAR file associated with the affected node chains. The NAR file timestamp indicates the moment the backup file was created. The file contains data captured from that time forward, up to the configured NAR file size. Restore the sequence of backup NAR files that covers the full interval during which the problem occurred. Restoring NARs Use this procedure to restore and reprocess NAR files. For each NAR file that you want to restore and reprocess 1. Log on to the Network Mediation admin client and determine the ID of the node with the NAR file that you want to restore. 2. Select the mediation server on which the node resides that you want to examine. 3. Select the functional node and click Edit. The Node dialog box opens. The node ID is the fourth item in the dialog box. 4. Stop the node. 5. Navigate to the installation directory. For example: Setup Guide 51

64 Chapter 4: Backing Up and Restoring cd /MetaSolvNetworkMediation List the contents of the subdirectories input and backup using the following command: ls input backup The UNIX system displays a list of subdirectories named for the ID of each node. For example, you may see output similar to the following: backup: 1hb48pz-8ha-cdyeaz08 1hb48pz-8ha-cdyex5zr 1hb48pz-8ha-cdyf91bt 1hb48pz-8ha-cdyek5tl 1hb48pz-8ha-cdyf5xxu 1hb48pz-8ha-cdyfabet 1hb48pz-8ha-cdyel3we 1hb48pz-8ha-cdyf7gvb 1hb48pz-8ha-cdynof9c 1hb48pz-8ha-cdyetth6 1hb48pz-8ha-cdyf8a5n input: 1hb48pz-8ha-cdyeaz08 1hb48pz-8ha-cdyex5zr 1hb48pz-8ha-cdyf91bt 1hb48pz-8ha-cdyek5tl 1hb48pz-8ha-cdyf5xxu 1hb48pz-8ha-cdyfabet 1hb48pz-8ha-cdyel3we 1hb48pz-8ha-cdyf7gvb 1hb48pz-8ha-cdynof9c 1hb48pz-8ha-cdyetth6 1hb48pz-8ha-cdyf8a5n 7. Navigate to the backup directory that contains a NAR file that you want to restore. For example, type: cd 1hb48pz-8ha-cdyeaz08 8. Move or copy the NAR file from the node's backup directory to its input directory. For example, type: mv <NAR_file_name>.archbkup../input/ <NAR_file_name>.arch 9. Rename the file. For example: <filename>.archbkup to <filename>.arch 10. Start the node. The node reprocesses the NAR file. 52 MetaSolv Software, Inc.

65 5 Database Storage and Reporting This chapter provides installation and configuration information for the optional Network Mediation Database Storage and Reporting solution. This solution is part of the Network Mediation Cartridge Development Kit. For more information, contact your MetaSolv sales representative. Chapter task list The topics in this chapter include: Creating an Oracle user and dba group on page 56 Installing Oracle on page 57 Verifying the Oracle installation on page 59 Loading the Network Mediation schema on page 60 Configuring Oracle on page 61 Configuring UNIX executables on page 62 Configuring and using the Repository Manager on page 62 Installing the Oracle Client on page 66 Modifying tnsnames.ora on page 66 Installing the Oracle JDBC driver on page 67 Configuring Oracle for automatic restart on page 67 Verifying the Oracle automatic restart on page 68 Crystal Reports on page 69 Setup Guide 53

66 Chapter 5: Database Storage and Reporting Database Storage and Reporting architecture The Database Storage and Reporting market segment lets you configure DMS-MSC node chains that process and distribute data to both a billing system and an Oracle 9i database. Through the use of Crystal Reports, you can query the database for certain DMS-MSC records and capture the results in a report. Figure 1 below shows the recommended configuration of the Database Storage and Reporting node chain. The DMS-MSC CC collects data from DMS-MSC network devices and passes the data to both the DMS-MSC AMA DIRP DC and the JDBC DC. The DMS-MSC AMA DIRP DC sends the data to a billing system. The JDBC DC sends the data to an Oracle 9i database. Repository Manager Figure 1: Database Storage and Reporting architecture The Repository Manager is a Network Mediation tool that runs on an Oracle server and can import and export CDRs from an Oracle 9i Enterprise database. You can configure the Manager to export CDRs at a specific time and store them in an accessible way, such as on Digital Audio Tape (DAT) or Digital Linear Tape (DLT). The Manager can import the archived CDRs at a later date, if necessary. You can also configure the Manager to delete CDRs from the database at the same time every day, if you do not wish to archive them. 54 MetaSolv Software, Inc.