Enabling Ethernet Overhead Accounting On The Pre3 And Pre4; Verifying Overhead Accounting - Cisco 10000 Series Configuration Manual

Verifying Overhead Accounting

!
interface GigabitEthernet1/0/0.100

Enabling Ethernet Overhead Accounting on the PRE3 and PRE4

The following configuration example shows how to enable Ethernet overhead accounting on the PRE3
or PRE4. In the example, the configuration of the policy map named ethernet_ovrh shapes class-default
traffic at a rate of 200,000 kbps and enables overhead accounting with a user-defined value of 18. The
ethernet_ovrh policy is attached to subinterface Gigabit Ethernet 1/0/0.100, thereby enabling overhead
accounting on the subinterface.
Router# configuration-terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# policy-map ethernet_ovrh
Router(config-pmap)# class class-default
Router(config-pmap-c)# shape average 200000 account user-defined 18
!
Router(config)# interface GigabitEthernet1/0/0.100
Router(config-subif)# service-policy output ethernet_ovrh
!
Router# show running-config | begin 1/0/0.100
interface GigabitEthernet1/0/0.100
encapsulation dot1Q 101
pppoe enable group group_pta
service-policy output ethernet_ovrh
Verifying Overhead Accounting
To verify overhead accounting, enter any of the following commands in privileged EXEC mode:
Command
Router# show policy-map [interface interface]
Cisco 10000 Series Router Quality of Service Configuration Guide
10-12
shape 200 account user-defined 18
encapsulation dot1q 100
pppoe enable group global
no snmp trap link-status
service-policy output ethernet_ovrh
Purpose
Displays information about the policy map attached to the
interface you specify, including ATM overhead accounting. If
you do not specify an interface, the command displays
information about all of the policy maps configured on the router.
interface interface is the interface type and number (for example,
atm 4/0/0).
When you enter the show policy-map interface
Note
command, the resulting classification byte counts and the
queuing feature byte counts do not match. This mismatch
occurs because the classification byte count does not
consider overhead, whereas the queuing features do
consider overhead.
Chapter 10 Overhead Accounting
OL-7433-09