HP HP-UX IPQos Administrator's Guide

HP-UX IPQoS A.01.00

Administrator’s Guide

HP-UX 11i v1 and

HP-UX 11i v2 (September 2004 or later)

Manufacturing Part Number: 5991-0736

October 2005

Printed in the US

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.

U.S. Government License

Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright © 1997-2005 Hewlett-Packard Development Company L.P. All rights reserved. Reproduction, adaptation, or translation of this document without prior written permission is prohibited, except as allowed under the copyright laws.

Trademark Notices

UNIX is a registered trademark in the United States and other countries, licensed exclusively through The Open Group.

1. Introduction

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Benefits of HP-UX IPQoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

DiffServ Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

HP-UX IPQoS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

HP-UX IPQoS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Planning for HP-UX IPQoS Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

General Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

HP-UX Host Specific Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2. Installing HP-UX IPQoS

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Supported Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Disk Space Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Patch Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Acquiring HP-UX IPQoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Installing HP-UX IPQoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Initial Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Update Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Verifying the HP-UX IPQoS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Removing HP-UX IPQoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Contents

3. Getting Started with HP-UX IPQoS

HP-UX IPQoS Deployment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

HP-UX IPQoS Deployment Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

HP-UX IPQoS Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

ipqosadmin Administration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

System Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

HP-UX IPQoS Operating States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Start and Stop Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Starting HP-UX IPQoS - Without a Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Stopping HP-UX IPQoS - Without a Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Contents

4. HP-UX IPQoS Configuration Files

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Configuration File Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Syntax Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Creating an HP-UX IPQoS Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Filter Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Filter Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Policy Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Policy Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Adapter Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Adapter Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

5. Administering HP-UX IPQoS

ipqosadmin Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

ipqosadmin Options and Administrative Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

ipqosadmin Usage Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Administering HP-UX IPQoS Operating States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Using ipqosadmin to Change States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Disabling/Re-Enabling HP-UX IPQoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Displaying State Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Verifying a Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Loading a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Unloading a Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Showing Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Showing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Setting and Showing Log Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

6. Troubleshooting HP-UX IPQoS

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Troubleshooting Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

HP-UX IPQoS ipqosadmin Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

HP-UX System and Networking Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Troubleshooting Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Installation Scenario: HP-UX IPQoS Installation Fails . . . . . . . . . . . . . . . . . . . . . . 104

HP-UX IPQoS Configuration File Verification Fails. . . . . . . . . . . . . . . . . . . . . . . . . 104

Active Configuration Is Not As Expected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

State Is Not As Expected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Traffic Management Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Corrupt or Missing HP-UX IPQoS Configuration File . . . . . . . . . . . . . . . . . . . . . . . 107

Internal Error from Corrupt or Missing HP-UX IPQoS Database File. . . . . . . . . . 108

Sample Error and Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Reporting Problems to HP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Contents

A. HP-UX IPQoS Configuration File Attributes: Quick Reference

Summary of Configuration File Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

B. HP-UX IPQoS Configuration File Examples

Example 1: Premium Services Class Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Contents

Example 2: Trusted Applications and DSCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Example 3: Packets Can Match Multiple Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Example 4: Limit ftp Bandwidth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

C. ipqosadmin Quick Reference

ipqosadmin Usage Syntax Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

ipqosadmin Syntax Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Tables

Table 1. Publishing History Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Table 2. HP-UX 11i Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Table 3. HP-UX IPQoS - Relevant RFCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Table 3-1. HP-UX IPQoS Operating States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Table 4-1. Supported Transport Protocol Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Table 4-2. Supported Network Protocol Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Table 6-1. Getting Information with ipqosadmin. . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Table 6-2. Sample Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Table 6-3. Sample Warning and Informational Messages . . . . . . . . . . . . . . . . . . . . .110

Table A-1. Filter Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

Table A-2. Policy Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Table A-3. Adapter Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Table C-1. ipqosadmin Syntax Quick Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . .127

Tables

Figures

Figure 1-1. Traffic Classification and Conditioning Flow in HP-UX IPQoS. . . . . . . .22

Figure 1-2. Architectural Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Figures

About This Document

This document describes how to install, configure, administer, and troubleshoot HP-UX IPQoS.

The document printing date and part number indicate the document’s 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 document part number will change when extensive changes are made.

Document updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, subscribe to the appropriate product support service. Contact your HP sales representative for details.

The latest version of this document can be found online at: http://www.docs.hp.com/en/netcom.html#IPQoS.

Intended Audience

This document is intended for system and network administrators responsible for installing, configuring, and managing HP-UX IPQoS. Administrators are expected to have knowledge of HP-UX and networking concepts, commands and configuration, including knowledge of Transmission Control Protocol/Internet Protocol (TCP/IP).

This document is not a tutorial.

New and Changed Documentation in This Edition

This is the first edition of this document.

Publishing History

Table 1 Publishing History Details

Document

Manufacturing

Part Number

5991-0736 HP-UX IPQoS A.01.00

Administrator’s Guide

Title

Operating Systems

Supported

HP-UX 11i v1 HP-UX 11i v2 (September 2004 or later)

Publication

Date

October 2005

What Is in This Document

HP-UX IPQoS A.01.00 Administrator’s Guide is divided into several chapters, and each contains information about installing, configuring, managing, or troubleshooting HP-UX IPQoS.

Chapter 1 Introduction Use this chapter to obtain a summary and an overview of

HP-UX IPQoS features.

Chapter 2 Installing HP-UX IPQoS Use this chapter to learn the system

requirements and procedures necessary to install HP-UX IPQoS.

Chapter 3 Getting Started with HP-UX IPQoS Use this chapter to obtain a

summary of tasks, commands and files associated with using HP-UX IPQoS.

Chapter 4 HP-UX IPQoS Configuration Files Use this chapter to learn the details

of creating HP-UX IPQoS configuration files.

Chapter 5 Administering HP-UX IPQoS Use this chapter to learn about common

tasks involved in administering HP-UX IPQoS.

Chapter 6 Troubleshooting HP-UX IPQoS Use this chapter to learn techniques for

troubleshooting HP-UX IPQoS, what to do for common problems, and how to report problems to HP.

Appendix A HP-UX IPQoS Configuration File Attributes Quick Reference Use

this appendix as a quick reference of configuration file syntax specifics.

Appendix B HP-UX IPQoS Configuration File Examples Use this appendix to view

sample configuration files.

Appendix C ipqosadmin Quick Reference Use this appendix as a quick reference of

ipqosadmin syntax specifics.

Glossary Glossary Use the glossary to obtain definitions for commonly used terms

related to HP-UX IPQoS.

Typographic Conventions

This document uses the following conventions. audit (5) An HP-UX manpage. In this example, audit is the name and 5 is the section

in the HP-UX Reference. On the web and on the Instant Information CD, it may be a hot link to the manpage itself. From the HP-UX command line, you can enter “man audit” or “man 5 audit” to view the manpage.

Book Title The title of a book. On the web and on the Instant Information CD, it may be

a hot link to the book itself.

KeyCap The name of a keyboard key. Note that Return and Enter both refer to the

same key.

Emphasis Text that is emphasized.

Bold Text that is strongly emphasized. Bold The defined use of an important word or phrase.

ComputerOut Text displayed by the computer.

UserInput Commands and other text that you type.

Command A command name or qualified command phrase.

Variable The name of a variable that you may replace in a command or function or

information in a display that represents several possible values. | Separates items in a list of choices. [] The contents are optional in formats and command descriptions. If the

contents are a list separated by |, you must choose one of the items. {} The contents are required in formats and command descriptions. If the

contents are a list separated by |, you must choose one of the items. ... The preceding element may be repeated an arbitrary number of times.

HP-UX Release Name and Release Identifier

Each HP-UX 11i release has an associated release name and release identifier. The uname (1) command with the -r option returns the release identifier. This table shows the releases available for HP-UX 11i.

Table 2 HP-UX 11i Releases

Release

Identifier

B.11.23 HP-UX 11i v2 Intel Itanium and PA-RISC

B.11.22 HP-UX 11i v1.6 Intel Itanium

B.11.11 HP-UX 11i v1 PA-RISC

Release Name

Supported Processor

Architecture

1 Introduction

This chapter introduces and describes HP-UX IPQoS functionality. It provides a brief overview of the DiffServ model HP-UX IPQoS uses to accomplish Quality of Service (QoS). It addresses the following topics:

Chapter 1 17

Introduction

• “Overview” on page 19

• “HP-UX IPQoS Features” on page 25

• “HP-UX IPQoS Architecture” on page 27

• “Planning for HP-UX IPQoS Deployment” on page 29

Chapter 118

Introduction

Overview

Given current technology trends, it is increasingly important to have a means available to deal with network traffic issues. HP-UX IPQoS helps businesses meet an increasing demand for the ability to control networking throughput, and to ensure network resources are optimally managed.

To support specific business requirements, the Internet Engineering Task Force (IETF) acknowledged the need for a method of providing differentiated classes of service for Internet traffic. The Differentiated Services Working Group of the IETF defined the Differentiated Services (DiffServ or DS) model. HP-UX IPQoS software provides IETF DiffServ-compliant network quality of service controls for IP-based network communications.

For outbound traffic on HP-UX hosts, HP-UX IPQoS provides traffic conditioning (transmission prioritization for specified traffic classes), Differentiated Services Code Point (DSCP) marking, and VLAN-priority marking. HP-UX IPQoS uses a configuration that has been loaded into the kernel, and that contains user-supplied definitions of traffic classes (filters) and traffic-handling instructions (policies) assigned to configured adapters.

HP-UX IPQoS provides an important host-based component of a larger network traffic management solution. HP-UX IPQoS hosts work with DS-aware routers to provide differentiated services on the network.

IMPORTANT The span of control for HP-UX IPQoS is for an individual HP-UX host, and for

outbound traffic only. Although the IETF DiffServ model takes a holistic network-wide view, HP-UX

IPQoS is configured on a single host, not globally on a network-wide basis. This is consistent with the single-system administration model used with HP-UX systems.

Benefits of HP-UX IPQoS

The DiffServ model allows for IP Quality of Service (IPQoS) distinctions to be applied to various groupings of network traffic. IP QoS provides controls that enable you to give defined traffic classes differentiated service.

The following factors contributed to the problems that IPQoS solves:

Chapter 1 19

Introduction

Overview

• Over the last several years there have been unprecedented increases in network traffic. In

part, this is due to the explosive increases in Internet usage. It is also partly a result of the tremendous increase in multimedia and wireless applications (applications extremely susceptible to limits in bandwidth and network capacity).

• Traditional uses of the network now compete with mission critical applications. Thus

there is a greater need for guaranteed communication during unexpected situations, such as natural disasters and other major emergencies.

• By default, IP networks merely provide “best effort” service to all traffic types. Just

keeping the network up and running is insufficient, because some traffic requires higher performance.

• Overprovisioning expands and upgrades infrastructure equipment capacity. This

approach tries to keep ahead of peak usage, rather than strategically addressing typical usage. It can be prohibitively expensive, because the capital investments needed to keep congestion and queueing delays within reasonable limits during peak times are much higher than those needed to keep up with average use.

Using DiffServ-compliant nodes (hosts and routers) is an important traffic engineering technique that helps address these and other problems.

HP-UX IPQoS can help the network support business objectives, while helping minimize the cost of managing network resources. It helps keep network costs down by using bandwidth more efficiently and by eliminating the need for overprovisioning as a result of expanding the usefulness of the existing infrastructure.

HP-UX IPQoS features can help Internet Service Providers (ISPs) and Application Service Providers (ASPs) offer differentiated levels of network service to customers. Individual organizations can use HP-UX IPQoS features to prioritize internal traffic.

DiffServ Mechanisms

Generally speaking, IP QoS can be achieved through any mechanism that delivers better than best effort service to network traffic. The DiffServ model provides IP QoS in networks by using a defined set of building blocks to build a variety of aggregate behaviors. HP-UX IPQoS provides controls that enable you to give defined traffic classes differentiated service. It does this by following specified bandwidth and marking characteristics.

The DiffServ architectural components include traffic classification and traffic conditioning.

Chapter 120

Introduction

Overview

Traffic Classification

Traffic classification filters packets in a traffic stream into distinct classes (groups) based on the content of parts of the packet header. In the classification process, IP packets are matched against selectors of each filter to determine if the packet belongs in that filter class. Traffic classifiers separate and steer traffic classes to traffic conditioners for further processing.

Two types of classifiers are defined in the DiffServ model. The Behavior Aggregate (BA) Classifier selects packets based on the DSCP only. The Multi-Field (MF) classifier selects packets based on the values of a combination of header fields such as source address, destination address, and transport port numbers. HP-UX IPQoS provides BA and MF classification.

Traffic Conditioning

Traffic conditioning consists of one or more of the following actions: Metering Metering is part of the flow control strategy. Flow control measures traffic

flow for a class, then releases packets onto the network at a specified rate.

The metering component ensures conformance to configured flow rates.

Metering measures the traffic stream against a traffic profile specified via

policies in HP-UX IPQoS. It tracks the transmission rate of traffic flows on a

per-class basis. It then compares the actual flow rate against configured

flow rates, and passes state information to other conditioning functions to

trigger a specific action for each packet.

With HP-UX IPQoS, you can reserve a percentage of the total available

bandwidth; you can also specify a maximum bandwidth. See “Policy

Attributes” on page 71 for more information. Marking Marking marks packets with values that translate to forwarding behaviors.

Marking is the basis for potential differentiated treatment when the packet

reaches a resource that recognizes the marking, such as a DS-aware router.

Forwarding behavior determines the priority and drop precedence of traffic

about to be forwarded on the network. This can involve marking or

re-marking the DS field of an IP packet with a DS codepoint (DSCP) value.

It can also involve marking or re-marking the VLAN tag of an Ethernet

frame header with a Class of Service (CoS) priority value.

After a value is placed in the packet header, the packet forwarding behavior

is determined by the forwarding scheme used by DS-aware nodes in the

network. For example, different traffic classes can be steered to use

different routes such as reserved-traffic-only links and usage-based-billing

links. The steering depends on forwarding rules set in the DS-aware

Chapter 1 21

Introduction

Overview

routers, and VLAN priority markings for VLAN-aware switches. You must

assign DS and VLAN priority marking values in accordance with your

forwarding scheme.

In HP-UX IPQoS, both DS fields and VLAN tags can be marked. Policing Policing (dropping) may drop some packets to bring a traffic stream into

compliance with a traffic profile specified via policies. Policing is a subset of

shaping.

In HP-UX IPQoS, policing actions are triggered by metering results that

indicate action is warranted. Shaping Shaping enables the delay of some or all of the packets in a traffic stream to

bring the stream into compliance with a traffic profile. Usually a finite

buffer is used, and in some cases packets are dropped if there is insufficient

buffer space to hold delayed packets.

In HP-UX IPQoS, shaping actions are triggered by metering results that

indicate action is warranted.

Figure 1-1 Traffic Classification and Conditioning Flow in HP-UX IPQoS

Figure 1-1 displays the flow of traffic classification and conditioning components applicable to HP-UX IPQoS. As illustrated, outbound packets under HP-UX IPQoS control may pass through only the marking path, only the metering path or through both paths, depending on the specifics of the active configuration. The components shown in Figure 1-1 act as follows:

Chapter 122

Introduction

Overview

— The classifier selects a packet in a traffic stream based the content of a part of the packet

header. In HP-UX IPQoS, classification is based on filter attributes specified in the active HP-UX IPQoS configuration.

— The meter checks compliance to a defined traffic profile and passes results to

shaper/policer to trigger appropriate actions for in- and out-of-profile packets. In HP-UX IPQoS, metering is based on policy attributes specified in the active HP-UX IPQoS configuration.

— The marker can write/rewrite the DSCP and VLAN priority values. In HP-UX IPQoS,

marking is based on policy attributes specified in the active HP-UX IPQoS configuration.

— The shaper delays (and the policer drops) some packets, so that traffic maintains

compliance with a defined traffic profile. In HP-UX IPQoS, shaping actions result from maintaining accordance with metering specifications in the active HP-UX IPQoS configuration. HP-UX IPQoS does not perform shaping based on marking characteristics. Other nodes, such as DS-aware routers, may perform shaping as a result of marking specifications.

DSCP Marking

Each IP packet has a DS field. For IPv4, this is the leftmost 6-bits of the TOS field; for IPv6, this is the leftmost 6-bits of the Traffic Class field. The DS field can be used to mark a packet so that it receives a particular forwarding behavior. The DiffServ model defines a set of commonly used standard DSCP’s and their corresponding forwarding behaviors. The forwarding behavior assigned to a DSCP is referred to as the per-hop behavior (PHB). The PHB defines the forwarding precedence a packet receives in relation to other traffic on a DiffServ-enabled network.

A common agreement about the use and interpretation of the possible values used in the DS field is needed for interdomain use, multivendor interoperability, and overall consistency of expected aggregate behaviors in a network. The IETF Differentiated Services Working Group has standardized a common layout for the six-bit field of these octets. For more information, refer to RFC 2474 Definition of the Differentiated Service Field (DS Field) in the IPv4 and IPv6 Headers and RFC 2475 An Architecture for Differentiated Services, which define the architecture and the general use of the bits within the DS field.

You can select a DSCP value from a group of well-known codepoints associated with the two key forwarding types defined in the DiffServ model. The PHB types are Expedited Forwarding (EF) for higher priority traffic, and Assisted Forwarding (AF) for other traffic. The well-known codepoints, which would appear in the leftmost 6-bits of the TOS or Traffic Class fields, are 46 (101110) for the EF PHB, and a range of codepoints for the AF PHB. For more information, refer to RFC 2597 Assured Forwarding PHB Group and RFC 2598 An Expedited Forwarding PHB.

Chapter 1 23

Introduction

Overview

Router and Host Behaviors with DSCP Marking An IP QoS-capable system, such as an HP-UX IPQoS host, marks the field with a DSCP value. A DS-aware router then applies the appropriate forwarding behavior associated with the DSCP value to the packet.

The DSCP is used for prioritizing transmission bandwidth. For example, when a router becomes congested, it uses the DSCP values of queued packets to decide which ones to drop, if necessary.

Routers can also use the DSCP to re-create the VLAN priority tag. Routers at the boundaries between administrative domains, such as between ISPs, can convert tags to different values. Minimally, the values roughly correspond to the same values in the other domain.

Unlike VLAN tags, DSCP markers do not add to the traffic, because the DSCP marker is carried in an existing field of the IP packet.

Summary

In the DiffServ model, each traffic-generating source cooperates in two ways. The first is traffic conditioning. Traffic conditioning reduces load peaks and consequent

queueing delays. It assures that when the source node generates data faster than the adapter can send it, the most important traffic goes out first. HP-UX IPQoS policies use the reservation bandwidth and maximum allowed bandwidth policy attributes to help with this “send now or later” type of bandwidth management.

The second is marking, where sources place a VLAN or DSCP priority tag in their packets so that infrastructure equipment can decide which packets should be sent first and which should be dropped first.

Transmission priority (reserved and maximum bandwidth allocation) is of limited use as a control. Since the transmission priority isn’t carried with the packet, its usefulness ends at the first router. VLAN marking propagates through the first-hop switch. Marking the DS field, which is carried in the packet, can have wider significance.

Chapter 124

HP-UX IPQoS Features

HP-UX IPQoS A.01.00 provides the following features:

• Conforms to the IETF DiffServ model

HP-UX IPQoS brings an HP-UX host into conformance to the IETF DiffServ model. HP-UX IPQoS cooperates with QoS policies and policy management as configured in edge and core routers, and which can also be configured in the switching infrastructure.

— Provides differentiated classes of service on outbound traffic by performing traffic

conditioning actions. Important traffic classes can take bandwidth away from less important classes, up to user-specified limits.

❏ Classification occurs when traffic classes are defined in filters. ❏ Marking occurs when marking attributes are set in policies. ❏ Metering occurs when bandwidth is reserved for defined traffic classes in policies.

— Allows DSCP and VLAN marking on outbound traffic from the HP-UX server.

Introduction

❏ Can assign different DSCP network routing priorities (valid range 0-63). ❏ Can assigned different VLAN priorities (valid range 0-7).

IMPORTANT Conformance of HP-UX IPQoS to the IETF DiffServ model applies only to

outbound traffic on an HP-UX host.

• Supports traffic classification on broad range of packet attributes

HP-UX IPQoS supports traffic classification with any combination of the following packet attributes: IP source or destination address or address ranges (numerically or by host name); transport port numbers or range (numerically or by service name; can specify source, destination, or both); transport protocol number (only tcp or udp are currently supported); network protocol number (Ethertype); DSCP value; and destination physical (MAC) address.

• Provides provisioned QoS management

With provisioned QoS, network resources are statically configured in anticipation of traffic that will flow through them. Most QoS mechanisms in network devices and computing systems use provisioned QoS; for example, priority queues, rate controls, and packet marking. With signaled QoS, applications or the operating system dynamically signal network devices in an attempt to reserve resources on them.

Chapter 1 25

Introduction

HP-UX IPQoS Features

HP-UX IPQoS provides provisioned QoS only. Signaled QoS is not supported.

• Supports both IPv4 and IPv6

HP-UX IPQoS can filter on IPv4 and IPv6 addresses. (For IPv6 addresses to be meaningful, you must to be running on an IPv6-enabled system.)

• Provides a simple configuration file format

HP-UX IPQoS configuration files are in text format and use a simple syntax. They can be created and maintained using any common HP-UX text editor, such as vi.

• Provides a single simple utility for all administrative tasks

HP-UX IPQoS provides one inclusive command-line utility, ipqosadmin, for managing administrative tasks related to using HP-UX IPQoS. This utility can verify, load, and unload a configuration; and show state, active configuration, and statistical information.

• Provides an API for (optional) programmatic HP-UX IPQoS control

Optionally, you can use the HP-UX IPQoS API to configure and manage HP-UX IPQoS. For more information on the HP-UX IPQoS API, refer to the HP-UX IPQoS A.01.00 Programmer’s Guide.

• Provides statistics for configured adapters, policies, and filters

HP-UX IPQoS can display current statistics on all active adapters, policies, and filters. or on specific adapters, policies, and filters, using the command-line utility, ipqosadmin. You can also reset statistics using ipqosadmin.

• No changes to existing applications are required

No changes are needed to existing applications. You can immediately realize the benefits of HP-UX IPQoS without any recoding, recompiling, or patching.

• Compatible with HP-UX IPSec

HP-UX IPQoS is compatible with HP-UX IPSec. HP-UX IPQoS can classify traffic by transport port numbers when used with the IPSec Authentication Header (AH). However, HP-UX IPQoS cannot classify traffic by transport port number when used with the IPSec Encapsulating Security Payload (ESP), because the ESP protocol encrypts the IP payload. HP-UX IPQoS can classify other filter attributes that are in the IP layer or below (such as IP address), independent of HP-UX IPSec encryption mechanisms.

• IEEE802.3ad (Auto Port-aggregation) compatible

HP-UX IPQoS is IEEE802.3ad and IEEE802.3 compatible.

Chapter 126

HP-UX IPQoS Architecture

Figure 1-2 displays a high-level overview of the HP-UX IPQoS architecture.

Figure 1-2 Architectural Overview

Introduction

As shown in Figure 1-2, HP-UX IPQoS operates in both user space and kernel space. Also shown in Figure 1-2, HP-UX IPQoS inserts a module between the IP and the DLPI layers, into the STREAMS plumbed by ifconfig. To insert this module:

• HP-UX 11i v1: HP-UX IPQoS uses the autopush mechanism.

Chapter 1 27

Introduction

HP-UX IPQoS Architecture

• HP-UX 11i v2: HP-UX IPQoS uses the INTERFACE_MODULES list in the

/etc/rc.config.d/netconf and /etc/rc.config.d/netconf-ipv6 files.

HP-UX IPQoS supports as many network adapters as are configured on the system (up to

128).

Chapter 128

Introduction

Planning for HP-UX IPQoS Deployment

Before you begin using HP-UX IPQoS, you must plan your implementation. The following sections discuss a high-level planning overview, general planning considerations including network-wide considerations, and HP-UX host specific planning considerations.

Overview

You need to begin by understanding the current traffic on your network. As part of your network traffic analysis, determine where the traffic bottlenecks are, when they happen, and what are the largest contributors. There is a general rule that assumes you will identify the “knee of the curve”. In other words, there is often an inflection point where the steepness of the curve changes significantly. Before the knee, incremental traffic leads to incremental delays, whereas after the knee of the curve, incremental traffic leads to significant increased delays.

Once you have identified where the worst bottlenecks are, define policies and filters that give priority to essential traffic, and limit the rest. The more detail you gather, the more specifically you can define the filters and policies.

In general, use a common sense approach to managing your network traffic. Analyze your network thoroughly before making changes. Start with a simple filter and policy, so that analysis can be done easily. Take measurements and determine if you are getting intended results without unintended consequences. If so, you can continue to expand the filters and policies to achieve your traffic management goals.

NOTE A detailed network-wide QoS planning strategy discussion is beyond the scope

of this guide.

General Planning Considerations

Implementing HP-UX IPQoS as part of your overall QoS strategy is an iterative process. As part of your preparation and to determine how HP-UX IPQoS fits into your larger QoS (DS-aware) network, you must take several planning steps, including the following:

• Analyze your organization’s needs and goals. Break them down into manageable sizes.

Prioritize them. Define the results needed to happen to meet specific goals.

Chapter 1 29

Introduction

Planning for HP-UX IPQoS Deployment

As part of this analysis, you must understand the current factors preventing your organization from achieving its network performance goals. Then you can better understand how to use HP-UX IPQoS policies to achieve improvements in network performance.

• Assess your network traffic. Analyze the baseline data on both your overall network as

well as on your HP-UX hosts. Understand the typical traffic patterns and bottlenecks in the network, including

determining which traffic is most sensitive to congestion. Measure response times for critical applications, determine the bottlenecks in response time or performance, and look at the mix of traffic. Gather data over a long enough time period to show the effects of the cyclical realities of your environment. Prioritize among the various types of traffic in the network.

• Review your network topology so that you can plan a strategy for using IP QoS-enabled

systems and DS-aware routers. Determine the network resources available for QoS management. Determine if you have the types of devices (hosts and routers) and the capacity on the network to carry out the actions required to meet your business goals.

Decide which systems will be IP QoS-enabled and which routers will be DS-aware. Minimally, you will need at least one IP QoS-enabled system and at least one DS-aware router. If your local router is not DS-aware, then it will pass marked packets on to the next hop without evaluating the DSCP marks. For each DS-aware component, you must plan an IP QoS strategy and map it into policies.

As part of identifying specific resources for IP QoS deployment follow these steps:

1. Determine key connector devices and locate frequently used paths.

2. Know the resources that are the bottlenecks in these paths.

3. Know which adapters (NICs) on these resources you must specifically apply IP QoS mechanisms to.

4. Isolate parts of the network that cause problems or need to be managed.

HP-UX Host Specific Planning Considerations

After examining network wide considerations, analyze HP-UX host specific considerations to help you plan your HP-UX IPQoS implementation.

• Review, classify, and prioritize the outbound traffic HP-UX hosts generate. Determine any groups into which outbound HP-UX host traffic can be divided. Organize these groups into differentiated classes of service by determining appropriate classification, metering and marking behaviors that can then be translated to filter and policy specifications.

Chapter 130

+ 105 hidden pages