NetIQ Performance Endpoints 5.1. User Guide

Transcription

1 NetIQ Performance Endpoints 5.1 User Guide July 2011

2 Legal Notice THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU. This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data. This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time NetIQ Corporation. All rights reserved. U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R (for Department of Defense (DOD) acquisitions) and 48 C.F.R and (for non-dod acquisitions), the government s rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement. Check Point, FireWall-1, VPN-1, Provider-1, and SiteManager-1 are trademarks or registered trademarks of Check Point Software Technologies Ltd. ActiveAudit, ActiveView, Aegis, AppManager, Change Administrator, Change Guardian, Compliance Suite, the cube logo design, Directory and Resource Administrator, Directory Security Administrator, Domain Migration Administrator, Exchange Administrator, File Security Administrator, Group Policy Administrator, Group Policy Guardian, Group Policy Suite, IntelliPolicy, Knowledge Scripts, NetConnect, NetIQ, the NetIQ logo, PSAudit, PSDetect, PSPasswordManager, PSSecure, Secure Configuration Manager, Security Administration Suite, Security Manager, Server Consolidator, VigilEnt, and Vivinet are trademarks or registered trademarks of NetIQ Corporation or its subsidiaries in the USA. All other company and product names mentioned are used only for identification purposes and may be trademarks or registered trademarks of their respective companies. For purposes of clarity, any module, adapter or other similar material ("Module") is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.

3 Contents About this Book and the Library...vii About NetIQ Corporation...ix Chapter 1 Introducing Performance Endpoints 1 Chapter 2 Endpoint Initialization File 3 ALLOW...4 SECURITY_AUDITING...4 AUDIT_FILENAME...5 ENABLE_PROTOCOL...5 Configuring Endpoints for Large-Scale Customization...6 Chapter 3 HP-UX 7 System Requirements...7 Installing the Endpoint...8 Unattended Installation for HP-UX...9 What Happens During Installation...9 Removing the Endpoint Package...9 Configuring HP-UX Endpoints...10 Starting an HP-UX Endpoint...11 Stopping an HP-UX Endpoint...11 How to Tell Whether an HP-UX Endpoint Is Active...12 Disabling Automatic Startup...12 Logging and Messages...12 Chapter 4 IBM AIX 15 System Requirements...15 Installing the Endpoint...16 Unattended Installation for AIX What Happens During Installation Removing the Endpoint Package Configuring AIX Endpoints...18 Starting an AIX Endpoint...19 Stopping an AIX Endpoint...19 How to Tell Whether an AIX Endpoint Is Active...20 Disabling Automatic Startup...20 Logging and Messages...20 Contents iii

4 Chapter 5 Linux 21 System Requirements...22 Installing the RPM-Based Endpoint for Linux...22 Removing the RPM Endpoint Package...23 Installing the Cobalt-Based Endpoint for Linux...23 Removing the Cobalt Endpoint Package...24 Installing the TAR-Based Endpoint for Linux...24 Removing the TAR-Based Endpoint Package...26 What Happens During Installation...26 Configuring Linux Endpoints...26 Starting a Linux Endpoint...28 Stopping a Linux Endpoint...28 How to Tell Whether a Linux Endpoint Is Active...29 Automatically Starting the Endpoint...29 Disabling Automatic Startup...30 Logging and Messages...30 Increasing the Number of Concurrent Connections...30 Chapter 6 Microsoft Windows 31 System Requirements...32 Installing the Endpoint...33 Removing the Endpoint Software...35 Configuring Windows Endpoints...35 Starting the Endpoint...37 Stopping the Endpoint...37 Disabling Your Screen Saver...37 Using the SetAddr Utility...37 Disabling Automatic Startup...39 How to Tell Whether a Windows Endpoint Is Active...39 Logging and Messages...39 Chapter 7 Sun Solaris 41 System Requirements...41 Installing the Endpoint...42 Admin File for Default Solaris Installation...43 Unattended Installation for Solaris...43 What Happens During Installation...44 Removing the Endpoint Package...44 Configuring Solaris Endpoints...45 Starting a Solaris Endpoint...46 Stopping a Solaris Endpoint...46 How to Tell If a Solaris Endpoint Is Active...47 Disabling Automatic Startup...47 Logging and Messages...47 iv User Guide

5 Chapter 8 Web-Based Performance Endpoint 49 Running the Web-Based Endpoint...50 Error Handling...50 Compatibility with Other Endpoints...51 Stopping the Web-Based Endpoint...51 Contents v

6 vi User Guide

7 About this Book and the Library The NetIQ AppManager product (AppManager) is a comprehensive solution for managing, diagnosing, and analyzing performance, availability, and health for a broad spectrum of operating environments, applications, services, and server hardware. AppManager provides system administrators with a central, easy-to-use console to view critical server and application resources across the enterprise. With AppManager, administrative staff can monitor computer and application resources, check for potential problems, initiate responsive actions, automate routine tasks, and gather performance data for real-time and historical reporting and analysis. Intended Audience This guide provides information for individuals responsible for installing an AppManager module and monitoring specific applications with AppManager. Other Information in the Library The library provides the following information resources: Installation Guide for AppManager Provides complete information about AppManager pre-installation requirements and step-by-step installation procedures for all AppManager components. User Guide for AppManager Control Center Provides complete information about managing groups of computers, including running jobs, responding to events, creating reports, and working with Control Center. A separate guide is available for the AppManager Operator Console. Administrator Guide for AppManager Provides information about maintaining an AppManager management site, managing security, using scripts to handle AppManager tasks, and leveraging advanced configuration options. Upgrade and Migration Guide for AppManager Provides complete information about how to upgrade from a previous version of AppManager. Management guides Help Provide information about installing and monitoring specific applications with AppManager. Provides context-sensitive information and step-by-step guidance for common tasks, as well as definitions for each field on each window. The AppManager library is available in Adobe Acrobat (PDF) format from the NetIQ Web site: About this Book and the Library vii

8 Conventions The library uses consistent conventions to help you identify items throughout the documentation. The following table summarizes these conventions. Convention Use Bold Window and menu items Technical terms, when introduced Italics Book and CD-ROM titles Variable names and values Emphasized words Fixed Font File and folder names Commands and code examples Text you must type Text (output) displayed in the command-line interface Brackets, such as [value] Optional parameters of a command Braces, such as {value} Required parameters of a command Logical OR, such as value1 value2 Exclusive parameters. Choose one parameter. viii User Guide

9 About NetIQ Corporation NetIQ, an Attachmate business, is a global leader in systems and security management. With more than 12,000 customers in over 60 countries, NetIQ solutions maximize technology investments and enable IT process improvements to achieve measureable cost savings. The company s portfolio includes awardwinning management products for IT Process Automation, Systems Management, Security Management, Configuration Audit and Control, Enterprise Administration, and Unified Communications Management. For more information, please visit Contacting Sales Support For questions about products, pricing, and capabilities, please contact your local partner. If you cannot contact your partner, please contact our Sales Support team. Worldwide: United States and Canada: Web Site: Contacting Technical Support For specific product issues, please contact our Technical Support team. Worldwide: Contacting Documentation Support Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you. Contacting the Online User Community info@netiq.com North and South America: Europe, Middle East, and Africa: +353 (0) Web Site: support@netiq.com Qmunity, the NetIQ online community, is a collaborative network connecting you to your peers and NetIQ experts. By providing more immediate information, useful links to helpful resources, and access to NetIQ experts, Qmunity helps ensure you are mastering the knowledge you need to realize the full potential of IT investments upon which you rely. For more information, please visit About NetIQ Corporation ix

10 x User Guide

11 Chapter 1 Introducing Performance Endpoints This guide contains information about installing, configuring, and running NetIQ Performance Endpoints. Performance Endpoints are lightweight software agents that allow you to send synthetic VoIP traffic between two nodes on your network and take performance measurements. Enpoints are available for several operating systems. The latest version of the endpoint software can be downloaded free from the Web. A single installation file for each supported operating system is available at You cannot run endpoint software from a CD. You must install it on a computer. The following table identifies the NetIQ products that support Performance Endpoints. System requirements for individual endpoint packages are itemized in the corresponding chapters in this guide. NetIQ Product Endpoint Vivinet Assessor Vivinet Diagnostics AppManager ResponseTime for Networks HP-UX No No Yes No IBM AIX No No Yes No Linux for Cobalt RaQ3 (x86) Yes Yes Yes Yes Linux x86 (TAR) Yes Yes Yes Yes Linux x86 (RPM) Yes Yes Yes Yes Microsoft Windows Yes Yes Yes Yes Sun Solaris (SPARC and x86) Yes Yes Yes Yes AppManager for VoIP Quality Chapter 1 Introducing Performance Endpoints 1

12 2 User Guide

13 Chapter 2 Endpoint Initialization File An endpoint initialization file is installed with each Performance Endpoint. With this file, you can perform the following tasks: Restrict the use of this endpoint to specific AppManager, Vivinet Diagnostics, or Vivinet Assessor consoles Control which access attempts are logged in an audit file Change the filename of the audit file Enable only particular protocols on this endpoint for setup connections On most operating systems, this file is named endpoint.ini. This file has the same format and structure on all supported operating systems. By default, the endpoint initialization file contains the following keywords and parameters. You can change these keywords and parameters to tailor individual endpoints for your needs. Keyword ALLOW SECURITY_AUDITING AUDIT_FILENAME ENABLE_PROTOCOL Parameters ALL NONE ENDPOINT.AUD ALL The endpoint.ini file is an editable text file. There is a separate copy for each operating system. You should customize it before endpoint installation. Your changes are then incorporated into each installation for different sets of computers. You can modify this text file before installation by copying the endpoint installation directory for an operating system to a hard drive, preferably a LAN drive, and then modifying the file before running the installation from that drive. Chapter 2 Endpoint Initialization File 3

14 ALLOW This keyword determines which computers can run tests using this endpoint. To allow any user to run tests on this endpoint, use the ALL parameter, which is the installation default: ALLOW ALL However, although ALLOW ALL is the default, it is not recommended. ALLOW ALL makes it easy to install an endpoint and see that it is running, but it also lets any user who can reach the endpoint potentially use that endpoint as a traffic generator. To allow only specific users to run tests with this endpoint, remove the ALLOW ALL line and identify one or more specific computers by their network addresses. You can specify more than one address per protocol. For example, ALLOW TCP ALLOW TCP Specify a connection-oriented protocol (that is, TCP) as the first parameter and provide its corresponding network address as the second parameter. Endpoints listen only for incoming tests on connectionoriented protocols, such as TCP. Datagram tests are set up and results are returned using their sister connection-oriented protocol. Thus, UDP tests are set up using TCP. The network address in TCP/IP must be in dotted notation. Endpoints do not respond to endpoint discovery requests unless the IP address of the computer is specifically allowed, or unless ALLOW ALL is specified. This prevents the user of a computer from finding endpoints to which it should not have access. You cannot use the ALLOW parameter to restrict access from one endpoint to another endpoint. The ALLOW parameter can be used only to permit or prevent access from specific computers to the endpoint at which the parameter is defined. To restrict your endpoint to access only your own computer, specify your own IP network address rather than Specify , the equivalent of localhost, to allow another user who specifies localhost as Endpoint 1 to access your computer as Endpoint 2. SECURITY_AUDITING This keyword determines which access attempts the endpoint logs in its audit file. The following table identifies the possible parameters: NONE PASSED REJECTED ALL Writes nothing to the audit file Logs only access attempts that passed the ALLOW address check. Logs only access attempts that failed the ALLOW address check. Logs both passed and rejected access attempts. If a test initialization fails for a reason other than address checking, no entry is made in the audit file. 4 User Guide

15 AUDIT_FILENAME This keyword specifies the filespec for the audit file. For more information, see SECURITY_AUDITING on page 4. The default filename is endpoint.ini is endpoint.aud. If no drive or path is specified, the audit file uses the drive and path of the endpoint program. This file contains at most two lines for each endpoint pair that is started on this endpoint. These two lines represent the start of an endpoint instance and the end of that instance. Each line written to the audit file consists of a set of information about the endpoint instance and what it has been asked to do. The information is written in comma-separated form, so you can load the audit file into a spreadsheet or database. When the audit file is created, an initial header line explains the contents of the subsequent entries. The following table shows the fields of each entry in the audit file: Field Time Action Description The date and time when the entry was created, in the local time zone. Whether an endpoint instance was "Started" or "Ended." Endpoint Whether the endpoint is in the role of Endpoint 1 or Endpoint 2. Protocol of Console The network protocol used to contact Endpoint 1. Network Address of Console Security Result Endpoint Partner Protocol Endpoint Partner Address The network address as seen by Endpoint 1. If you encounter problems setting up your ALLOW entries, use this value for the protocol address. Whether this SECURITY_AUDITING "passed" or was "rejected." If this is an entry for an "Ended" action, this field is reported as "n/a." The network protocol used to run the test with a partner endpoint. The network address of a partner endpoint. ENABLE_PROTOCOL This keyword lets you control which connection-oriented protocols an endpoint uses to listen for setup connections. This does not affect the network protocols, which can be used to run tests. There are two possible parameters: ALL TCP In general, you should use the ALL setting, which is the default. Specify protocols explicitly to reduce the overhead of listening on the other protocols or if you encounter errors when listening on the other protocols. For more information, see ALLOW on page 4. Chapter 2 Endpoint Initialization File 5

16 Configuring Endpoints for Large-Scale Customization To customize features such as automatic upgrades, you must edit the endpoint.ini file for each endpoint. For obvious reasons, you may not want to manually undertake such a potentially lengthy procedure. To perform a large-scale customization of endpoint.ini, you can extract the files contained in gsendw32.exe, which is installed by default in when you install the Performance Endpoint software. In addition to WinZip, you need the WinZip command-line support add-on and WinZip Self-Extractor. To extract the files in gsendw32.exe: 1. From the location in which you installed the Performance Endpoint software, double-click the gsendw32.exe file and extract the files to a temporary directory. 2. Edit or replace the endpoint.ini that is now in the temporary directory. 3. Using WinZip, create a new archive that contains all the files in the temporary directory. 4. Using the WinZip Self-Extractor, create a self-extracting executable. To enable the command line to run, enter the following: SETUP.EXE replace_ini Now, anyone who runs the executable you created will automatically have the endpoint installed using the endpoint.ini file you customized. To create a file that silently self-installs with a custom endpoint.ini: 1. Double-click the gsendw32.exe file and extract the files to a temporary directory. 2. Edit or replace the endpoint.ini that is now in the temporary directory. 3. Create a custom response file, such as customer.iss. For example, enter SETUP -noinst -r -f1.\customer.iss 4. Using WinZip, create a new archive that contains all the files in the temporary directory. 5. Using the WinZip Self-Extractor, create a self-extracting executable; for the command line to run, enter the following: SETUP.EXE replace_ini -s -f1.\customer.iss Now, anyone who runs the file you created will automatically have the endpoint installed using customer.iss as the response file, and the endpoint.ini file that is installed will be the customized version you created. 6 User Guide

17 Chapter 3 HP-UX This chapter explains the installation, configuration, and operation of the Performance Endpoint software for Hewlett-Packard HP-UX or later. Because of their lack of effective multi-threading support, HP-UX versions 9.0 and earlier are not supported. The NetIQ AppManager ResponseTime for Networks module supports the use of endpoints installed on HP-UX computers. System Requirements The computer on which you install the HP-UX endpoint package has the following system requirements: Requirement HP-UX Compatible network protocol software for RTP, TCP, and UDP Notes Version at minimum, with TCP/IP networking and corresponding networking hardware installed and configured. Version supports IP Multicast. Chapter 3 HP-UX 7

18 Installing the Endpoint Ensure you are logged in as a root user. The commands and parameters discussed in the following procedures are case-sensitive. Use the combination of uppercase and lowercase letters as shown. To install the endpoint: 1. Use the rm command to ensure a clean temporary install directory. This example uses /tmp. 2. Download the endhpxr.tar.z file to the /tmp directory. Note The endpoint filename is endhpxr.tar.z (with a capital Z). However, your Web browser might change the filename to all lowercase. Therefore, when you specify the filename in the Save As dialog box, you should capitalize the Z at that time. 3. Uncompress the endpoint by using the uncompress command: cd /tmp uncompress endhpxr.tar tar -xvf endhpxr.tar 4. From the directory where you downloaded the endpoint, run the endpoint installation script:./endpoint.install 5. You will see the license agreement, presented with the more command. Press the spacebar until the end of the agreement is displayed. You are asked whether you accept the terms and conditions of the agreement. If you do, enter accept_license. 6. The endpoint installs itself in /opt/netiq. During installation, you will see several status messages. Pay close attention to the output. If the installation is successful, you see the following message: Installation of endpoint was successful. If you see the following message, review the entire output from the install script for an explanation of the warnings and further instructions. Notice! There were potential problems with migrating from $oldinstallpath to $installpath. Review the warnings displayed above for further explanation. 7. If you need the disk space after installing the endpoint, you can delete the temporary directory and installation script. The installation script and temporary directory are not removed automatically. To remove the temp files, enter the following: rm -fr temp rm endpoint.install rm endhpxr.tar 8. When installation is complete, see Configuring HP-UX Endpoints on page 10 to ensure your endpoint is ready to be used in ResponseTime monitoring. 8 User Guide

19 Unattended Installation for HP-UX You can install the endpoint silently, that is, without providing additional user input. Complete the steps, as described in Installing the Endpoint on page 8 through the tar command. Next, run the endpoint installation, adding the accept_license parameter:./endpoint.install accept_license What Happens During Installation During installation, the endpoint is installed into the /opt/netiq directory. The directory is created with the following contents: The executable programs The README file Various install and uninstall programs Directory cmpfiles. This directory contains files with the.cmp file extension. These files contain data of different types, such as typical text or binary data. These files are used by the endpoint as data on SEND commands. The different data types can be used to vary the data compression performance of your network hardware and software. File endpoint.ini. For more information, see Endpoint Initialization File on page 3. The installation program stops any copy of the endpoint program that may currently be running and starts a copy of the newly installed endpoint. You can run tests immediately, without a reboot. No changes are made to the PATH environment variable of the root user. Installation also performs the following additional actions: Copies a startup/shutdown script to the /sbin/init.d directory Links the startup/shutdown script to /sbin/rc2.d/s900endpoint. This is invoked by HP-UX when the computer boots up. Links the startup/shutdown script to /sbin/rc1.d/k100endpoint. This is invoked by HP-UX when the computer is shut down. Copies a configuration file to the /sbin/rc.config.d directory. This file should be modified to control whether the endpoint starts when your system boots. By default, the endpoint will start upon reboot. Removing the Endpoint Package To remove the endpoint, enter the following at a command prompt. You must be logged in as root to run this command: /opt/netiq/endpoint.remove The command removes all files from /opt/netiq, except for files added to this directory that were not present at installation, such as the endpoint.ini file, or any other files you may need if you reinstall the product. This command does not remove the /opt/netiq directory. Chapter 3 HP-UX 9

20 Configuring HP-UX Endpoints The endpoint dynamically configures its own programs, so you do not have to update the configuration files for your communications software. However, your communications software must be configured and running correctly. The following steps guide you through this verification. 1. Determine the network addresses of the computers to be used in tests. 2. Verify the network connections. Configuration for TCP/IP The RTP, TCP, and UDP protocols use TCP/IP software for network communications. TCP/IP offers two forms of network addresses: IP addresses and domain names. An IP address is a 32-bit numeric address represented in dotted notation, such as As an alternative, you can use domain names, which are in a format that is easier to recognize and remember. To use domain names, you need either a Domain Name Server (DNS) set up in your network or an /etc/hosts file on each computer. Determining the IP Address Use one of the following methods to determine the IP address of the local computer you are using: From the Hewlett Packard System Administration Manager (SAM) interface, open the Networking/Communications menu and select Network Interface Cards. Enter the following at a command prompt: netstat -in You may have several network interfaces. If you are using a LAN network, for example, look at the output for the lan0 interface. Your local IP address is shown in the Address column. Testing the TCP/IP Connection Ping is a simple utility program, included in all TCP/IP implementations. To check the connection from one computer to another, enter the following at a command prompt: ping xx.xx.xx.xx 64 1 Replace the x s with the IP address of the target computer. If Ping returns a message that says 1 packets transmitted, 1 packets received, 0% packet loss then the Ping worked. Otherwise, there will be a delay, and then you will see 1 packets transmitted, 0 packets received, 100% packet loss This error indicates the Ping failed, and you cannot reach the target computer. Before testing with TCP/IP, ensure you can run Ping successfully from the AppManager console computer to each computer serving as Endpoint 1, and between each pair of endpoints involved in a test. 10 User Guide

21 Sockets Port Number TCP/IP applications use their network address to decide which computer to connect to in a network. They use a sockets port number to decide which application program to connect to within a computer. The TCP/IP sockets port number for endpoints is This port number is used during the initialization of a test. During the actual running of the test, other port numbers are used. If the script specifies port_number=auto on the CONNECT_ACCEPT command, additional ports are dynamically acquired from the protocol stack. Otherwise, the endpoint issuing the CONNECT_ACCEPT commands, usually Endpoint 2, uses the port number specified in the script. Starting an HP-UX Endpoint On HP-UX, the endpoint program starts automatically each time HP-UX is rebooted. Screen output goes to file /var/opt/netiq/endpoint.console. To see any error messages generated at this endpoint, enter the following command: tail -f /var/opt/netiq/endpoint.console Detailed information about the start and stop of each individual connection pair is written to file endpoint.aud. The contents of this file vary depending on how you set the SECURITY_AUDITING keyword in your endpoint.ini file. For more information, see Endpoint Initialization File on page 3. You can manually start the endpoint program at a command prompt. Ensure you are logged in as a root user. To start the endpoint, enter: /opt/netiq/endpoint & The & parameter indicates to HP-UX that the endpoint program should run in the background. The screen output from the endpoint program is interleaved with other UNIX commands. Press Enter to enter more commands. If you manually start the endpoint, consider redirecting its output to the endpoint.console file. You can tell by the time stamp of the file when the endpoint program was started and stopped. If the endpoint program is already running, you get the following message: CHR0183: The endpoint program is already running. Only one copy is allowed at a time. Stopping an HP-UX Endpoint The endpoint program has a special command-line option, -k. To stop an endpoint program, enter the following from a command prompt. You must be logged in as root to run this program. /opt/netiq/endpoint -k The -k command-line option stops all endpoint processes running on that computer. You should see the message Sent exit request to the running endpoint, which indicates the endpoint program has been sent a request to stop. If the request to stop is not handled correctly by the running endpoint program, use the UNIX kill -TERM command. Avoid using kill -9 to stop the running endpoint program. It does not clean up what has been created Chapter 3 HP-UX 11

22 If the endpoint fails, stops abnormally, or encounters assertion conditions, you may need to perform additional cleanup. If the endpoint is still running, try to stop it using the endpoint -k or kill -TERM command. Next, enter the following command: rm /var/opt/netiq/.netiq.endpoint.pid How to Tell Whether an HP-UX Endpoint Is Active You can use a traditional UNIX command to determine whether the endpoint program is active. At a command prompt, enter the following: ps -ef grep endpoint If the endpoint program is running, you will see output similar to the following: root Apr 22? 0:00 /opt/netiq/endpoint Disabling Automatic Startup To disable automatic startup, edit the /etc/rc.config.d/endpoint file so the START_ON_INIT variable is set to 0 (zero). Logging and Messages Most error messages encountered on an endpoint are returned to the AppManager console computer. However, some may be logged to the /var/opt/netiq/endpoint.log file. To view an error log, use the program named FMTLOG. FMTLOG reads from a binary log file, and writes its formatted output to stdout. Here is the syntax of the FMTLOG command: /opt/netiq/fmtlog log_filename >output_filename For example, enter the following to write a readable ASCII version of the error log to a filename myoutput: /opt/netiq/fmtlog /var/opt/netiq/endpoint.log >myoutput The endpoint code performs internal checking on itself. Our software captures details related to the problem in an ASCII text file. Assertion failures are written to the file /var/opt/netiq/assert.err. Save a copy of the file and send it to support@netiq.com for problem determination. CORE and CMA_DUMP.LOG Files NetIQ has seen situations in which the endpoint core dumps on HP-UX. The operating system then creates two files: a file named cma_dump.log written to the /opt/netiq or /tmp directory a file named core written to /opt/netiq. If a core dump occurs, save a copy of the core and cma_dump.log files and return them to support@netiq.com for debugging. 12 User Guide

23 Message CHR0181 You may receive the error message CHR0181 while running a test. If the error was detected at the HP-UX computer, it says the endpoint program on HP-UX has run out of system semaphores. Each instance of Endpoint 1 requires a system semaphore. You can use the HP-UX SAM facility to increase the number of available system semaphores. Use the following procedure and the HP-UX SAM facility to change the kernel configurable parameters: 1. As a root user, start SAM by typing sam. 2. Open the Kernel Configuration menu. 3. Open the Configurable Parameters menu. 4. Update the semmap, semmni, semmns, and semmnu parameters as necessary. After changing the kernel parameters, reboot HP-UX to have the changes take effect. See your HP-UX System Administration Tasks manual for the definitions of these parameters. Messages CHR0174, CHR0204, CHR0210, and CHR0245 You may see one of these error messages if you exceed the soft file limit per process allowed by HP-UX. You can verify this by searching the /var/opt/netiq/endpoint.console file for the following text: %Internal DCE Threads problem (version CMA BL10+), terminating execution. % Reason: cma ts_open: fd is too large % See 'cma_dump.log' for state information. You may need to stop and restart the endpoint program using the methods outlined in Starting an HP- UX Endpoint on page 11 and Stopping an HP-UX Endpoint on page 11. You can use the HP-UX SAM facility to increase the number of open files allowed per process by changing the maxfiles kernel configurable parameters. Chapter 3 HP-UX 13

24 14 User Guide

25 Chapter 4 IBM AIX This chapter explains the installation, configuration, and operation of the Performance Endpoint software for IBM AIX on the RISC System/6000 (RS/6000). The NetIQ AppManager ResponseTime for Networks module supports the use of endpoints installed on HP-UX computers. System Requirements The AIX endpoints have the following system requirements: Requirement IBM AIX on RS/6000 Compatible network protocol software for RTP, TCP, and UDP Notes Version at minimum, with TCP/IP networking and corresponding networking hardware installed and configured. Version supports IP Multicast. Chapter 4 IBM AIX 15

26 Installing the Endpoint Ensure you are logged in as a root user. The commands and parameters discussed here are casesensitive. Use the combination of uppercase and lowercase letters as shown. To install the endpoint: 1. Use the rm command to ensure a clean temporary install directory. Then save the endpoint to that directory. This example uses /tmp. 2. Download the endaixr.tar.z file to the /tmp directory. 3. Uncompress the endpoint file by using the uncompress command: cd /tmp uncompress endaixr.tar tar -xvf endaixr.tar 4. From the directory where you downloaded the endpoint, run the endpoint installation script:./endpoint.install 5. You will see the license agreement, presented with the more command. Press the spacebar until the end of the agreement is shown. 6. You are asked whether you accept the terms and conditions of the agreement. If you do, enter accept_license and press Return. The endpoint installs itself in /usr/lpp/netiq. During installation, you will see several status messages. Pay close attention to the output. If the installation is successful, you see the message Installation of endpoint was successful. If you see the following message, review the entire output from the install script for an explanation of the warnings and further instructions. Notice! There were potential problems with migrating from $oldinstallpath to $installpath. Review the warnings displayed above for further explanation. If you need the disk space after installing the endpoint, delete the temporary directory and installation script. The installation script and temporary directory are not removed automatically. To remove the temp files, enter: rm -fr temp rm endpoint.install rm endaixr.tar For more information, see Configuring AIX Endpoints on page User Guide

27 Unattended Installation for AIX You can install the AIX endpoint silently, that is, without providing any additional user input. Complete the steps, as described in Installing the Endpoint on page 16 through the tar command. Next, run the endpoint installation, adding the accept_license parameter:./endpoint.install accept_license What Happens During Installation During installation, the endpoint is installed into the /usr/lpp/netiq directory. A directory is created with the following contents: The executable programs The README file Various install and uninstall programs Directory cmpfiles. This directory contains files with the.cmp file extension. These are files containing data of different types, such as typical text or binary data. These files are used by the endpoint as data on SEND commands. The different data types can be used to vary the data compression performance of your network hardware and software. File endpoint.ini. For more information, see Endpoint Initialization File on page 3. The installation program stops any copy of the endpoint program that may currently be running and starts a copy of the newly installed endpoint. You can run tests immediately, without a reboot. The endpoint software performs the following tasks so the endpoint is started every time your system boots: Copies the rc.netiq initialization script to the /etc directory. Updates /etc/inittab to invoke /etc/rc.netiq No changes are made to the PATH environment variable of the root user. Removing the Endpoint Package Use the following command to remove the endpoint. You must be logged in as root to run this program: /usr/lpp/netiq/endpoint.remove The remove program removes the files from /usr/lpp/netiq, except for any files added to this directory that were not present at installation, such as the endpoint.ini file, and does not delete the directory. The remove program does not automatically delete files that have been added to the directory that you may need if you reinstall the product. Chapter 4 IBM AIX 17

28 Configuring AIX Endpoints The endpoint dynamically configures its own programs, so you do not have to update the configuration files for your communications software. However, your communications software must be configured and running correctly. The following steps guide you through this verification. 1. Determine the network addresses of the computers to be used in tests. 2. Verify the network connections. Configuration for TCP/IP The RTP, TCP, and UDP protocols use TCP/IP software for network communications. TCP/IP offers two forms of network addresses: IP addresses and domain names. An IP address is a 32-bit numeric address. It is represented in dotted notation, such as As an alternative, use domain names, which are in a format that is easier to recognize and remember. To use domain names, you need either a Domain Name Server (DNS) set up in your network or an /etc/hosts file on each computer. Determining the IP Address Use one of the following methods to determine the IP address of the local computer you are using: For the IBM System Management Interface Tool (SMIT), open the Communications Applications and Services menu, then the TCP/IP menu, and then the Minimum Configuration & Startup menu. Next, select the network interface used to reach other endpoints (for example, en0 or tr0). SMIT displays the network interface configuration. Your host IP address is in the Internet ADDRESS field. Enter the following at a command prompt: netstat -in You may have several network interfaces. If you are using a LAN network, for example, look at the output for the en0 interface. Your local IP address is shown in the Address column. Testing the TCP/IP Connection Ping is a simple utility program, included in all TCP/IP implementations. To test the connection from one computer to another, enter the following at a command prompt: ping xx.xx.xx.xx 64 1 Replace the x s with the IP address of the target computer. If Ping returns a message that says 1 packets transmitted, 1 packets received, 0% packet loss, the Ping worked. Otherwise, there will be a delay, and then you will see the following message: 1 packets transmitted, 0 packets received, 100% packet loss This error message indicates the Ping failed, and you cannot reach the target computer. Ensure you can run Ping successfully from the AppManager console computer to each computer serving as Endpoint 1, and between each pair of endpoints involved in a test, before starting your testing with TCP/IP. 18 User Guide

29 Sockets Port Number TCP/IP applications use their network address to decide which computer to connect to in a network. They use a Sockets port number to decide which application program to connect to within a computer. The TCP/IP sockets port number for endpoints is This port number is used during the initialization of a test. During the actual running of the test, other port numbers are used. Starting an AIX Endpoint The endpoint program starts automatically each time AIX is rebooted. It sends its screen output to file /var/adm/endpoint.console. To see any error messages generated at this endpoint, enter the following command: tail -f /var/adm/endpoint.console The detailed information about the start and stop of each individual connection pair is written to file endpoint.aud. The contents of this file vary depending on how you set the SECURITY_AUDITING keyword in your endpoint.ini file. For more information, see Endpoint Initialization File on page 3. Instead of automatic startup, you can choose to manually start the endpoint program at a command prompt. Ensure you are logged in as a root user. To start the endpoint, enter the following: /usr/lpp/netiq/endpoint & The & parameter indicates to AIX the endpoint program should run in the background. The screen output from the endpoint program is interleaved with other UNIX commands. Just press Return to enter more commands. If you manually start the endpoint, consider redirecting its output to the endpoint.console file. You can tell by the time stamp of the file when the endpoint program was started and stopped. If the endpoint program is already running, you get the following message: CHR0183: The endpoint program is already running. Only one copy is allowed at a time. Stopping an AIX Endpoint The endpoint program has a special command-line option, -k. To stop an endpoint program, enter the following command from a command prompt. You must be logged in as root to run this program: /usr/lpp/netiq/endpoint -k The -k command stops any endpoint process running on that computer. You should see the message Sent exit request to the running endpoint, which indicates the endpoint program has been sent a request to stop. If the request to stop is not handled correctly by the running endpoint program, use the UNIX kill -TERM command. If the endpoint fails, stops abnormally, or encounters assertion conditions, you may need to perform additional cleanup. If the endpoint is still running, try to stop it using the endpoint -k or kill -TERM command. Next, enter the following command: rm /var/adm/.netiq.endpoint.pid Chapter 4 IBM AIX 19

30 How to Tell Whether an AIX Endpoint Is Active You can use a traditional UNIX command to determine whether the endpoint program is active. At a command prompt, enter: ps -ef grep endpoint If the endpoint program is running, you will see output similar to the following: root :19:54-0:00 /usr/lpp/netiq/endpoint -G T 3 root :37:47-0:00 /usr/lpp/netiq/endpoint Disabling Automatic Startup To disable automatic startup, comment out or remove the following lines from the /etc/rc.netiq script: if test -f $installpath/endpoint; then echo "Starting the NetIQ Endpoint." $installpath/endpoint 1>$outputPath/endpoint console 2>&1 & fi Logging and Messages Although most error messages encountered on an endpoint are returned to the AppManager console, some may be logged to disk. Errors are saved in a file named endpoint.log, in the /var/adm directory. To view an error log, use the program named FMTLOG. FMTLOG reads from a binary log file, and writes its formatted output to stdout. Use the following FMTLOG command: /usr/lpp/netiq/fmtlog /var/adm/endpoint.log >output_filename The endpoint code performs a lot of internal checking on itself. Our software captures details related to the problem in an ASCII text file named assert.err in the /var/adm directory. Save a copy of the file and send it to us via for problem determination. You may receive message CHR0181 while running a test. If the error was detected at the AIX computer, it says the endpoint program on AIX has run out of system semaphores. Each instance of Endpoint 1 requires a system semaphore. The maximum number of semaphores is not configurable on AIX. It is hard-coded to a large value (4096). To avoid this problem, stop other programs that use semaphores, or decrease the number of connection pairs that use the AIX computer as Endpoint User Guide

31 Chapter 5 Linux This chapter explains the installation, configuration, and operation of the Performance Endpoint software for Linux. The Linux endpoints run on the following Linux platforms: Red Hat Linux for x64 and x86 processors. Versions 6.1 and later ship with a current version of the Performance Endpoint. SUSE Linux for x64 and x86 processors Cobalt Web Server RaQ3 for x86 processors Other Linux systems that incorporate the Linux kernel 2.0 (or later) with threading support on x86 processors, such as Caldera Systems. For Linux endpoints, there are three types of installation procedures. The basic procedure uses TAR files, which should be used for Slackware and Linux systems other than Red Hat or Cobalt. The following NetIQ products support the use of endpoints installed on all supported Linux platforms: AppManager ResponseTime for Networks module AppManager for VoIP Quality module Vivinet Assessor Vivinet Diagnostics Chapter 5 Linux 21

32 System Requirements The Linux endpoints have the following system requirements: Requirement Notes A computer capable of running Linux For Cobalt servers: the RaQ3 system, which uses an Intel x86 processor, gives good performance For x64 computers: AMD Opeteron 64-bit systems or Intel Xeon 64-bit systems For x86 computers: a CPU such as an Intel 80386, 80486, a member of the Pentium family, or equivalent. A Pentium or better is recommended. Linux kernel 2.0. with support for pthreads, which is at least version of glibc Compatible network protocol software for RTP, TCP, and UDP TCP/IP networking and corresponding networking hardware must be installed and configured, plus ELF support. Some older installations of Linux may not have this installed. At the Web site, you can find information about Linux, as well as download the glibc-2.0 file. The endpoint installation procedures check for this file, because it is required to run the endpoint. NetIQ has tested with Red Hat (kernel ). Red Hat 5.0 or later is required for IP Multicast. Red Hat 8.0 or later is required for IPv6. NetIQ has also tested with Slackware 3.6. Installing the RPM-Based Endpoint for Linux Use the RPM-based (x86 processor) installation if you are installing the endpoint on Red Hat Linux. Ensure you are logged in as a root user. The commands and parameters discussed here are casesensitive. Use the combination of uppercase and lowercase letters as shown in the following procedure. To install the endpoint: 1. Use the rm command to ensure a clean temporary install directory (this example uses /tmp). 2. Save the endlnxr.rpm file to the /tmp directory. 3. Use the RPM command to install the endpoint: cd /tmp rpm -Uvh endlnxr.rpm During installation, you will see several status messages. When the installation is successful, you see the message Installation of endpoint was successful. If you see the following message, review the entire output from the install script for an explanation of the warnings and further instructions. Notice! There were potential problems with migrating from $oldinstallpath to $installpath. Review the warnings displayed above for further explanation. After you complete installation, see Configuring Linux Endpoints on page 26 to ensure your endpoint is ready to be used in testing and monitoring. 22 User Guide

33 Removing the RPM Endpoint Package Use the following command to remove the endpoint. You must be logged in as root to run this program: rpm -e endpoint The command removes all files from /usr/local/netiq, except for files added to the directory that were not present at installation, such as the endpoint.ini file. This command does not delete the directory. The command does not automatically delete files added to the directory that you may need if you reinstall the product. If anything goes wrong during the process of uninstalling the endpoint, a reinstalled endpoint may not run. You may need to do some extra cleanup. Check for the hidden file /usr/local/netiq/.netiq.endpoint.pid. You can use the ls -a command to view hidden files. Then enter the following command to delete it: rm /usr/local/netiq/.netiq.endpoint.pid Installing the Cobalt-Based Endpoint for Linux Use the Cobalt installation to install the endpoint for x86 (RaQ3) on a Cobalt Web server. Some prerequisite levels of Cobalt software are needed to operate the Performance Endpoint on a Cobalt Web server. Typically, when you install an endpoint, you can automatically upgrade from the previous version of the endpoint. However, when you upgrade the endpoint on a Cobalt RaQ3 (x86) computer, you must remove the previous version of the endpoint, following the directions in Removing the Cobalt Endpoint Package on page 24. Then install the new version of the endpoint. If you attempt to install Endpoint 5.1 without removing a previous version, you get a message stating, Error uninstalling RPM. This message indicates the upgrade failed. To install the endpoint: 1. Use the rm command to ensure a clean temporary install directory (this example uses /tmp). 2. Save the file appropriate for your operating system to the /tmp directory. 3. Access the Welcome to Cobalt page on the Cobalt Web Server and click the link for the RaQ Server Management section. 4. Enter the username and password for the Administrator. 5. On the Server Management dialog box, click Maintenance and then click Install Software. 6. In the Software to install field, enter the location of the package. If you are using the Browse function, ensure the filename and extension are in lowercase. /tmp/endcbl3.pkg 7. If prompted, enter the password for the Administrator. Chapter 5 Linux 23