HP WebQoS Setup and Install
Configuring HP WebQoS on HP-UX
Edition 3
Manufacturing Part Number: B8311-90004
E0900
U.S.A.
© Copyright 2000, Hewlett-Packard Company. .
Legal Notices
The information in this document is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited
to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall
not be held liable for errors contained herein or direct, indirect, special, incidental or consequential
damages in connection with the furnishing, performance, or use of this material.
Warranty. A copy of the specific warranty terms applicable to your Hewlett- Packard product and
replacement parts can be obtained from your local Sales and Service Office.
Restricted Rights Legend. Use, duplication or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013.
HEWLETT-PACKARD COMPANY
3000 Hanover Street
Palo Alto, California 94304 U.S.A.
Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR
52.227-19(c)(1,2).
Copyright Notices. ©copyright 1999-00 Hewlett-Packard Company.
©copyright 1979, 1980, 1983, 1985-93 Regents of the University of California
This software is based in part on the Fourth Berkeley Software Distribution under license from the
Regents of the University of California.
©copyright 1980, 1984, 1986 Novell, Inc.
©copyright 1986-1992 Sun Microsystems, Inc.
©copyright 1985-86, 1988 Massachusetts Institute of Technology.
©copyright 1989-93 The Open Software Foundation, Inc.
©copyright 1986 Digital Equipment Corporation.
©copyright 1990 Motorola, Inc.
©copyright 1990, 1991, 1992 Cornell University
©copyright 1989-1991 The University of Maryland
©copyright 1988 Carnegie Mellon University
Trademark Notices. UNIX® is a registered trademark of the Open Group.
X Window System is a trademark of the Massachusetts Institute of Technology.
OSF/Motif is a trademark of the Open Software Foundation in the U.S. and other countries.
Java™ is a U.S. trademark of Sun Microsystems, Inc.
Netscape and Netscape Navigator are U.S. trademarks of Netscape Communications Corporation.
MS-DOS®, Microsoft®, Windows®, and Windows NT® are U.S. registered trademarks of Microsoft
Corporation.
2
1. Understanding HP WebQoS
The Role and Benefits of HP WebQoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
WebQoS Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Request Classifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Capacity Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Policy Based Service Level Objectives (SLOs) and Thresholds . . . . . . . . . . . . . . . 15
How WebQoS Fits Into Your Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
WebQoS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Request and Management Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2. Installing HP WebQoS
3. Configuring HP WebQoS
Modifying Configuration Files Before Start-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Enabling Network Type of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
The IN_TOS Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
The OUT_TOS Flag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Modifying WebQoS Global Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
SCA and Web Server Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
SCA Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
SCO Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Denial of Service Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Logging and Tracing Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
URL Encoding Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Configuring Your Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Zeus Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Configuring Zeus Web Server Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
IP-Based Virtual Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Subservers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Improving Web Server Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
iPlanet Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Running the WebQoS setup Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Running setup -r. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Configuring WebQoS from the Management User Interface. . . . . . . . . . . . . . . . . . . . . 40
Starting the WebQoS Management User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Understanding the Management User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Contents
3
Contents
Adding a System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Adding a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
To Configure Service Statistics Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
To Configure Service Level Objectives for the Service . . . . . . . . . . . . . . . . . . . . . . 49
To Specify Service-Wide Corrective Actions for SLOs. . . . . . . . . . . . . . . . . . . . . . . 52
Modifying Service-Wide Corrective Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Adding a Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
To Identify the Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
To Identify the Web Server for the Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Prioritizing Requests to the Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Setting Site Service Level Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
To Specify Corrective Actions for Site SLOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Adding Site Threshold Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
To Specify Corrective Actions for Threshold Policies . . . . . . . . . . . . . . . . . . . . . . . 72
Configuring Advanced Features for the Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Modifying Session Timeouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Assigning Web Server Request Queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Modifying Web Server Accept Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Specifying Site-Wide Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Enabling Site Statistics Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Verifying Your Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4. Using HP WebQoS
Navigating the Services/Systems View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Editing a System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Editing a Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
To Edit the Site Type and Service Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
To Edit the Site’s Request Classification Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
To Edit the Site’s SLOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
To Edit a Site’s Threshold Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
To Edit Session Timeouts, Request Queues, Accept Threads, and Corrective Actions.
90
To Apply Your Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Copying a System or Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Deleting a System, Service, or Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Monitoring SLOs and the History Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4
Contents
Understanding the Service Level Objectives View. . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Understanding the History Log View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Filtering SLOs and Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Filtering the History Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Displaying Site Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Viewing SLO Related Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Viewing Site Session Control Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Displaying Service Performance Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Viewing Service SLO Related Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Viewing Service Session Control Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Viewing Defer Related Statistics for the Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Changing the Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Connecting to Another Management Station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Shared Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Error Messages Viewable From the Management User Interface. . . . . . . . . . . . . . 115
Error Messages Viewable From the Terminal Window . . . . . . . . . . . . . . . . . . . . . . 117
Logging and Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Measurement Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Statistics Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Changing Logging and Tracing Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
5. Customizing and Using HP OpenView with HP WebQoS
Installing, Configuring, and Using HP OpenView Service Reporter . . . . . . . . . . . . . 123
Installing and Configuring the WebQoS System . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Installing and Configuring the Service Reporter System. . . . . . . . . . . . . . . . . . . . . 125
Viewing WebQoS Reports in Service Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Installing, Configuring and Using PerfView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Logging WebQoS Site Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Logging WebQoS Service Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Viewing Graphs in PerfView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Installing and Configuring HP OpenView IT/Operations . . . . . . . . . . . . . . . . . . . . . . 132
Installing the Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Getting a Quick Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Customizing the ITO Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Managing the WebQoS System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5
Contents
Troubleshooting WebQoS Processes on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
If Problems Occur But There Are No Error Messages . . . . . . . . . . . . . . . . . . . . . 138
6. Installing and Using HP LocalDirector Controller
What is HP LocalDirector Controller? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Installing HP LocalDirector Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Installing the Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Configuring Cisco LocalDirector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Configuring HP LocalDirector Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Configuring the HP LDControl Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Configuring the HP LDControl Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Starting and Stopping the HP LDControl Daemon . . . . . . . . . . . . . . . . . . . . . . . . . 148
Configuring a System with More than One LAN Card . . . . . . . . . . . . . . . . . . . . . . 149
Troubleshooting the HP LD Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
General Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
HP LDControl Cannot Find Cisco’s LocalDirector . . . . . . . . . . . . . . . . . . . . . . . . 149
Problems Accessing the HP LD Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
HP LDControl Daemon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Problems with HP LocalDirector Controller and Cisco LocalDirector . . . . . . . . . . 152
A. Policy and Rule Descriptions
Request Classification Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Policies Set in WebQoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Service Level Objectives for Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Service Level Objectives for the Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Threshold Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Corrective Actions for SLO and Threshold Policy Violations. . . . . . . . . . . . . . . . . . 161
Customizing the Reject and Defer Web Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
B. HP OpenView IT/Operations (ITO) Alarms
IT/Operations Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
ITO Alarms Based on WebQoS Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
ITO Alarms Based on WebQoS Process Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . 170
ITO Alarms Based on WebQoS Statistic Crossing a Threshold. . . . . . . . . . . . . . . . 171
WebQoS Statistic Variable Names for ITO Threshold Templates. . . . . . . . . . . . . . . . 173
6
Contents
7
Contents
8
Printing History
The manual printing date and part number indicate its current edition.
The printing date will change when a new edition is printed. Minor
changes may be made at reprint without changing the printing date. The
manual part number will change when extensive changes are made.
Manual updates may be issued between editions to correct errors or
document product changes. To ensure that you receive the updated or
new editions, you should subscribe to the appropriate product support
service. See your HP sales representative for details.
Second Edition: March 2000 (HP-UX 11)
Third Edition: September 2000 (HP-UX 11)
9
10
1 Understanding HP WebQoS
This chapter explains the roles and benefits of HP WebQoS and how it
fits into your environment. It also describes fundamental WebQoS
concepts to help you understand how WebQoS technology works.
Chapter 1 11
Understanding HP WebQoS
The Role and Benefits of HP WebQoS
The Role and Benefits of HP WebQoS
HP WebQoS is an enhancement to the HP-UX operating environment
that stabilizes, optimizes, and prioritizes Internet-related applications
and transactions that run on HP 9000 Enterprise servers. HP WebQoS
works with web-enabled applications built on top of the iPlanet Web
Server1 version 4.1 or the Zeus Web Server2 version 3.3.6.
HP WebQoS enables you to use your resources efficiently to deliver
predictable and differentiated service levels for your web-based
applications, based on the type of customer or transaction. It allows you
to determine these service levels based on business policies.
Although the Internet represents significant opportunities for expanding
your business, the following risks may hamper your ability to deliver
web-based services to customers and partners reliably:
• Unpredictable and possibly fluctuating demand for services.
Because the Internet offers instantaneous access to your site,
promotional, seasonal, or current events may instigate sudden and
immediate interest in your services. Although the additional interest
and business may be welcome, your server may not be able to handle
the load if significant numbers of clients come all at one time. Or if
you are a service provider hosting multiple sites on one server, you
should make sure that the demands of one site do not restrict use by
other sites on the same server.
• Heavier than expected system processing per user request.
The actual workloads exhibited by each visitor to your site may not
align with the workload models you generated during the capacity
planning stage. Perhaps users are performing far more searches than
you anticipated or are spending a lot more time performing compute
intensive operations while at your site.
• All requests are treated the same.
During overload conditions, all user requests and all transactions are
impacted. Even your most important customers who are trying to
access their accounts to make purchases,or sales representatives who
1. The iPlanet Web Server is a product of Sun Microsystems, Inc.
2. The Zeus WebServer is a product of Zeus Technology.
Chapter 112
Understanding HP WebQoS
The Role and Benefits of HP WebQoS
are trying to make a sale at the end of the month, are at the mercy of
Web surfers.
Each of the above conditions can cause increased load at your site or may
impede your ability to deliver your services at optimum levels.
By configuring WebQoS based on the type of services offered and traffic
experienced at your site, you ensure that important web-based
transactions are handled optimally in order to maximize revenue and
customer satisfaction.
Key capabilities and benefits of WebQoS for HP-UX 9000, Series 800
customers allow you to do the following:
• Stabilize the system during server overload situations.
When the server is at capacity, WebQoS works to alleviate the load
and improve the performance. For more information, refer to
“Capacity Protection” on page 14.
• Prioritize client requests to the server system.
WebQoS allows you to provide differentiating service to different
types of client requests by prioritizing requests submitted to the site.
For more information, refer to “Request Classifications” on page 14.
• Establish rules for the classification of service requests from users.
WebQoS fulfills high priority service requests with optimum
performance while lower priority service requests are handled in
accordance with your instructions. For more information, refer to
“Request Classifications” on page 14.
WebQoS Concepts
The following are fundamental WebQoS concepts and capabilities.
Understanding these concepts is necessary before you can understand
how WebQoS technology works.
Service
A service refers to something of value that a business is offering to other
businesses or consumers. For example, a business may provide email,
messaging, documentation publishing, cataloging, and Electronic
Commerce services. A WebQoS service is a way to logically group web
sites related to a business application that you offer to customers or
partners.
Chapter 1 13
Understanding HP WebQoS
The Role and Benefits of HP WebQoS
Request Classifications
Request classifications determine access priority for requests submitted
to a web site. They enable you to give preferential treatment to your
most important customers or transactions, allowing you to meet formal
or informal service-level agreements.
WebQoS request classifications differentiate requests as they enter the
server system by dividing requests into categories based on application,
client or destination IP addresses, destination port number, and URL
document paths. High request classifications have higher priority access
to the server.
WebQoS supports three request classifications: high, medium, and low.
During periods of heavy system load, low priority requests may possibly
be redirected or rejected. If a request is accepted, it is scheduled based on
its request classification priority. Based on your configured policies, the
request might be immediately processed, or it may wait in the queue
while other higher priority requests are processed first.
Sessions
A session is composed of one or more requests to a web site from the
same user. These requests may arrive over one, or over several
connections. Once a session has been granted, a user's remaining
requests are guaranteed to be forwarded to the web server, unless the
session times out.
Under periods of heavy system load, new sessions may not be granted.
This is controlled by the WebQoS policies. When new sessions are
rejected, redirected, or deferred, existing sessions continue
uninterrupted. User request prioritization and session management are
the primary tools used by WebQoS to provide Capacity Protection. The
network manager is responsible for updating the timers that define a
session, and for establishing the policies that control whether the session
is admitted.
Capacity Protection
Capacity Protection prevents system overload with load balancing and
admission control. This minimizes the impact of unexpected surges in
demand while maximizing the volume of completed transactions.
Capacity Protection makes sure that performance levels for active
customers and their currently running transactions are not
compromised. New user requests are not admitted to a site unless their
Chapter 114
Understanding HP WebQoS
The Role and Benefits of HP WebQoS
transactions can be completed quickly.
With Capacity Protection, you configure a system when it is functioning
at peak levels to do the following:
• Redirect high priority customers to another system with available
capacity.
• Defer high priority customers for a few moments until current
sessions are completed.
• Reject low priority customers in extreme overload conditions.
Policy Based Service Level Objectives (SLOs) and Thresholds
To ensure that your business policies are reflected in your Web
applications, they need to be translated into service level objectives
(SLOs) and thresholds. SLOs are business-oriented policies and
thresholds are operations-oriented policies.
Business-oriented service level objectives define the following:
• Response time—measured from the time a request enters the server
to the time it leaves the server.
• Concurrent session capacity—created when an initial request is
accepted and maintained until the session times out.
Operations-oriented thresholds for capacity protection determine the
following:
• Average CPU load—measured on the local system.
• Queue depth—the maximum number of service requests waiting that
are not yet forwarded to the web server.
The administrator defines SLOs, thresholds,and their relative priorities.
WebQoS can trade off meeting policies based on these priorities.
Information Technology rules concerning response time, throughput,
availability, and priorities for request classification rules and
applications are translated into SLOs and thresholds.
The administrator also configures corrective actions that are executed
when the rules are violated. Corrective actions are a list of prioritized
actions an administrator uses to help bring the SLO or threshold into
compliance with the rule.
Chapter 1 15
Understanding HP WebQoS
How WebQoS Fits Into Your Environment
How WebQoS Fits Into Your Environment
WebQoS, which includes a set of extensions to HP-UX, works with your
web server and application servers for all of your web-enabled
applications. Refer to Figure 1-1, "WebQoS in Your Environment".
Figure 1-1 WebQoS in Your Environment
To ensure acceptable web-based interactions between you and your
customers, all parts of your web environment (client, network, web
server, and application server which includes an application) must work
together efficiently and effectively. The network alone cannot deliver
acceptable service levels if the server is creating delays due to excessive
demand or component failures. The server alone cannot deliver
acceptable service levels if the network is exhibiting bottlenecks.
The following describes briefly the function of each part of the
environment:
• The client identifies itself and initiates requests.
• The network distinguishes class priorities and routes priority packets
efficiently while delivering best effort service to lower priority
packets.
• The web server distinguishes WebQoS request priorities and
manipulates operating system scheduling policies and resource
management policies to ensure high priority service requests are
processed quickly.
• The application server contains an application with the processing
rules that enables service requests to be classified and handled by the
server and network.
Chapter 116
WebQoS Components
WebQoS comprises a number of components that perform priority-based
resource management and service request handling. (See Table 1-1,
“WebQoSComponents.”)In addition, management components allow you
to configure WebQoS for the systems on which it is installed as well as
define the service level objectives (SLOs) and threshold policies that are
important to your business. (For an explanation of SLOs, refer to
“Service Level Objectives for Site” on page 158.)
Note that not all components are required on every WebQoS-enabled
system. Refer to Figure 1-2, "Request and Management Data Flow", to
understand how these components fit into the WebQoS picture.
Table 1-1 WebQoS Components
Component Installed On Description
Understanding HP WebQoS
How WebQoS Fits Into Your Environment
Management User
Interface
WebQoS
Management Server
or Service Control
Operator (SCO)
Any Windows
NT/95/98
system. Can be
installed on
multiple PCs.
Mustreside onat
least one system
in the WebQoS
domain.
Any HP-UX
Enterprise
Server running
HP-UX 11.x.
Must reside on
only one system.
Allows you to configure WebQoS-enabled
systems, including identification of those
systems, websites and applications that
make up a particular service offering. Also
lets you define performance objectives for the
components of the service. Enables you to
monitor performance levels and service level
objectives (SLOs).
Manages the WebQoS configuration and
communicates with the management user
interface. Sends out management control
directives to the Service Control Agents
(SCAs) and receives status from them.
Chapter 1 17
Understanding HP WebQoS
How WebQoS Fits Into Your Environment
Table 1-1 WebQoS Components
Component Installed On Description
WebQoS Services or
Service Control
Agent (SCA) and
WebQoS Request
Control
Any HP-UX
Enterprise
Server running
on HP-UX 11.x
and running a
web server that
is managed by
WebQoS.
Collects performance information from the
Service Resource Controller and WebQoS
request control. Receives management
control directives from the Service Control
Operator. Distributes configuration
information to WebQoS nodes. The SCA
monitors operation information and gives
feedback to the SCO. This information is
displayed by the management user interface.
This component includes the following
sub-components:
Session Manager—creates sessions and
tracks activity within a session until it
expires.
Classifier—examines attributes of a service
request to determine the appropriate request
classification assignment for the request.
Admission Controller—monitors system load
and response time in order to decide whether
or not new sessions are accepted.
Scheduler—submits service requests to the
web server based on each request's assigned
request classification priority.
Class Encoder/Decoder—encodes and
decodes the request classification priority for
requests and responses into network packet
headers so that network devices can handle
these accordingly.
Chapter 118
How WebQoS Fits Into Your Environment
Request and Management Data Flow
In this example, you are running a web server system that is accessible
by various clients through a browser. The system may be running
multiple web server processes, each of which may be hosting different
web sites that are assigned to different process groups. By assigning
these sites to different process groups, you cause them to exhibit
different performance characteristics. If you assign your most important
website to the high priority process group, it receives majority access to
shared system resources. Also, by assigning different priorities for each
web server, you can give different performance levels to different user
requests or to different actions.
Figure 1-2 Request and Management Data Flow
Understanding HP WebQoS
Chapter 1 19
Understanding HP WebQoS
How WebQoS Fits Into Your Environment
Chapter 120
2 Installing HP WebQoS
Information about installing, upgrading, and removing this product can
be found in the HP WebQoS Premium for HP-UX Release Note.
Chapter 2 21
Installing HP WebQoS
Chapter 222
3 Configuring HP WebQoS
This chapter describes how to modify the WebQoS configuration files. It
also describes the management user interface and how to use it.
Chapter 3 23
Configuring HP WebQoS
Figure 3-1 WebQoS Administrator’s Task Flow
Chapter 324
Configuring HP WebQoS
The steps below are explained in detail in the sections following.
1. Modify configuration files from the command line before starting
WebQoS.
2. Configure your web server.
3. Run the WebQoS setup script to start the WebQoS SCO.
4. Start the WebQoS management user interface. The WebQoS SCO
must be started prior to starting the management user interface.
5. Use the management user interface to configure one or more systems.
A system is a computer with web sites and application servers
managed by WebQoS.
6. Use the management user interface to configure one or more services.
A service is a way to logically group web sites that are related to the
same business application. You can view logical groups of web sites as
a single entity in the management user interface and you can set a
service level objective for the service that allows you to put limits on
the number of concurrent sessions.
7. Use the management user interface to configure one or more sites. A
site is a web server instance that is managed by WebQoS. When you
configure a site, you do the following:
• Connect the site logically to a previously configured service so you
can view grouped sites belonging to that service in the
management user interface.
• Specify the system and port number which identify the site. The
system must already be configured in WebQoS. You can look at all
the sites on a system in the management user interface.
• Prioritize requests to the site with request classification rules.
• Define response time and capacity objectives and policies for the
site.
• Set service level objectives for the site.
8. Use the management user interface to edit your site(s).
9. Configure necessary files from the command line after configuration
is completed from the management user interface.
Chapter 3 25
Configuring HP WebQoS
Modifying Configuration Files Before Start-Up
Modifying Configuration Files Before
Start-Up
The following files can be modified from the command line before
starting WebQoS:
• /etc/opt/webqos/net_tos.conf (See “Enabling Network Type of
Service” below.
• /etc/opt/webqos/qos.conf (See “Modifying WebQoS Global
Configuration” on page 27.)
Enabling Network Type of Service
Enabling network type of service (TOS) allows classification rules to be
reflected in network traffic priorities. Please check with your network
equipment provider if TOS encoding is supported.
If you would like to enable network TOS, you must modify the following
configuration file: /etc/opt/webqos/net_tos.conf.
Modify this file before you start up WebQoS. The file contains two flags,
IN_TOS and OUT_TOS, which tell WebQoS how to interpret and set the
TOS byte in the IP headers of incoming and outgoing requests.
The IN_TOS Flag
The IN_TOS flag tells WebQoS how to interpret the TOS values of
requests coming into WebQoS from your clients. If you have configured
your networking devices (for example routers or switches) to set the TOS
byte, and you want WebQoS to classify incoming requests based on that
value rather than other request classification rules (for example IP
address, URL, or port number), you should set this flag to TRUE. Then
configure the expected value ranges for each request classification. Next,
you configure your request classification rules to enable network QoS.
Refer to “Setting Site Service Level Objectives”.
The OUT_TOS Flag
The OUT_TOS flag tells WebQoS how to set the TOS values for outgoing
responses back to the client. If your network devices are configured to
interpret these settings, you can signal these network devices to ensure
Chapter 326
Configuring HP WebQoS
Modifying Configuration Files Before Start-Up
your requests receive the appropriate priority across the network.
Specific instructions to enable network TOS are included in the
/etc/opt/webqos/net_tos.conf file.
Modifying WebQoS Global Configuration
To modify your WebQoS global configuration, you need to modify the
/etc/opt/webqos/qos.conf configuration file.
You should do this before you run the WebQoS setup script. If you
update this file after running the setup script, the web server must be
restarted for any changes to take effect. However, logging and tracing
parameters can be changed dynamically and take effect when a site is
edited.
The following parameters can be set:
SCA and Web Server Parameters
The following parameters affect the SCA and web server. If you change
any of these parameters, you must restart the SCA and web server.
• HTTPVersion - Default: HTTP/1.1
• KeepDeferringAfterMaxDeferTime - No default
Defer users when the maximum defer time is reached. Set this
parameter to TRUE to continue deferring users.Set this parameter to
FALSE to reject users when the maximum defer time is reached.
• MeasurementInterval - Default: 30 seconds
How often, in seconds, WebQoS collects performance measurements.
The MeasurementInterval must be an even multiple of the
MonitorInterval. The minimum value is 5 seconds.
If Site Statistics Logging is enabled in the management user
interface, this parameter also specifies the interval at which the SCA
generates site statistics.
• MonitorCPUWeight - Default: 20%
Percentageof the current CPU utilization (pstat is used to determine
current CPU utilization) used to calculate the weighted CPU
utilization. The weighted CPU utilization is based on the current and
previous (last measured) CPU utilization:
Chapter 3 27
Configuring HP WebQoS
Modifying Configuration Files Before Start-Up
weighted CPU% = (MonitorCPUWeight% * current CPU) +
[(100 - MonitorCPUWeight)% * previous CPU]
For example, if you set the MonitorCPUWeight to 20, the current
CPU utilization is 60, and the previous CPU utilization is 50, the
weighted CPU utilization is (20% * 60) + [(100 - 20)% * 50] or 52%.
If you want to monitor the current CPU utilization only, set this
parameter to 100.
The MonitorInterval parameter determines how often the weighted
CPU utilization is calculated (default is every 5 seconds).
If you modify MonitorCPUWeight, you must restart the SCA and your
web server.
• MonitorInterval - Default: 5 seconds
How often, in seconds, threshold policies are monitored. The
minimum value is 5 seconds. If you change the value, you must
restart the web server.
• MonitorResponseTimeWeight - Default: 50%
Percentage of the current response time used to calculate the
weighted response time. The weighted response time is based on the
current and previous (last measured) response time:
weighted response = (MonitorResponseTimeWeight% * current
response time) + [(100 - MonitorResponseTimeWeight)% * previous
response time]
For example, if you set the MonitorResponseTimeWeight to 20, the
current response time is 3 seconds, and the previous response time is
2 seconds, the weighted response time is (20% * 3) + [(100 - 20)% * 2]
or 2.2 seconds.
If you want to monitor the current response time only, set this
parameter to 100.
The MonitorInterval parameter determines how often the weighted
response time is calculated (default is every 5 seconds).
• NumOfDeferredSessionsPerMinute - No default
The number of sessions that can be deferred per minute. If the value
is greater than 60, then the parameter
NumOfDeferredSessionsPerSecond automatically increases.
• NumOfDeferredSessionsPerSecond - Default: 1
Chapter 328
Configuring HP WebQoS
Modifying Configuration Files Before Start-Up
The number of deferred sessions that have the same deferral time
allocated to them. Minimum deferral time is 10 seconds; maximum is
120 seconds.
Forexample, if you set this parameter to 1 and two requests arrive at
the same time, the first deferred session is allocated a deferral time of
10 seconds and the second deferred session is allocated a deferral
time of 11 seconds. If you set the parameter to 2 and two requests
arrive at the same time, the first deferred session is allocated a
deferral time of 10 seconds and the second also is allocated a deferral
time of 10 seconds.
SCA Parameters
The following parameters affect the SCA only. If you change any of these
parameters, you must restart the SCA.
• LogInterval - Default: 30 minutes
How often, in minutes, WebQoS logs measurements to a
measurement log file located in the directory
/var/opt/webqos/measures. The LogOn parameter must be enabled
(set to 1) before WebQoS logs measurements to the log file. The
minimum value is 1 minute.
• LogOn - Default: 0 (disabled)
Enable or disable measurement logging. To enable measurement
logging, set this parameter to 1. To disable measurement logging, set
this parameter to 0.
WebQoS creates a new measurement log file daily for each WebQoS
site and places it in the directory /var/opt/webqos/measures. The
measurement log file name is the site name you entered in the
management user interface followed by the date. The log file contains
performance measurements collected during the day for the site.
The measurements logged include:
— Average response time for each request class
— Number of new, redirected, deferred, and rejected sessions foreach
request class
— Average and maximum queue lengths
• SaveFiles - Default: 0 (disabled)
Chapter 3 29
Configuring HP WebQoS
Modifying Configuration Files Before Start-Up
Enable or disable saving measurement log files (located in the
directory /var/opt/webqos/measures). If enabled, all measurement
log files are saved. If disabled, measurement log files more than two
days old are deleted.
SCO Parameters
The following parameters affect the SCO only. If you change any of these
parameters, you must restart the SCO.
• SCOLogInterval - Default: 5 minutes
How often, in minutes, WebQoS logs aggregate service statistics to a
service statistics log file located in the directory
/var/opt/webqos/stats). Service statistics logging must be enabled
using the management user interface before aggregate service
statistics are logged. Values range from 5 to 30 minutes. See “To
Configure Service Statistics Logging” on page 47 for a list of the
logged aggregate statistics.
• SCOLogSROn - Default: 0 (disabled)
Enable or disable logging to HP OpenView MeasureWare. You can
view the statistics logged using the HP OpenView Service Reporter.
Service statistics logging must be enabled using the management
user interface before statistics are logged.
To enable logging, set this parameter to 1. To disable logging, set this
parameter to 0.
• ServiceSLOInterval - Default: 30 seconds
How often, in seconds, the SCO requests the site SLO status from the
SCA.
Denial of Service Parameters
The following parameters can be set to protect your web server from
denial of service attacks.
Connections with No Data Configure the following parameters to
protect your web server against excessive connections that contain no
data.
• MaxPollDescriptors - Default: 50% of the total number of file
descriptors available for each process defined by the maxfiles kernel
parameter. For example, if the maxfiles kernel parameter is 4096,
Chapter 330
Loading...