IBM. Tivoli. Netcool/Proviso. Cisco Class-Based QoS Technology Pack. User Guide. Document Revision R2E2

Transcription

1 Tivoli Netcool/Proviso Document Revision R2E2 IBM Cisco Class-Based QoS Technology Pack User Guide

2 Note Before using this information and the product it supports, read the information in Notices on page 41. Copyright IBM Corp US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents Chapter 1: Introduction Audience Organization Chapter 2: Devices and services Overview Summary of device technology Supported MIBs RFC1213-MIB CISCO-CLASS-BASED-QOS-MIB Review of the Modular CB QoS CLI Traffic Class Match Statement Service Policy QoS Actions Review of the CISCO-CLASS-BASED-QOS-MIB Policy and Object Tables Configuration Tables Performance Tables Chapter 3: Supported reports and Overview Reporter sets Reporter set tree Reporter set contents Key performance indicators Chapter 4: Configuring the technology pack Overview Before you begin Configure the technology pack Verifying resources Losing Indexes After Device Reboots IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide iii

4 Customizing Discovery Results InventoryHook.sh InventoryAppPack.sh cbqos_object_id_mv.pl Notices Additional Copyright Information iv IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide

5 Chapter 1: Introduction This manual describes the IBM Tivoli Netcool /Proviso 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/Proviso 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/Proviso 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 technology packs. Chapter 2, Devices and services Provides an overview of the device technology supported by the technology pack. Chapter 3, Supported reports and Provides information about the reporter sets and key performance indicators () 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/Proviso product suite Tivoli Netcool/Proviso is made up of the following components: IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide 1

6 Chapter 1: Introduction Tivoli Netcool/Proviso DataMart is a set of management, configuration and troubleshooting GUIs that the Tivoli Netcool/Proviso system administrator uses to define policies and configuration, as well as to verify and troubleshoot operations. Tivoli Netcool/Proviso DataLoad provides flexible, distributed data collection and data import of SNMP and non-snmp data to a centralized database. Tivoli Netcool/Proviso DataChannel aggregates the data collected through Tivoli Netcool/Proviso DataLoad for use by the Tivoli Netcool/Proviso DataView reporting functions. It also processes on-line calculations and detects real-time threshold violations. Tivoli Netcool/Proviso DataView is a reliable application server for on-demand, web-based network reports. Tivoli Netcool/Proviso Technology Packs extend the Tivoli Netcool/Proviso system with service-ready reports for network operations, business development, and customer viewing. Figure 1 shows the different Tivoli Netcool/Proviso modules. Figure 1: Tivoli Netcool/Proviso modules DataLoad collects network data. DataChannel computes aggregations and stores data in DataMart. DataMart provides data management and applications. DataView produces and manages reports. Tivoli Netcool/Proviso documentation IBM provides the following Tivoli Netcool/Proviso documentation: Release notes Configuration recommendations User guides References Technical notes Online help 2 IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide

7 Chapter 2: Devices and services This chapter discusses the following topics: Topic Page Overview 3 Summary of device technology 3 Supported MIBs 3 Review of the Modular CB QoS CLI 5 Review of the CISCO-CLASS-BASED-QOS-MIB 8 Overview This chapter provides a summary of the Cisco Class-Based QoS device technology and the associated Management Information Bases (MIBs), which 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 CB QoS CLI (Modular Class-Based Quality of Service Command Line Interface) lets you configure classes of traffic and actions to take on these different traffic classes. The CISCO-CLASS-BASED-QOS-MIB (located in the file named CISCO-CLASS-BASED-QOS-MIB.my) reports metrics that correspond to the classes and actions configured with the Modular CB QoS CLI. The Cisco CBQoS Technology Pack collects and reports performance metrics gathered from this MIB. To use the Cisco CBQoS Technology Pack, you need to understand the CISCO-CLASS-BASED-QOS-MIB and the Modular CB QoS CLI. This document assumes that you have such knowledge and that you understand how the CISCO-CLASS-BASED-QOS-MIB has been configured and modified at your site. For more information on the CISCO-CLASS-BASED-QOS-MIB and the Modular CB QoS CLI, see the appropriate Cisco documentation. For information about properties and formulas supported by this technology pack, see the IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack Reference. 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 devices that provide SNMP Agent support, as defined in the CISCO-CLASS-BASED-QOS-MIB and the RFC1213-MIB. IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide 3

8 Chapter 2: Devices and services RFC1213-MIB The RFC1213-MIB is a Management Information Base (MIB) that defines objects associated with the following groups: system Defines objects associated with system operation, including system uptime, system name, system services, and so forth. The following list provides examples of the system group objects: sysuptime sysname syslocation sysservices interfaces Defines objects that keep track of each interface operating in a managed entity. The interfaces group monitors the status of each interface including the number of network interfaces present on the system, the type of network entity, the interface s current bandwidth, and so forth. The following list provides examples of the interfaces group objects: ifnumber iftype ifspeed at The at (address translation group) is provided for backward compatibility with MIB-I. ip Defines objects that keep track of IP (Internet Protocol) routing and other IP-related activities. The following list provides examples of the ip group objects: ipindiscards ipoutdiscards iproutedest icmp Defines objects that keep track of the activities related to the Internet Control Message Protocol (ICMP). The following list provides examples of the icmp group objects: icmpinmsgs icmpoutmsgs icmpinerrors icmpouterrors tcp Defines objects that keep track of the activities related to the Transmission Control Protocol (TCP). The following list provides examples of the tcp group objects: tcprtomin tcprtomax tcpactiveopens tcppassiveopens udp Defines objects that keep track of the activities related to the User Datagram Protocol (UDP). The following list provides examples of the udp group objects: udpindatagrams udpoutdatagrams udpinerrors udplocaladdress egp Defines objects that keep track of the activities related to the Exterior Gateway Protocol (EGP). The following list provides examples of the egp group objects: 4 IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide

9 Chapter 2: Devices and services egpinmsgs egpoutmsgs egpinerrors egpouterrors transmission There are currently no objects defined for this group. snmp Defines objects that keep track of the activities related to the SNMP (Simple Network Management Protocol). The following list provides examples of the snmp group objects: snmpinpkts snmpoutpkts snmpingetresponses snmpintraps CISCO-CLASS-BASED-QOS-MIB The CISCO-CLASS-BASED-QOS-MIB defines objects associated with QoS configuration and statistics information for Cisco platforms that support the Modular CB QoS CLI (Modular Class-Based Quality of Service Command Line Interface) representing multiple logical entities supported by a single SNMP Agent. Configuration information available through this MIB includes all ClassMap, PolicyMap, Match Statements, and Feature Actions configuration parameters. Statistics available through this MIB include summary counts/rates by traffic class before and after any configure QoS policies are enforced. In addition, detailed feature-specific statistics are available for select PolicyMap features. For information about the objects defined in the CISCO-CLASS-BASED-QOS-MIB, see Review of the CISCO- CLASS-BASED-QOS-MIB on page 8. 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: IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide 5

10 Chapter 2: Devices and services 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. 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 6 IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide

11 Chapter 2: Devices and services 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 startingpoint and 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. 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) IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide 7

12 Chapter 2: Devices and services 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 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 8 IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide

13 Chapter 2: Devices and services 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). 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 reuse of service policies is of great value to a 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 IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide 9

14 Chapter 2: Devices and services 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 cbqospolicydirection 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 5: Classes Match Statements Service Policies Actions 10 IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide

15 Chapter 2: Devices and services 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 cbqosobjectsindex 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 IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide 11

16 Chapter 2: Devices and services Table 1 briefly describe each of these configuration tables. The Cisco CBQoS Technology Pack maps these table objects to appropriately named Tivoli Netcool/Proviso 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 cbqoscmcfgtable cbqosmatchstmtcfg 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. 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. 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. cbqospolicymapname cbqoscmname cbqosmatchstmtname 12 IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide

17 Chapter 2: Devices and services Table 1: Configuration tables Table name Description Objects used by the technology pack cbqosqueueingcfg Table cbqosredcfgtable cbqosredclasscfg 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. 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. 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. cbqosqueueingcfgbandwidth cbqosqueueingcfgbandwidthunits cbqosredcfgdscpprec cbqosredcfgexponweight cbqosredcfgmeanqsize cbqosredvalue cbqosredcfgmaxthreshold cbqosredcfgminthreshold cbqosredcfgpkgdropprob IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide 13

18 Chapter 2: Devices and services Table 1: Configuration tables Table name Description Objects used by the technology pack cbqospolicecfg Table cbqostscfgtable 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. 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. cbqospolicecfgburstsize cbqospolicecfgconformaction cbqospolicecfgexceedaction cbqospolicecfgextburstsize cbqospolicecfgrate cbqospolicecfgviolateaction cbqostscfgburstsize cbqostscfgextburstsize cbqostscfgrate 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 14 IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide

19 Chapter 2: Devices and services 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 describes statistical information about a match statement. The cbqosmatchstmtstatstable includes IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide 15

20 Chapter 2: Devices and services 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. 16 IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide

21 Chapter 2: Devices and services 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 (defined in the cbqosobjectstable) and cbqospolicyindex (defined in the IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide 17

22 Chapter 2: Devices and services 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 11 for more information. The Cisco CBQoS Technology Pack uses the following objects in the cbqosredclassstatstable: cbqosredrandomdropbyte64 cbqosredrandomdroppkt64 cbqosredtaildropbyte64 cbqosredtaildroppkt64 cbqosredtransmitbyte64 cbqosredtransmitpkt64 18 IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide

23 Chapter 3: Supported reports and This chapter discusses the following topics: Topic Page Overview 19 Reporter sets 19 Reporter set tree 20 Reporter set contents 21 Key performance indicators 33 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/Proviso Cisco Class-Based QoS 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/Proviso Cisco Class-Based QoS 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/Proviso DataView User s Guide. This Technology Pack User Guide assumes an understanding of the report-related topics discussed in the IBM Tivoli Netcool/Proviso DataView User s 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. IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide 19

24 Chapter 3: Supported reports and Table 2 shows a summary of the reports in each reporter set provided by the Cisco CBQoS Technology Pack. Table 2: Reporter set summary Reporter set Dashboard Group Resource Detail Threshold Class Match Common Reports Per Policy Police Queue Shape WRED TOTALS See the IBM Tivoli Netcool/Proviso DataView User s 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: AP Cisco CBQoS Police Shape Per Policy Queue WRED Class Match Common Reports 20 IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide

25 Chapter 3: Supported reports and Reporter set contents This section describes the contents of the reporter sets provided in the Cisco CBQoS Technology Pack, including the key performance indicators () for each report. Police Policed Traffic per Class Resource Summary Policing Exceeded Volume (octets) Policing Violated Volume (octets) Policing Violated Volume (packets) Policing Conformed Volume (octets) Policing Conformed Volume (packets) Policing Exceeded Volume (packets) Conformed Volume (octets) Violated Volume (octets) Policed Traffic per Class Group Summary Policing Exceeded Volume (octets) Policing Violated Volume (octets) Policing Violated Volume (packets) Policing Conformed Volume (octets) Policing Conformed Volume (packets) Policing Exceeded Volume (packets) Violated Volume (octets) Conformed Volume (octets) Policed Traffic Details Policing Exceeded Volume (octets) Policing Violated Volume (octets) Policing Violated Volume (packets) Policing Conformed Volume (octets) IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide 21

26 Chapter 3: Supported reports and Policing Conformed Volume (packets) Policing Exceeded Volume (packets) Policing Exceeded Volume (octets) Policing Violated Volume (octets) Policing Exceeded Volume (packets) Policing Conformed Volume (octets) Policing Conformed Volume (packets) Policing Violated Volume (packets) Policed Traffic per Class Action Overview Policing Exceeded Volume (octets) Policing Violated Volume (octets) Policing Violated Volume (packets) Policing Conformed Volume (octets) Policing Conformed Volume (packets) Policing Exceeded Volume (packets) Rank Variations for Policing Exceeded Volume (octets) Highest Policing Violated Volume (packets) Rank Variations for Policing Conformed Volume (octets) Highest Policing Violated Volume (octets) Highest Policing Conformed Volume (packets) Highest Policing Conformed Volume (octets) Highest Policing Exceeded Volume (packets) Rank Variations for Policing Violated Volume (packets) Rank Variations for Policing Violated Volume (octets) Rank Variations for Policing Conformed Volume (packets) Rank Variations for Policing Exceeded Volume (packets) Highest Policing Exceeded Volume (octets) Shape Shaping Details Traffic Shaping Dropped Throughput (bps) 22 IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide

27 Chapter 3: Supported reports and Traffic Shaping Delayed Volume (packets) Traffic Shaping Delayed Throughput (bps) Traffic Shaping Dropped Volume (packets) Dropped Volume (packets) Dropped Throughput (bps) Delayed Volume (packets) Delayed Throughput (bps) Shaped Traffic per Class Resource Summary Traffic Shaping Delayed Volume (packets) Traffic Shaping Dropped Volume (packets) Traffic Shaping Delayed Volume (octets) Traffic Shaping Dropped Volume (octets) Dropped Volume (octets) Delayed Volume (octets) Shaped Traffic per Class Group Summary Traffic Shaping Delayed Volume (packets) Traffic Shaping Dropped Volume (packets) Traffic Shaping Delayed Volume (octets) Traffic Shaping Dropped Volume (octets) Dropped Volume (octets) Delayed Volume (octets) Shaped Traffic per Class Action Overview Traffic Shaping Dropped Throughput (bps) Traffic Shaping Delayed Volume (packets) Traffic Shaping Delayed Throughput (bps) Traffic Shaping Dropped Volume (packets) Highest Traffic Shaping Dropped Volume (packets) IBM Tivoli Netcool/Proviso Cisco Class-Based QoS Technology Pack User Guide 23