Network Router User Manual

A-25
Cisco 7304 Router MIB Specifications Guide
OL-4925-02
Appendix A Using MIBs
Billing Customers for Traffic
Input and Output Interface Counts
The router maintains information about the number of packets and bytes that are received on an input
interface and transmitted on an output interface. When a QoS service policy is attached to an interface,
the router applies the rules of the policy to traffic on the interface and increments the packet and bytes
counts on the interface.
The following CISCO-CLASS-BASED-QOS-MIB objects provide interface counts:
• cbQosCMDropPkt and cbQosCMDropByte (cbQosCMStatsTable)—Total number of packets and
bytes that were dropped because they exceeded the limits set by the service policy. These counts
include only those packets and bytes that were dropped because they exceeded service policy limits.
The counts do not include packets and bytes dropped for other reasons.
• cbQosPoliceConformedPkt and cbQosPoliceConformedByte (cbQosPoliceStatsTable)—Total
number of packets and bytes that conformed to the limits of the service policy and were transmitted.
Determining the Amount of Traffic to Bill to a Customer
Perform these steps to determine how much traffic on an interface is billable to a particular customer:
Step 1 Determine which service policy on the interface applies to the customer.
Step 2 Determine the index values of the service policy and class map used to define the customer’s traffic. You
will need this information in the following steps.
Step 3 Access the cbQosPoliceConformedPkt object (cbQosPoliceStatsTable) for the customer to determine
how much traffic on the interface is billable to this customer.
Step 4 (Optional) Access the cbQosCMDropPkt object (cbQosCMStatsTable) for the customer to determine
how much of the customer’s traffic was dropped because it exceeded service policy limits.
Scenario for Demonstrating QoS Traffic Policing
This section describes a scenario that demonstrates the use of SNMP QoS statistics to determine how
much traffic on an interface is billable to a particular customer. It also shows how packet counts are
affected when a service policy is applied to traffic on the interface.
To create the scenario, follow these steps, each of which is described in the sections that follow:
1. Create and attach a service policy to an interface.
2. View packet counts before the service policy is applied to traffic on the interface.
3. Issue a ping command to generate traffic on the interface. Note that the service policy is applied to
the traffic.
4. View packet counts after the service policy has been applied to determine how much traffic to bill
the customer for:
• Conformed packets—The number of packets within the range set by the service policy and for
which you can charge the customer.
• Exceeded or dropped packets—The number of packets that were not transmitted because they
were outside the range of the service policy. These packets are not billable to the customer.