• No results found

IBM. Tivoli. Netcool Performance Manager. Cisco Class-Based QoS Technology Pack. User Guide. Document Revision R2E1

N/A
N/A
Protected

Academic year: 2021

Share "IBM. Tivoli. Netcool Performance Manager. Cisco Class-Based QoS Technology Pack. User Guide. Document Revision R2E1"

Copied!
64
0
0

Loading.... (view fulltext now)

Full text

(1)

IBM

Netcool Performance Manager

Tivoli

Document Revision R2E1

Cisco Class-Based QoS 2.2.0.0 Technology Pack

User Guide

(2)
(3)

Chapter 1: Introduction

. . . 1

Audience . . . 1

Organization . . . 1

Chapter 2: Devices and services

. . . 5

Overview . . . 5

Summary of device technology . . . 5

Supported MIBs . . . 5

Review of the Modular CB QoS CLI. . . 6

Traffic Class . . . 7

Match Statement . . . 7

Service Policy . . . 8

QoS Actions . . . 8

Review of the CISCO-CLASS-BASED-QOS-MIB . . . 9

Policy and Object Tables . . . 9

Configuration Tables . . . 12

Performance Tables . . . 15

Chapter 3: Supported reports and KPIs

. . . 21

Overview . . . 21

Reporter sets . . . 21

Reporter set tree . . . 22

Reporter set contents . . . 23

Key performance indicators . . . 41

Chapter 4: Configuring the technology pack

. . . 43

Overview . . . 43

Before you begin. . . 43

Configure the technology pack . . . 44

Verifying resources . . . 46

Losing Indexes After Device Reboots. . . 47

Customizing Discovery Results . . . 47

(4)

cbqos_object_id_mv.pl . . . 48

Notices

. . . .49

(5)

This manual describes the IBM® Tivoli® Netcool® Performance Manager Cisco CBQoS Technology Pack. Specifically, the manual describes the reports that display information about the devices and technologies that operate in the Cisco Class-Based QoS environment.

Audience

The audiences for this manual are the network administration engineers at IBM customer sites who will install, configure, and use the Cisco CBQoS Technology Pack as part of their Tivoli Netcool Performance Manager installation. IBM Professional Services engineers may also find this manual useful.

To install and use the Cisco CBQoS Technology Pack, you should have a working knowledge of the following subjects:

• Tivoli Netcool Performance Manager DataMart

• TCP/IP networks

• Telecommunications network management

• Administration of the operating system

The audiences should also be familiar with the specific technology that the Cisco CBQoS Technology Pack deals with, in this case Cisco Class-Based QoS.

Organization

This guide is organized as follows: • Chapter 1, Introduction

Provides a general introduction to the Tivoli Netcool Performance Manager product suite. • Chapter 2, Devices and services

Provides an overview of the device technology supported by the technology pack. • Chapter 3, Supported reports and KPIs

Provides information about the reporter sets and key performance indicators (KPIs) that the Cisco CBQoS Technology Pack provides for each device operating in the Cisco Class-Based QoS environment.

Chapter 4, Configuring the technology pack

Describes how to configure the Cisco CBQoS Technology Pack.

The Tivoli Netcool Performance Manager product suite

IBM Tivoli Netcool Performance Manager consists of two main components: a wireline component (formerly Tivoli Netcool/Proviso) and a wireless component (formerly Tivoli Netcool Performance Manager for Wireless). The Tivoli Netcool Performance Manager wireline component is made up of the following modules:

(6)

Tivoli Netcool Performance Manager DataMart is a set of management, configuration and

troubleshooting GUIs that the Tivoli Netcool Performance Manager system administrator uses to define policies and configuration, as well as to verify and troubleshoot operations.

Tivoli Netcool Performance Manager DataLoad provides flexible, distributed data collection and data import of SNMP and non-SNMP data to a centralized database.

Tivoli Netcool Performance Manager DataChannel aggregates the data collected through Tivoli Netcool Performance Manager DataLoad for use by the Tivoli Netcool Performance Manager DataView reporting functions. It also processes on-line calculations and detects real-time threshold violations. • Tivoli Netcool Performance Manager DataView is a reliable application server for on-demand,

web-based network reports.

Tivoli Netcool Performance Manager Technology Packs extend the Tivoli Netcool Performance Manager system with service-ready reports for network operations, business development, and customer viewing.

Figure 1 shows the different Tivoli Netcool Performance Manager modules. Figure 1: Tivoli Netcool Performance Manager modules

Tivoli Netcool Performance Manager documentation

IBM provides the following Tivoli Netcool Performance Manager documentation:

• Release notes

• Configuration recommendations

• User guides

(7)
(8)
(9)

This chapter discusses the following topics:

Overview

This chapter provides a summary of the Cisco Class-Based QoS device technology, and the associated Management Information Bases (MIBs), that the Cisco CBQoS Technology Pack is designed to support.

Summary of device technology

Cisco provides a capability called Modular Quality of Service (QoS) in its IOS, which lets you configure the QoS functionality of a router. The Modular QoS Command Line Interface (CLI) enables a user to configure various classes of traffic types and actions for the classified traffic.

This is an SNMP pack that will gather metrics based on the CISCO-CLASS-BASED-QOS-MIB file. This MIB is the source of all the metrics reported in this technology pack.

The Class Based QoS (CB-QoS) MIB reports metrics that correspond to the classes and actions configured with the CLI. The Cisco CBQoS Technology Pack collects and reports performance metrics gathered from this MIB. This will provide the user with the ability to collect statistics for the class defined under the policy.

Supported MIBs

The Cisco CBQoS Technology Pack collects performance and accounting data using an SNMP collection model. This technology pack requires read-only access to the SNMP Agents associated with the Cisco Class-Based QoS devices that provide SNMP Agent support.

The Cisco CBQoS Technology Pack uses the following MIBs to collect performance and accounting related statistics:

• CISCO-CLASS-BASED-QOS-MIB

Topic Page

Overview 5 Summary of device technology 5

Supported MIBs 5

Review of the Modular CB QoS CLI 6

(10)

• CISCO-SMI • CISCO-TC • IANAifType-MIB • rfc1213-MIB-II • rfc1155 • rfc1315-FRAME • rfc1902-SNMPv2-SMI • rfc1903-SNMPv2-TC • rfc1907-SNMPv2-MIB

Review of the Modular CB QoS CLI

To work with the Cisco CBQoS Technology Pack, you need a basic understanding of Cisco’s Modular CB QoS CLI (Modular Class-Based Quality of Service Command Line Interface). This section provides an overview of this CLI.

Note: This overview does not explain how to configure Modular QoS on a router. For in-depth information about Cisco’s Modular QoS, see the Cisco documentation.

As documented in the Cisco document, Modular Quality of Service Command Line Interface Overview, configure Modular QoS by:

1. Defining a traffic class, using the class-map command.

2. Creating a service policy that associates the traffic class with one or more policies using the policy-map

command.

3. Attaching the service policy to an interface, using the service-policy command.

The configuration of Modular QoS involves the definitions of policies, classes, match statements, and actions and establishing the relationships among them.

This section provides a high-level overview of the following components that make up the configuration of Modular QoS using the Modular CB QoS CLI:

The Traffic Class or Class-Map definition — This is a name, a set of match statements, and a rule for how to apply these rules. Classes can be hierarchically defined. You can define a class in terms of other classes, which enables a user to establish a mix of match-any and match-all rules for a single class. • Match Statements — These are the different ways that traffic can be mapped to a class.

Service Policies — These map Classes to QoS Management actions. A service policy maps the class name to a set of actions. More than one service policy can use the same class to define policies. For example, the same class might be managed differently at different interfaces and therefore more than one policy is needed. • Actions — These are the various QoS traffic management actions that are possible.

Attaching a Service Policy to an Interface — A service policy must be applied to an interface and traffic direction for it to actually affect traffic. The same service policy can be applied to more than one interface. You apply service policies using the service-policy command, which is a special type of CLI action.

Note: You can create a fairly rich and complex set of class, policy, match, and action definitions on a router. However, be advised that a router with many interfaces and many policies could have a very complicated set of definitions for a user to navigate.

(11)

Traffic Class

A traffic class is a relatively simple concept. All packets that match the criteria in the match statements for a class are members of that class. Each traffic class has a specific name.

Note: The ability to refer to the class by name allows it to be used more than once on a router, which is very useful.

A traffic class is defined in terms of the following attributes:

Class Name — A traffic class name is specified using an ASCII string.

LMatch Statements — These statements determine whether a packet should be considered a member of the class. Match statements specify criteria, and packets’ contents are compared against those criteria. If a statement’s criteria matches the contents of a packet, the match is successful.

Match Combination Logic — This defines how the match statements are to be processed — match-any or match-all. Match-any means the packet is considered to be in the class when any of the class’s match statements are successful. Match-all means the packet is considered to be in the class only when all the class’s match statements are successful.

Match Statement

A match statement is a Modular CB QoS CLI command that defines criteria to be tested against the contents of each packet. The following are some of the possible types of match statements:

match access-group access group

This statement tests packets against a specified access control list (ACL) number. The ACL must have been previously defined.

match cos cos-value [cos-value cos-value cos-value]

This statement tests each packet’s layer 2 Class of Service marking for up to four values. • match destination-address mac

This statement tests each packet’s mac layer destination address. • match input-interface interface-name

This statement tests for the interface of the router that the packet entered. • match ip dscp ip-dscp-value [dscp-value (up to 8 values possible)]

This statement tests the DSCP (DiffServ Control Point)of an IP (Internet Protocol) packet. You can include up to eight DSCP values in the match statement. Values can range from 0 to 63.

match ip precedence ip-precedence-value [ip-precedence value (up to 4 values possible)]

This statement tests the IP Precedence of an IP packet. You can include up to four precedence values in the match statement. Values can range from 0 to 7.

match ip rtp starting-point port-range

This statement matches RTP (Real-Time Transport Protocol) packets whose port range is between

starting-point and starting-starting-point+port-range.

match mpls experimental number

This statement matches Multiprotocol Label Switching (MPLS) packets whose EXP field equals number. match protocol protocol

This statement tests for the protocol of a packet. Among the possible values of protocol are ip, ipx, arp, decnet, vines.

(12)

match qos-group qos-group

This statement tests the qos-group of a packet. The meaning of each qosgroup and its numerical value are defined locally on a router. If a packet has been determined to be in a specified qos-group, the match is successful. This is an important match statement option. Class maps previously defined can be used within a new class map. Using this option is the only method of including both match-any and match-all statements in a single traffic class.

Service Policy

A service policy maps a class to a set of actions. A service policy is implemented with the policy-map Modular CB QoS CLI command. A service policy is defined in terms of the following three attributes:

Policy Name — A policy name is specified using an ASCII string.

Class Name — This is the name of the traffic class that is to be part of this policy. Traffic in this class will have the actions of this policy applied to it.

Actions — These are the QoS traffic management actions.

The following section, QoS Actions, provides information about the possible actions that can be taken. One of these actions defines a way to nest service policies. In other words, a policy can be defined hierarchically, which makes it easy to reuse them.

QoS Actions

The Modular CB QoS CLI can perform the following actions:

• Specifying a minimum bandwidth

• Policing

• Shaping

• Specifying fair queueing

• Specifying WRED (Weighted Random Early Detection)

Some of the possible Modular CB QoS CLI action commands are as follows: • bandwidth {bandwidth-kbps | percent percent]

This action command sets a minimum bandwidth for the traffic class as a raw value or a percent of overall bandwidth.

fair-queue number-of-queues

This action command sets a number of queues to be reserved for this class.

police bps burst-normal burst-max conform-action action exceed-action action violate-action action

This action command specifies the maximum bandwidth to be used by this class. Policing is implemented with a token-bucket algorithm, and these are the parameters for it.

queue-limit

This action command specifies the maximum length of a queue for this traffic (when WRED is not used).

random-detect

This action command enables WRED drop policy when the class has a guaranteed bandwidth. • set ip dscp

(13)

This action command sets the DSCP (DiffServ Control Point) field in the IP Header. It must be between 0 and 63.

set ip precedence

This action command sets the Precedence field in the IP Header. It must be between 0 and 7. • shape {average | peak} mean-rate [burst-size [excess-burst-size]]

This action command shapes the traffic to the indicated burst rate. • service-policy {input | output} policy-map-name

This action command specifies the name of a service policy, which enables the nesting of service-policies. Multiple policies can be applied within a single policy.

Note: Once a service policy is defined, it must be mapped to a network interface using this command.

Review of the CISCO-CLASS-BASED-QOS-MIB

The CISCO-CLASS-BASED-QOS-MIB is the source of all the metrics reported in the Cisco CBQoS Technology Pack. Specifically, the CISCO-CLASS-BASED-QOS-MIB reports metrics associated with the Modular QoS, including configuration and performance information, as well as traffic counts for each of the service policies applied to an interface. You need to understand the CISCO-CLASS-BASED-QOS-MIB only if you intend to customize or augment the contents of the Cisco CBQoS Technology Pack.

Note: The actual data reported for an applied policy depends in part upon the type of actions defined for that policy.

The CISCO-CLASS-BASED-QOS-MIB (located in the file named CISCO-CLASS-BASED-QOS-MIB.my) is

available at the Cisco web site.

The following topics promote an understanding of the CISCO-CLASS-BASED-QOS-MIB: • Policy and Object Tables

Configuration Tables

Performance Tables

Policy and Object Tables

The policy and object tables provide the keys to obtaining the configurations and performance metrics. With these tables you can learn all the run-time service policies and the hierarchy of their components, including classes, match statements, and actions. You can also learn the indexes needed to get configuration and performance metrics for each of these components.

The policy and object tables do the following:

• Support discovery of all the run-time service policies running on a router.

These are the policies that have been attached to an interface and traffic direction. A service policy can be attached to more than one interface and traffic direction. There are unique representations for each of these run-time instances of a service policy.

• Support discovery of the interfaces and traffic directions associated with each run-time service policy. Special support is provided for the Frame Relay and ATM PVC interfaces. The service policies are attached not only to an interface, but also to a circuit or PVC (Permanent Virtual Circuit).

(14)

• Provide a description of the hierarchical structure of each of the run-time service policies. The components (that is, the class (or classes), match statements, and actions) are all identified.

• Provide the appropriate indexes.

For each component type, there is an index to learn the component configuration details and an index to retrieve performance metrics.

The following policy and object tables are described in more detail in the following sections: • cbQosServicePolicyTable

cbQosInterfacePolicyTable

cbQosFrameRelayPolicyTable

cbQosATMPVCPolicyTable

cbQosObjectsTable

The following sections are based on the text provided in the CISCO-CLASS-BASED-QOS-MIB.

cbQosServicePolicyTable

Note: Each entry in this table describes the logical interface to which a given policy map is attached. Depending on the interface and media type, some fields might have meaningful values, and some might not. Please read each individual description.

Each entry in this table represents the application or attachment of a service policy to an interface and traffic direction.

It is possible for the same service policy to be attached to more than one interface and traffic direction. The re-use of service policies is of great value to a re-user configuring QoS on a router. There is a unique service policy instance, and therefore a unique cbQosPolicyIndex for each use of a service policy.

Note: The cbQosPolicyIndex references a unique run-time instance of the service policy. This is to be distinguished from the configuration definition of the service policy.

The Cisco CBQoS Technology Pack uses the following objects in the cbQosServicePolicyTable:

• cbQosIfIndex

• cbQosPolicyDirection

cbQosInterfacePolicyTable

The cbQosInterfacePolicyTable describes the service policies attached to the main interface and the subinterface. This table represents the mapping of service policies to an interface and traffic direction. There is no information in this table that is not in the cbQosServicePolicyTable. However, the indexing of these two tables is different. The cbQosInterfacePolicyTable is of interest to users who want to discover the CB QoS service policies based the interface indexes and directions of traffic.

The Cisco CBQoS Technology Pack uses the following objects in the cbQosInterfacePolicyTable:

• ifIndex

(15)

cbQosFrameRelayPolicyTable

The cbQosFrameRelayPolicyTable describes the service policies attached to the Frame Relay DLCIs (Data

Link Connection Identifiers). The cbQosFrameRelayPolicyTable provides almost the same information as

the cbQosInterfacePolicyTable. The difference is that the cbQosInterfacePolicyTable describes service policies attached to the main and subinterfaces.

Like the cbQosInterfacePolicyTable, the cbQosFrameRelayPolicyTable represents the mapping of

service policies to an interface and direction.

Note: The circuit DLCI is required to identify the index of the service policy attached to the DLCI.

The cbQosFrameRelayPolicyTable is of interest to users who wants to discover the CB QoS service policies based the interface indexes and directions of traffic.

The Cisco CBQoS Technology Pack uses the following objects in the cbQosFrameRelayPolicyTable:

• cbQosPolicyDirection

• ifIndex

cbQosATMPVCPolicyTable

The cbQosATMPVCPolicyTable describes the service policies attached to an Asynchronous Transfer Mode (ATM) PVC (Permanent Virtual Circuit). The Cisco CBQoS Technology Pack uses the following objects in the

cbQosATMPVCPolicyTable: • cbQosPolicyDirection

• ifIndex

cbQosObjectsTable

The cbQosObjectsTable includes entries for all objects defined using the Modular CB QoS CLI, as described in Review of the Modular CB QoS CLI on page 6:

• Classes

• Match Statements

• Service Policies

• Actions

Each entry represents a run-time instance of what has been configured using the CLI. For example, the same class can be reused in multiple service policies, and the same classes and service policies can be attached to more than one interface and traffic direction.

Each attachment to an interface and traffic direction represents a new run-time instance of a service policy. Also, as each service policy is made up of many components — classes, actions and match statements — all of these will be represented by their own run-time instances.

Besides defining every Modular QoS entity, this table also defines the hierarchical relationships among these entities. For example, a match statement is part of a class, and a class is part of a service policy. The hierarchical relationship is defined using the cbQosParentObjectsIndex object in each entry.

The Cisco CBQoS Technology Pack uses the following objects in the cbQosObjectsTable:

• cbQosConfigIndex

(16)

• cbQosObjectsType

• cbQosParentObjectsIndex

Configuration Tables

Configuration tables represent the configuration information associated with the QoS object entries defined in the cbQosObjectsTable. There are tables for each type of QoS object, because each object has unique properties. The index for all these tables is cbQosConfigIndex, the same index returned in the

cbQosObjectsTable.

The Cisco CBQoS Technology Pack works with the following configuration tables that the CISCO-CLASS-BASED-QOS-MIB supports: • cbQosPolicyMapCfgTable • cbQosCMCfgTable • cbQosMatchStmtCfgTable • cbQosQueueingCfgTable • cbQosREDCfgTable • cbQosREDClassCfgTable • cbQosPoliceCfgTable • cbQosTSCfgTable

Table 1 briefly describe each of these configuration tables. The Cisco CBQoS Technology Pack maps these table objects to appropriately named Tivoli Netcool Performance Manager properties. The Cisco CBQoS Technology Pack also uses these objects in Discovery formulas.

Table 1: Configuration tables

Table name Description Objects used by the technology pack

cbQosPolicyMapCfg Table

Specifies configuration information for QoS entry objects of type policymap defined in the cbQosObjectsTable. Each entry in the

cbQosPolicyMapCfgTable table describes configuration information about a policy map.

The cbQosPolicyMapCfgTable contains only configuration information and no statistics. Therefore, this table is indexed by the cbQosConfigIndex of each policy map entry.

(17)

cbQosCMCfgTable Specifies configuration information for QoS entry objects of type

classmap defined in the

cbQosObjectsTable. Each entry

in the cbQosCMCfgTable table

describes configuration information about a class map.

The cbQosCMCfgTable contains only configuration information and no statistics. Therefore, this table is

indexed by the cbQosConfigIndex

of each class map entry.

cbQosCMName

cbQosMatchStmtCfg

Table Specifies configuration information for QoS entry objects of type matchStatement defined in the

cbQosObjectsTable. Each entry

in the cbQosMatchStmtCfgTable

table describes configuration information about a match statement. The cbQosMatchStmtCfgTable

contains only configuration information and no statistics. Therefore, this table is indexed by the

cbQosConfigIndex of each match statement entry.

cbQosMatchStmtName

cbQosQueueingCfg

Table Specifies configuration information for QoS entry objects of type queueing defined in the

cbQosObjectsTable. Each entry

in the cbQosQueueingCfgTable

table describes configuration information about a queueing action. The cbQosQueueingCfgTable

contains only configuration information and no statistics. Therefore, this table is indexed by the

cbQosConfigIndex of each queueing action entry.

• cbQosQueueingCfgBandwidth • cbQosQueueingCfgBandwidthUnits

Table 1: Configuration tables

(18)

cbQosREDCfgTable Specifies configuration information for QoS entry objects of type

randomDetect defined in the

cbQosObjectsTable. Each entry

in the cbQosREDCfgTable table

describes configuration information about a WRED (Weighted Random Early Detection) action.

The cbQosREDCfgTable contains only configuration information and no statistics. Therefore, this table is

indexed by the cbQosConfigIndex

of each WRED action entry.

• cbQosREDCfgDscpPrec • cbQosREDCfgExponWeight • cbQosREDCfgMeanQsize

cbQosREDClassCfg

Table Specifies configuration information for QoS entry objects of type randomDetect defined in the

cbQosObjectsTable. Each entry

in the cbQosREDClassCfgTable

table describes configuration information about a WRED action. More specifically, this table holds the IP precedence-based (not the DSCP values-based) WRED configuration parameters.

The cbQosREDClassCfgTable

contains only configuration information and no statistics. Therefore, this table is indexed by the

cbQosConfigIndex and

cbQosREDValue of each WRED

action entry. The cbQosREDValue

index specifies the IP precedence or IP DSCP (DiffServ Control Point) of the WRED action entry.

• cbQosREDValue

• cbQosREDCfgMaxThreshold • cbQosREDCfgMinThreshold • cbQosREDCfgPkgDropProb

Table 1: Configuration tables

(19)

Performance Tables

Performance tables report statistics associated with the QoS object entries defined in the cbQosObjectsTable. There are tables for each type of QoS object, because each object has unique statistics.

The Cisco CBQoS Technology Pack works with the following performance tables that the CISCO-CLASS-BASED-QOS-MIB supports: • cbQosCMStatsTable Object cbQosMatchStmtStatsTable Object cbQosPoliceStatsTable Object cbQosQueueingStatsTable Object cbQosPoliceCfg

Table Specifies configuration information for QoS entry objects of type police

defined in the

cbQosObjectsTable. Each entry

in the cbQosPoliceCfgTable table

describes configuration information about a police action. Specifically, the table holds such policy configuration parameters as rate, burst size, and actions based on traffic rates. The cbQosPoliceCfgTable

contains only configuration information and no statistics. Therefore, this table is indexed by the

cbQosConfigIndex of each police action entry. • cbQosPoliceCfgBurstSize • cbQosPoliceCfgConformAction • cbQosPoliceCfgExceedAction • cbQosPoliceCfgExtBurstSize • cbQosPoliceCfgRate • cbQosPoliceCfgViolateAction

cbQosTSCfgTable Specifies configuration information for QoS entry objects of type

trafficShaping defined in the

cbQosObjectsTable. Each entry

in the cbQosTSCfgTable table

describes configuration information about a traffic-shaping action. Specifically, the table holds such traffic shaping configuration parameters as rate, burst size, and shaping types.

The cbQosTSCfgTable contains only configuration information and no statistics. Therefore, this table is

indexed by the cbQosConfigIndex

of each traffic-shaping action entry.

• cbQosTSCfgBurstSize • cbQosTSCfgExtBurstSize • cbQosTSCfgRate

Table 1: Configuration tables

(20)

cbQosTSStatsTable Object

cbQosREDClassStatsTable Object

The Cisco CBQoS Technology Pack uses these objects in SNMP collection formulas.

cbQosCMStatsTable Object

The cbQosCMStatsTable specifies statistical information for QoS entry objects of type classmap defined in the cbQosObjectsTable. Each entry in the cbQosCMStatsTable describes statistical information about a class map. The cbQosCMStatsTable includes statistics for all the run-time instances of class maps that are components of service policies defined and attached to interfaces and traffic directions using the Modular CB QoS CLI.

Specifically, the table holds such class map statistical information as: • Traffic counts prior to any QoS policy actions

• Dropped traffic counts as the result of any QoS actions (for example, policing, WRED, queueing, and so forth) associated with the class within a service policy

• Dropped traffic counts due to lack of resources

The cbQosCMStatsTable contains only statistical information and no configuration information. Therefore, this table is indexed by the instance-specific IDs cbQosObjectsIndex (defined in the cbQosObjectsTable) and cbQosPolicyIndex (defined in the cbQosServicePolicyTable) of each class map entry. These two indexes tie each class map entry to an attached run-time service policy and, therefore, to an interface and traffic direction. The cbQosObjectsTable links the run-time class map object to its configuration information and to its place in the hierarchy of QoS objects defined with the Modular CB QoS CLI.

The Cisco CBQoS Technology Pack uses the following objects in the cbQosCMStatsTable:

• cbQosCMPrePolicyByte64 • cbQosCMPrePolicyPkt64 • cbQosCMPostPolicyByte64 • cbQosCMDropByte64 • cbQosCMDropPkt64 • cbQosCMNoBufDropPkt64

The object names have the following meanings:

• cbQosPrePolicy* — Objects with this string in their names provide traffic-related metrics that occur prior to applying any QoS policy actions.

• cbQosPostPolicy* — Objects with this string in their names provide traffic-related metrics that occur after applying any QoS policy actions.

• cbQosDrop* — Objects with this string in their names provide traffic dropped-related metrics that occur after applying any QoS actions.

• cbQosNoBufDrop* — Objects with this string in their names provide traffic dropped-related metrics that occur due to a lack of resources.

cbQosMatchStmtStatsTable Object

The cbQosMatchStmtStatsTable specifies statistical information for QoS entry objects of type

matchStatement defined in the cbQosObjectsTable. Each entry in the cbQosMatchStmtStatsTable

(21)

statistics for all the run-time instances of match statements that are components of service policies defined and attached to interfaces and traffic directions using the Modular CB QoS CLI.

Specifically, the table holds such match statement statistical information as packet and byte counter metrics that occur before applying any QoS policy actions.

The cbQosMatchStmtStatsTable contains only statistical information and no configuration information. Therefore, this table is indexed by the instance-specific IDs cbQosObjectsIndex (defined in the

cbQosObjectsTable) and cbQosPolicyIndex (defined in the cbQosServicePolicyTable) of each match statement entry. These two indexes tie each match statement entry to an attached run-time service policy and, therefore, to an interface and traffic direction. The cbQosObjectsTable links the run-time match statement object to its configuration information and to its place in the hierarchy of QoS objects defined with the Modular CB QoS CLI.

The Cisco CBQoS Technology Pack uses the following objects in the cbQosMatchStmtStatsTable:

• cbQosMatchPrePolicyByte64 • cbQosMatchPrePolicyPkt64

cbQosPoliceStatsTable Object

The cbQosPoliceStatsTable specifies statistical information for QoS entry objects of type police defined

in the cbQosObjectsTable. Each entry in the cbQosPoliceStatsTable describes statistical information

about a police action. The cbQosPoliceStatsTable includes statistics for all the run-time instances of police actions that are components of service policies defined and attached to interfaces and traffic directions using the Modular CB QoS CLI.

Specifically, the table holds such police action statistical information as conformed, exceeded, and violated packet and byte counter metrics.

The cbQosPoliceStatsTable contains only statistical information and no configuration information. Therefore, this table is indexed by the instance-specific IDs cbQosObjectsIndex (defined in the

cbQosObjectsTable) and cbQosPolicyIndex (defined in the cbQosServicePolicyTable) of each police action entry. These two indexes tie each police action entry to an attached run-time service policy and, therefore, to an interface and traffic direction. The cbQosObjectsTable links the run-time police action object to its configuration information and to its place in the hierarchy of QoS objects defined with the Modular CB QoS CLI.

The Cisco CBQoS Technology Pack uses the following objects in the cbQosPoliceStatsTable:

• cbQosMatchPrePolicyByte64 • cbQosPoliceConformedByte64 • cbQosPoliceConformedPkt64 • cbQosPoliceExceededByte64 • cbQosPoliceExceededPkt64 • cbQosPoliceViolatedByte64 • cbQosPoliceViolatedPkt64

cbQosQueueingStatsTable Object

The cbQosQueueingStatsTable specifies statistical information for QoS entry objects of type queueing

defined in the cbQosObjectsTable. Each entry in the cbQosQueueingStatsTable describes statistical

information about a queueing action. The cbQosQueueingStatsTable includes statistics for all the run-time instances of queueing actions that are components of service policies defined and attached to interfaces and traffic directions using the Modular CB QoS CLI.

(22)

Specifically, the table holds such queueing action statistical information as Q depth and discard byte/packet counter metrics.

The cbQosQueueingStatsTable contains only statistical information and no configuration information. Therefore, this table is indexed by the instance-specific IDs cbQosObjectsIndex (defined in the

cbQosObjectsTable) and cbQosPolicyIndex (defined in the cbQosServicePolicyTable) of each queueing action entry. These two indexes tie each queueing action entry to an attached run-time service policy and, therefore, to an interface and traffic direction. The cbQosObjectsTable links the run-time queueing action object to its configuration information and to its place in the hierarchy of QoS objects defined with the Modular CB QoS CLI.

The Cisco CBQoS Technology Pack uses the following objects in the cbQosQueueingStatsTable:

• cbQosQueueingDiscardByte64 • cbQosQueueingDiscardPkt64

cbQosTSStatsTable Object

The cbQosTSStatsTable specifies statistical information for QoS entry objects of type trafficShaping

defined in the cbQosObjectsTable. Each entry in the cbQosTSStatsTable describes statistical information about a traffic shaping action. The cbQosTSStatsTable includes statistics for all the run-time instances of traffic shaping actions that are components of service policies defined and attached to interfaces and traffic directions using the Modular CB QoS CLI.

Specifically, the table holds such traffic shaping action statistical information as Q size and delay/drop byte/packet counter metrics.

The cbQosTSStatsTable contains only statistical information and no configuration information. Therefore, this table is indexed by the instance-specific IDs cbQosObjectsIndex (defined in the cbQosObjectsTable) and cbQosPolicyIndex (defined in the cbQosServicePolicyTable) of each traffic shaping action entry. These two indexes tie each traffic shaping action entry to an attached run-time service policy and, therefore, to an interface and traffic direction. The cbQosObjectsTable links the run-time traffic shaping action object to its configuration information and to its place in the hierarchy of QoS objects defined with the Modular CB QoS CLI.

The Cisco CBQoS Technology Pack uses the following objects in the cbQosTSStatsTable:

• cbQosTSStatsDelayedByte64 • cbQosTSStatsDelayedPkt64 • cbQosTSStatsDropByte64 • cbQosTSStatsDropPkt64

cbQosREDClassStatsTable Object

The cbQosREDClassStatsTable specifies statistical information for QoS entry objects of type

randomDetect defined in the cbQosObjectsTable. Each entry in the cbQosREDClassStatsTable

describes statistical information about a per precedence WRED (Weighted Random Early Detection) action. The

cbQosREDClassStatsTable includes statistics for all the run-time instances of per precedence WRED actions that are components of service policies defined and attached to interfaces and traffic directions using the Modular CB QoS CLI.

Specifically, the table holds such per precedence WRED action statistical information as random drop byte/packet, tail drop byte/packet, and transmit byte/packet counter metrics.

The cbQosREDClassStatsTable contains only per precedence/DSCP statistical information and no configuration information. Therefore, this table is indexed by the instance-specific IDs cbQosObjectsIndex

(23)

cbQosServicePolicyTable) of each per precedence WRED action entry. These two indexes tie each per precedence WRED action entry to an attached run-time service policy and, therefore, to an interface and traffic

direction. The cbQosObjectsTable links the run-time per precedence WRED action object to its

configuration information and to its place in the hierarchy of QoS objects defined with the Modular CB QoS CLI.

In addition to the cbQosObjectsIndex and cbQosPolicyIndex indexes, the

cbQosREDClassStatsTable also provides for an index called cbQosREDValue defined in the

cbQosREDClassCfgTable. See Configuration Tables on page 12 for more information.

The Cisco CBQoS Technology Pack uses the following objects in the cbQosREDClassStatsTable:

• cbQosREDRandomDropByte64 • cbQosREDRandomDropPkt64 • cbQosREDTailDropByte64 • cbQosREDTailDropPkt64 • cbQosREDTransmitByte64 • cbQosREDTransmitPkt64

(24)
(25)

This chapter discusses the following topics:

Overview

The Cisco CBQoS Technology Pack supplies a set of reports to display information about the devices and activity associated with the Cisco Class-Based QoS environment.

The reports contain metrics that are generated by the formulas that this technology pack provides. The metric names are the same as the names of the formulas that generate them. For information about a metric that is listed for a particular report, see the description of the associated formula in the Collection Formulas section of the

IBM Tivoli Netcool Performance Manager Cisco Class-Based QoS 2.2.0.0 Technology Pack Reference.

For information about how to navigate to a particular report on the DataView portal, see the NOC Reporting tree in the Subelement Groups section of the IBM Tivoli Netcool Performance Manager Cisco Class-Based QoS 2.2.0.0

Technology Pack Reference. This chapter provides information about deployed reports only.

For information about understanding report types, creating reports, configuring reports, viewing and working with reports, and deploying reports, see the IBM Tivoli Netcool Performance Manager DataView User and Administration

Guide. This Technology Pack User Guide assumes an understanding of the report-related topics discussed in the IBM Tivoli Netcool Performance Manager DataView User and Administration Guide.

Reporter sets

A reporter set contains a group of reporters that together provide information about a specific technology or vendor device. Technology pack developers use the Reporter Set Wizard to choose the type of template on which to base the reporter set. Technology packs use reporter sets as the framework for defining reports.

The Cisco CBQoS Technology Pack reports display, on a Web portal, the collected information about the devices and technologies that operate in the Cisco Class-Based QoS environment.

Topic Page

Overview 21 Reporter sets 21

Reporter set tree 22

Reporter set contents 23

(26)

Table 2 shows a summary of the reports in each reporter set provided by the Cisco CBQoS Technology Pack. Table 2: Reporter set summary

See the IBM Tivoli Netcool Performance Manager DataView User and Administration Guide for more information about reporter sets and the Reporter Set Wizard.

Reporter set tree

The Cisco CBQoS Technology Pack provides the following reporter sets, which are listed as they appear in the DataView Navigator tree structure:

Cisco CBQoS Class Match Common Reports Per Policy Police Queue Shape WRED

Reporter set Dashboard Group Resource Detail Threshold Class Match 0 2 1 1 0 Common Reports 2 0 0 0 0 Per Policy 8 1 1 4 6 Police 1 1 1 3 12 Queue 1 1 1 1 0 Shape 1 1 1 4 8 WRED 0 2 1 3 0

(27)

Reporter set contents

This section describes the contents of the reporter sets provided in the Cisco CBQoS Technology Pack, including the key performance indicators (KPIs) for each report.

Class Match

Match Stmts per Class Group Summary

KPIs

• Policy Throughput (bps) • Policy Volume (packets) • Policy Volume (octets) Charts

• Policy Volume (packets) • Policy Throughput (bps)

Match Statement Group Summary

KPIs

• Policy Throughput (bps) • Policy Volume (packets) • Policy Volume (octets) Charts

• Policy Volume (packets) • Policy Throughput (bps)

Match Stmts per Class Resource Summary

KPIs

• Policy Throughput (bps) • Policy Volume (packets) • Policy Volume (octets) Charts

• Policy Throughput (bps) • Policy Volume (packets)

Match Stmts Details

KPIs

(28)

• Match Policy Volume (packets) • Match Policy Volume (octets) Charts

• Match Policy Throughput (bps) • Match Policy Volume (packets) • Match Policy Volume (octets)

Common Reports

Device Health Overview

KPIs

• WRED Tail Drops Volume (packets) • Policy Drops (percent)

• WRED Random Drops Volume (packets) • Queue Policy Drops (packets)

• Traffic Shaping Dropped Volume (packets) • Policy Drops (packets)

Charts

• Highest Queue Policy Drops (packets)

• Rank Variations for WRED Tail Drops Volume (packets) • Highest WRED Random Drops Volume (packets) • Rank Variations for Policy Drops (percent) • Highest WRED Tail Drops Volume (packets) • Highest Policy Drops (packets)

• Highest Traffic Shaping Dropped Volume (packets) • Highest Policy Drops (percent)

• Rank Variations for Queue Policy Drops (packets)

• Rank Variations for Traffic Shaping Dropped Volume (packets) • Rank Variations for WRED Random Drops Volume (packets) • Rank Variations for Policy Drops (packets)

Device Traffic Overview

KPIs

• Policing Conformed Throughput (bps) • WRED Transmit Rate (bps)

• Pre-Policy Throughput (bps) • Post-Policy Throughput (bps)

(29)

Charts

• Rank Variations for WRED Transmit Rate (bps) • Highest Post-Policy Throughput (bps)

• Rank Variations for Pre-Policy Throughput (bps) • Highest WRED Transmit Rate (bps)

• Highest Pre-Policy Throughput (bps)

• Rank Variations for Post-Policy Throughput (bps) • Highest Policing Conformed Throughput (bps)

• Rank Variations for Policing Conformed Throughput (bps)

Per Policy

Per Policy Health Overview

KPIs

• Policy Drops (percent)

• No Buffer Queue Drops (packets) • Policy Drops (packets)

• Policy Drops (octets) Charts

• Highest Policy Drops (percent)

• Rank Variations for Policy Drops (packets) • Highest Policy Drops (octets)

• Rank Variations for Policy Drops (octets) • Rank Variations for Policy Drops (percent) • Highest Policy Drops (packets)

• Rank Variations for No Buffer Queue Drops (packets) • Highest No Buffer Queue Drops (packets)

Top 5 Policies

KPIs

• Policy Drops (percent) • Pre-Policy Throughput (bps) • Post-Policy Throughput (bps) • Policy Drops (packets) Charts

• Rank Variations for Post-Policy Throughput (bps) • Highest Pre-Policy Throughput (bps)

(30)

• Highest Post-Policy Throughput (bps) • Highest Policy Drops (percent)

• Rank Variations for Pre-Policy Throughput (bps) • Highest Policy Drops (packets)

• Rank Variations for Policy Drops (packets) • Rank Variations for Policy Drops (percent)

Network Policy Health Overview

KPIs

• Policy Drops (%) • Policy Drops (packets) Charts

• Highest Policy Drops (packets)

• Rank Variations for Policy Drops (percent) • Highest Policy Drops (percent)

• Rank Variations for Policy Drops (packets)

Network Policy Traffic Overview

KPIs

• Pre-Policy Throughput (bps) • Post-Policy Throughput (bps) Charts

• Highest Post-Policy Throughput (bps)

• Rank Variations for Post-Policy Throughput (bps) • Rank Variations for Pre-Policy Throughput (bps) • Highest Pre-Policy Throughput (bps)

Policy Action Health Overview

KPIs

• Queue Policy Drop Rate (bps) • Policing Violated Throughput (bps) • Traffic Shaping Dropped Throughput (bps) Charts

• Rank Variations for Traffic Shaping Dropped Throughput (bps) • Highest Policing Violated Throughput (bps)

• Highest Traffic Shaping Dropped Throughput (bps) • Highest Queue Policy Drop Rate (bps)

(31)

• Rank Variations for Policing Violated Throughput (bps) • Rank Variations for Queue Policy Drop Rate (bps)

Policy Action Traffic Overview

KPIs

• Policing Conformed Throughput (bps) • Policing Conformed Volume (packets) • Traffic Shaping Delayed Volume (packets) • Traffic Shaping Delayed Throughput (bps) Charts

• Rank Variations for Traffic Shaping Delayed Throughput (bps) • Highest Traffic Shaping Delayed Throughput (bps)

• Highest Policing Conformed Throughput (bps) • Highest Traffic Shaping Delayed Volume (packets) • Highest Policing Conformed Volume (packets)

• Rank Variations for Policing Conformed Volume (packets) • Rank Variations for Policing Conformed Throughput (bps) • Rank Variations for Traffic Shaping Delayed Volume (packets)

Per Policy Traffic Overview

KPIs

• Pre-Policy Throughput (bps) • Post-Policy Throughput (bps) Charts

• Highest Pre-Policy Throughput (bps)

• Rank Variations for Post-Policy Throughput (bps) • Highest Post-Policy Throughput (bps)

• Rank Variations for Pre-Policy Throughput (bps)

Top 5 Policies I

KPIs

• Pre-Policy Volume (packets) • Pre-Policy Volume (octets) • Policy Drops (octets) Charts

• Highest Policy Drops (octets)

(32)

• Rank Variations for Pre-Policy Volume (packets) • Highest Pre-Policy Volume (packets)

• Highest Pre-Policy Volume (octets)

• Rank Variations for Pre-Policy Volume (octets)

Policy Group Summary

KPIs

• Pre-Policy Volume (packets) • Pre-Policy Volume (octets) • Policy Drops (percent) • Pre-Policy Throughput (bps) • Post-Policy Throughput (bps) • Policy Drops (packets) • Policy Drops (octets) Charts

• Post-Policy Throughput (bps) • Pre-Policy Throughput (bps)

Policy Resource Summary

KPIs

• Pre-Policy Volume (packets) • Pre-Policy Volume (octets) • Policy Drops (percent) • Pre-Policy Throughput (bps) • Post-Policy Throughput (bps) • Policy Drops (packets) • Policy Drops (octets) Charts

• Post-Policy Throughput (bps) • Pre-Policy Throughput (bps)

Policy Details

KPIs

• Pre-Policy Volume (packets) • Pre-Policy Volume (octets) • Policy Drops (percent) • Pre-Policy Throughput (bps)

(33)

• Policy Drops (packets) • Policy Drops (octets) Charts

• Pre-Policy Volume (packets) • Post-Policy Throughput (bps) • Pre-Policy Throughput (bps) • Policy Drops (percent) • Policy Drops (octets) • Policy Drops (packets) • Pre-Policy Volume (octets)

Policy Health Details

KPIs

• Policy Drops (packets) • Policy Drops (percent) Charts

• Policy Drops (packets) • Policy Drops (percent)

Policy Traffic Details

KPIs • Post-Policy Throughput (bps) • Pre-Policy Throughput (bps) Charts • Post-Policy Throughput (bps) • Pre-Policy Throughput (bps)

Pre-Policy Throughput (bps) Baseline Threshold Violations

KPIs

• Pre-Policy Throughput (bps)

Post-Policy Throughput (bps) Baseline Threshold Violations

KPIs

(34)

Policy Drops (percent) Baseline Threshold Violations

KPIs

• Policy Drops (percent)

Pre-Policy Throughput (bps) Baseline Threshold Violation Details

Charts

• Pre Policy Throughput (bps)

Post-Policy Throughput (bps) Baseline Threshold Violation Details

Charts

• Post Policy Throughput (bps)

Policy Drops (percent) Throughput (bps) Baseline Threshold Violation Details

Charts

• Policy Drops (percent)

Per Policy Health Details

KPIs

• Policy Drops (percent) • Policy Drops (octets) • Policy Drops (packets)

• No Buffer Queue Drops (packets) Charts

• Policy Drops (octets) • Policy Drops (percent) • Policy Drops (packets)

• No Buffer Queue Drops (packets)

Police

Policed Traffic per Class Action Overview

KPIs

• Policing Violated Volume (packets) • Policing Violated Volume (octets) • Policing Exceeded Volume (octets) • Policing Exceeded Volume (packets) • Policing Conformed Volume (packets)

(35)

• Policing Conformed Volume (octets) Charts

• Highest Policing Conformed Volume (packets)

• Rank Variations for Policing Exceeded Volume (packets) • Rank Variations for Policing Exceeded Volume (octets) • Highest Policing Violated Volume (octets)

• Rank Variations for Policing Violated Volume (octets) • Rank Variations for Policing Conformed Volume (packets) • Rank Variations for Policing Conformed Volume (octets) • Highest Policing Conformed Volume (octets)

• Highest Policing Violated Volume (packets)

• Rank Variations for Policing Violated Volume (packets) • Highest Policing Exceeded Volume (packets)

• Highest Policing Exceeded Volume (octets)

Policed Traffic per Class Group Summary

KPIs

• Policing Violated Volume (packets) • Policing Violated Volume (octets) • Policing Exceeded Volume (octets) • Policing Exceeded Volume (packets) • Policing Conformed Volume (packets) • Policing Conformed Volume (octets) Charts

• Policing Conformed Volume (octets) • Policing Violated Volume (octets)

Policed Traffic per Class Resource Summary

KPIs

• Policing Violated Volume (packets) • Policing Violated Volume (octets) • Policing Exceeded Volume (octets) • Policing Exceeded Volume (packets) • Policing Conformed Volume (packets) • Policing Conformed Volume (octets) Charts

(36)

• Policing Conformed Volume (octets)

Policed Traffic Details

KPIs

• Policing Violated Volume (packets) • Policing Violated Volume (octets) • Policing Exceeded Volume (octets) • Policing Exceeded Volume (packets) • Policing Conformed Volume (packets) • Policing Conformed Volume (octets) Charts

• Policing Conformed Volume (octets) • Policing Conformed Volume (packets) • Policing Violated Volume (octets) • Policing Violated Volume (packets) • Policing Exceeded Volume (octets) • Policing Exceeded Volume (packets)

Threshold Violation - Conformed Volume (octets)

KPIs

• Policing Conformed Volume (octets)

Threshold Violation - Conformed Volume (octets) Details

Charts

• Policing Conformed Volume (octets)

Threshold Violation - Conformed Volume (packets)

KPIs

• Policing Conformed Volume (packets)

Threshold Violation - Conformed Volume (packets) Details

Charts

• Policing Conformed Volume (packets)

Threshold Violation - Exceeded Volume (octets)

KPIs

(37)

Threshold Violation - Exceeded Volume (octets) Details

Charts

• Policing Exceeded Volume (octets)

Threshold Violation - Exceeded Volume (packets)

KPIs

• Policing Exceeded Volume (packets)

Threshold Violation - Exceeded Volume (packets) Details

Charts

• Policing Exceeded Volume (packets)

Threshold Violation - Violated Volume (octets)

KPIs

• Policing Violated Volume (octets)

Threshold Violation - Violated Volume (octets) Details

Charts

• Policing Violated Volume (octets)

Threshold Violation - Violated Volume (packets)

KPIs

• Policing Violated Volume (packets)

Threshold Violation - Violated Volume (packets) Details

Charts

• Policing Violated Volume (packets)

Policing Conformed Details

KPIs

• Policing Conformed Throughput (bps) • Policing Conformed Volume (packets) Charts

• Policing Conformed Throughput (bps) • Policing Conformed Volume (packets)

(38)

Policing Exceeded and Violated Details

KPIs

• Policing Exceeded Volume (packets) • Policing Violated Volume (packets) • Policing Exceeded Throughput (bps) • Policing Violated Throughput (bps) Charts

• Policing Violated Throughput (bps) • Policing Exceeded Volume (packets) • Policing Violated Volume (packets) • Policing Exceeded Throughput (bps)

Queue

Queued Traffic per Class Action Overview

KPIs

• Queue Policy Drops (packets) • Queue Policy Drop Rate (bps) • Queue Policy Drops (octets) Charts

• Highest Queue Policy Drops (octets) • Highest Queue Policy Drop Rate (bps)

• Rank Variations for Queue Policy Drops (packets) • Rank Variations for Queue Policy Drop Rate (bps) • Rank Variations for Queue Policy Drops (octets) • Highest Queue Policy Drops (packets)

Queued Traffic per Class Group Summary

KPIs

• Queue Policy Drops (packets) • Queue Policy Drop Rate (bps) • Queue Policy Drops (octets) Charts

• Queue Policy Drop Rate (bps) • Queue Policy Drops (packets)

(39)

Queued Traffic per Class Resource Summary

KPIs

• Queue Policy Drops (packets) • Queue Policy Drop Rate (bps) • Queue Policy Drops (octets) Charts

• Queue Policy Drops (packets) • Queue Policy Drop Rate (bps)

Queued Drops Details

KPIs

• Queue Policy Drops (packets) • Queue Policy Drop Rate (bps) • Queue Policy Drops (octets) Charts

• Queue Policy Drops (packets) • Queue Policy Drop Rate (bps) • Queue Policy Drops (octets)

Shape

Shaped Traffic per Class Action Overview

KPIs

• Traffic Shaping Delayed Volume (packets) • Traffic Shaping Dropped Throughput (bps) • Traffic Shaping Delayed Throughput (bps) • Traffic Shaping Dropped Volume (packets) Charts

• Highest Traffic Shaping Dropped Volume (packets)

• Rank Variations for Traffic Shaping Delayed Volume (packets) • Rank Variations for Traffic Shaping Delayed Throughput (bps) • Highest Traffic Shaping Delayed Volume (packets)

• Highest Traffic Shaping Dropped Throughput (bps)

• Rank Variations for Traffic Shaping Dropped Throughput (bps) • Rank Variations for Traffic Shaping Dropped Volume (packets) • Highest Traffic Shaping Delayed Throughput (bps)

(40)

Shaped Traffic per Class Group Summary

KPIs

• Delayed Volume (packets) • Dropped Volume (octets) • Dropped Volume (packets) • Delayed Volume (octets) Charts

• Delayed Volume (octets) • Dropped Volume (octets)

Shaped Traffic per Class Resource Summary

KPIs

• Delayed Volume (packets) • Dropped Volume (octets) • Dropped Volume (packets) • Delayed Volume (octets) Charts

• Dropped Volume (octets) • Delayed Volume (octets)

Shaped Traffic Details

KPIs

• Traffic Shaping Delayed Volume (packets) • Traffic Shaping Dropped Volume (octets) • Traffic Shaping Dropped Volume (packets) • Traffic Shaping Delayed Volume (octets) Charts

• Delayed Volume (packets) • Delayed Volume (octets) • Dropped Volume (packets) • Dropped Volume (octets)

Shaping Traffic Details

KPIs

• Traffic Shaping Delayed Volume (packets) • Traffic Shaping Delayed Throughput (bps)

(41)

Charts

• Traffic Shaping Delayed Volume (packets) • Traffic Shaping Delayed Throughput (bps)

Shaping Health Details

KPIs

• Traffic Shaping Dropped Volume (packets) • Traffic Shaping Dropped Throughput (bps) Charts

• Traffic Shaping Dropped Volume (packets) • Traffic Shaping Dropped Throughput (bps)

Threshold Violation - Shaping Delayed Volume (octets)

KPIs

• Traffic Shaping Delayed Volume (octets)

Threshold Violation - Shaping Delayed Volume (octets) Details

Charts

• Traffic Shaping Delayed Volume (octets)

Threshold Violation - Shaping Delayed Volume (packets)

KPIs

• Traffic Shaping Delayed Volume (packets)

Threshold Violation - Shaping Delayed Volume (packets) Details

Charts

• Traffic Shaping Delayed Volume (packets)

Threshold Violation - Shaping Dropped Volume (octets)

KPIs

• Traffic Shaping Dropped Volume (octets)

Threshold Violation - Shaping Dropped Volume (octets) Details

Charts

(42)

Threshold Violation - Shaping Dropped Volume (packets)

KPIs

• Traffic Shaping Dropped Volume (packets)

Threshold Violation - Shaping Dropped Volume (packets) Details

Charts

• Traffic Shaping Dropped Volume (packets)

Shaping Details

KPIs

• Traffic Shaping Dropped Volume (packets) • Traffic Shaping Dropped Throughput (bps) • Traffic Shaping Delayed Volume (packets) • Traffic Shaping Delayed Throughput (bps) Charts

• Dropped Volume (packets) • Dropped Throughput (bps) • Delayed Volume (packets) • Delayed Throughput (bps)

WRED

WRED per Class Group Summary

KPIs

• Tail Drops Volume (octets) • Transmit Volume (octets) • Random Drops Volume (octets) • Transmit Rate (bps)

Charts

• Tail Drops Volume (octets) • Transmit Rate (bps)

WRED Group Summary

KPIs

• Tail Drops Volume (octets) • Transmit Volume (octets)

(43)

• Transmit Rate (bps) Charts

• Tail Drops Volume (octets) • Transmit Rate (bps)

WRED per Class Resource Summary

KPIs

• Tail Drops Volume (octets) • Transmit Volume (octets) • Random Drops Volume (octets) • Transmit Rate (bps)

Charts

• Transmit Volume (bps) • Tail Drops Volume (octets)

Class WRED Details

KPIs

• WRED Transmit Volume (packets) • WRED Tail Drops Volume (octets) • WRED Transmit Volume (octets) • WRED Random Drops Volume (octets) • WRED Tail Drops Volume (packets) • WRED Transmit Rate (bps)

• WRED Random Drops Volume (packets) Charts

• WRED Random Drops Volume (octets) • WRED Transmit Rate (bps)

• WRED Random Drops Volume (packets) • WRED Transmit Volume (octets) • WRED Tail Drops Volume (octets) • WRED Transmit Volume (packets) • WRED Tail Drops Volume (packets)

Class WRED Health Details

KPIs

• WRED Tail Drops Volume (pkts) • WRED Random Drops Volume (pkts)

(44)

Charts

• WRED Random Drops Volume (packets) • WRED Tail Drops Volume (packets)

Class WRED Traffic Details

KPIs

• WRED Transmit Rate (bps) • WRED Transmit Volume (pkts) Charts

• WRED Transmit Rate (bps) • WRED Transmit Volume (packets)

(45)

Key performance indicators

Table 3 lists all of the key performance indicators (KPIs) supported by the Cisco CBQoS Technology Pack. Table 3: Key performance indicators

KPI Comment

Class Match Policy Throughput (bps) Per Policy Class-Map Match Statement Throughput (bps) Class Match Policy Volume (octets) Per Class-Map Match Statement Volume (octets)

Class Match Policy Volume (pkts) Class Match Policy Volume (pkts)

No Buffer Queue Drops (packets) No Buffer Queue Drops per Class-Map Queuing Action defined for congestion

Policing Conformed Throughput (bps) Per Policy Policed Traffic Throughput per Class-Map Action Policing Conformed Volume (octets) Per Policy Policed Traffic Conformed (Octets) per Class-Map

Action

Policing Conformed Volume (packets) Per Policy Policed Traffic Conformed (Packets) per Class-Map Action

Policing Exceeded Throughput (bps) Per Policy Policed Traffic Exceeded Throughput (bps) per Class-Map Action

Policing Exceeded Volume (octets) Per Policy Policed Traffic Exceeded (octets) per Class-Map Action Policing Exceeded Volume (packets) Per Policy Policed Traffic Exceeded per Class-Map Action Policing Violated Throughput (bps) Per Policy Policed Traffic Violated Throughput (bps) per

Class-Map Action

Policing Violated Volume (octets) Per Policy Policed Traffic Violated (octets) per Class-Map Action Policing Violated Volume (packets) Per Policy Policed Traffic Violated Traffic (packets) per Class-Map

Action

Policy Drops (%) Per Policy Dropped Traffic (%)

Policy Drops (octets) Per Policy Total Dropped Traffic (octets) per Class-Map Policy Drops (packets) Per Policy Total Dropped Traffic (Packets) per Class-Map Post-Policy Throughput (bps) Post-Policy Throughput (bps) per Class-Map

Pre-Policy Throughput (bps) Pre-Policy Throughput (bits per sec) per Class-Map Pre-Policy Volume (octets) Pre-Policy Byte Traffic per Class-Map

Pre-Policy Volume (packets) Pre-Policy Packet Traffic per Class-Map

Queue Policy Drop Rate (bps) Per Policy Dropped Traffic Rate per Class Queuing Action (bps) Queue Policy Drops (octets) Per Policy Dropped Traffic per Class Queuing Action (octets) Queue Policy Drops (pkts) Per Policy Dropped Traffic per Class Queuing Action (packets) Traffic Shaping Delayed Throughput

(bps)

Per Policy Traffic Shaped Delayed Throughput (bps) per Class-Map Action

(46)

Traffic Shaping Delayed Volume (octets)

Per Policy Traffic Shaped Delayed (octets) per Class-Map Action Traffic Shaping Delayed Volume

(packets)

Per Policy Traffic Shaped Delayed (packets) per Class-Map Action Traffic Shaping Dropped Throughput

(bps)

Per Policy Traffic Shaped Dropped Throughput (bps) per Class-Map Action

Traffic Shaping Dropped Volume (octets)

Per Policy Traffic Shaped Dropped (octets) per Class-Map Action Traffic Shaping Dropped Volume

(packets)

Per Policy Traffic Shaped Dropped (packets) per Class-Map Action WRED Random Drops Volume (octets) Per Policy Random Dropped Traffic per Class WRED prec/dscp

Action (octets)

WRED Random Drops Volume (pkts) Per Policy Random Dropped Traffic per Class WRED prec/dscp Action (packets)

WRED Tail Drops Volume (octets) Per Policy Tail Dropped Traffic per Class WRED prec/dscp Action (octets)

WRED Tail Drops Volume (pkts) Per Policy Tail Dropped Traffic per Class WRED prec/dscp Action (octets)

WRED Transmit Rate (bps) Per Policy Forwarded Traffic per Class WRED prec/dscp Action (bps)

WRED Transmit Volume (octets) Per Policy Forwarded Traffic per Class WRED prec/dscp Action (octets)

WRED Transmit Volume (pkts) Per Policy Forwarded Traffic per Class WRED prec/dscp Action (packets)

(47)

This chapter explains how to configure the Cisco CBQoS Technology Pack and consists of the following topics:

Overview

The Cisco CBQoS Technology Pack is a MIB-based, SNMP pack, and its configuration is relatively straightforward.

Before you begin

Before configuring the Cisco CBQoS Technology Pack, ensure that you:

• Have the following software and documentation for your version of Tivoli Netcool Performance Manager:

— IBM Tivoli Netcool Performance Manager Technology Pack Release Notes for the current technology pack release

— IBM Tivoli Netcool Performance Manager Installation Guide

— IBM Tivoli Netcool Performance Manager Technology Pack Installation Guide

— IBM Tivoli Netcool Performance Manager Upgrade Guide(if you are upgrading the core software)

— IBM Tivoli Netcool Performance Manager Technology Pack Upgrade Guide(if you are upgrading the technology-pack software)

— IBM Tivoli Netcool Performance Manager DataMart Configuration Guide

Important: Refer to this guide to create an inventory profile and initiate a discovery.

— Access to the Tivoli Netcool Performance Manager DataMart server — An X Window server on the DataMart server

Note: (Tivoli Netcool Performance Manager ) If there is no graphics card on the DataMart server, you can install the Xvfb virtual frame buffer package to provide X Window services, as described in the IBM Tivoli Netcool Performance Manager Installation Guide.

Topic Page

Overview 43 Before you begin 43 Configure the technology pack 44

Losing Indexes After Device Reboots 47

(48)

— Access to the DataChannel server

• Have completed the following tasks:

— Reviewed the release notes for the current technology pack.

Important: Release notes contain important information you need to consider before installing a technology pack. They also contain information on specific patches that need to be installed before you configure a technology pack.

— Installed the current version of the Tivoli Netcool Performance Manager components, as described in the IBM Tivoli Netcool Performance Manager Installation Guide.

— Installed the Cisco CBQoS Technology Pack.

Note: Installation instructions for a technology pack can be found in the IBM Tivoli Netcool Performance Manager Technology Pack Installation Guide.

Upgrade instructions for a technology pack can be found in the IBM Tivoli Netcool Performance Manager Technology Pack Upgrade Guide.

Localization is done automatically during installation of the technology pack.

— Configured at least one DataChannel. — Configured an SNMP collector subchannel.

— Created a user on the Cisco Class-Based QoS server with permission to ftp and delete files.

Configure the technology pack

To configure the Cisco CBQoS Technology Pack, follow these steps: 1. Load the DataMart environment.

To load the shell with the DataMart environment, follow these steps: 1-a. Log in to the DataMart server as pvuser.

1-b. Change your working directory to the DataMart home directory (/opt/datamart, by default), using the following command:

cd /opt/datamart

1-c. Load the shell with the DataMart environment, by sourcing the dataMart.env file, as follows:

. /opt/datamart/dataMart.env

Note: After you load the DataMart environment into the shell, the PVMHOME variable is set to the DataMart home directory, /opt/datamart by default. These instructions assume that this variable has been set.

2. Activate data collection requests.

During installation of the technology pack, all predefined data collection requests are promoted to the database and set to inactive (that is, idle displays in the Active column of the Tivoli Netcool Performance Manager DataMart Request Editor). You need to activate these predefined data collection requests using the Request Editor.

To set data collection requests to active, follow these steps:

2-a. Change your working directory to $PVMHOME/bin (/opt/datamart/bin, by default) on the

DataMart server.

References

Related documents

At the middle school level, performers must be able to play a steady beat, play accurate rhythms, demonstrate correct eye movements, and recognize patterns of notes to be an

In the broader child psychology literature low self-esteem, peer relationships problems and bullying victimisation, difficulties in emotion regulation and coping, poor social

This is a program-to-program agreement between the Bucks County Community College (BCCC) and Philadelphia University’s Office of Continuing & Professional Studies

Rearrange the following letters to make a single word and then choose the category in which it belongs..

The anotlcent rrust certify that it viii st•rt construction if!.YllCdfetcly •fter the rodlflc .l.. tion is

Assessment Item Grade Percentage  Quizzes [7 @ 2% ea.] *Single lowest score dropped 14%  Capstone Assignment 5%  In Class Assessment (2 @ 3% each) 6%  Graded Cases

First of all there is a different interpretation of the service experience components: When for the regular users the Service Interface means going from the analogical to the

In order for the Department of Health and Human Services to bill the federal government for services provided under the Medi-Cal billing program, Targeted Case Management (TCM), the